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
After the node is upgraded to v1.10, you can get the balance of the account and the number of transactions, and ETH_SYNCING can return the latest block, it's OK to use RPC to look up the latest block data, it's OK to look up the historical block data, but looking up the details of the transaction returns null, why.
Thank you for your answer!
The text was updated successfully, but these errors were encountered:
If you wish to disable transaction unindexing altogether, you can run Geth with --txlookuplimit=0, which reverts to the old behavior of retaining the lookup map for every transaction since genesis.
Geth 1.10.0 contains some changes which remove unnecessary data in the blockchain database. In particular, Geth no longer keeps transaction inclusion info for all transactions, and instead limits the storage of inclusion records to one year. For application developers, this change means that very old transactions can no longer be accessed by hash. Note: if you would like to disable this behavior and keep inclusion information for all historical transactions, you can re-enable indexing using the --txlookuplimit=0 command-line flag. (#22293, #22419)
After the node is upgraded to v1.10, you can get the balance of the account and the number of transactions, and ETH_SYNCING can return the latest block, it's OK to use RPC to look up the latest block data, it's OK to look up the historical block data, but looking up the details of the transaction returns null, why.
Thank you for your answer!
The text was updated successfully, but these errors were encountered: