That means that the only direction the pagination for transactions work is from oldest transactions to the newest. That makes it impossible or inefficient to make a proper pagination of transactions, requesting pages of transactions from newest to oldest.
Please add support for query parameters last and before
Fuel’s client leverages RocksDB for data storage, and as evidenced in the source code at FuelLabs/fuel-core, RocksDB does not inherently support reverse iteration over a prefix. This limitation can be observed in the way the data is managed within the system.
But I totally get that this is a big deal and a useful feature to have. I’m going to bring this up with the client team and see what we can do about it. Thanks for pointing it out – it’s really helpful feedback.