You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://node1.mainnet.hathor.network/v1a/transaction?type=tx&count=10&hash=00000000c89746d3a41a6b8958b911b4137b40183017989f2969ccdcd6d7f0d0×tamp=1661892256&page=previous is using the rocksdb index.
http://localhost:8083/v1a/transaction?type=tx&count=10&hash=00000000c89746d3a41a6b8958b911b4137b40183017989f2969ccdcd6d7f0d0×tamp=1661892256&page=previous is a local node using memory index.
I tested this and it still happens. The fix should be trivial but we have to pick one of the two orderings. Also this shouldn't have any impact on any system, it's just an API preference.
API
/transaction
uses an index that is returning a different list depending on the index used in the full node.The explorer bug in this issue: HathorNetwork/hathor-explorer#220 is related to this issue here.
Example of APIs:
https://node1.mainnet.hathor.network/v1a/transaction?type=tx&count=10&hash=00000000c89746d3a41a6b8958b911b4137b40183017989f2969ccdcd6d7f0d0×tamp=1661892256&page=previous
is using the rocksdb index.Return
http://localhost:8083/v1a/transaction?type=tx&count=10&hash=00000000c89746d3a41a6b8958b911b4137b40183017989f2969ccdcd6d7f0d0×tamp=1661892256&page=previous
is a local node using memory index.Return
The lists are in the opposite order.
The text was updated successfully, but these errors were encountered: