-
Notifications
You must be signed in to change notification settings - Fork 730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing transactions in block 6754141 #2694
Comments
Hi @ryujimin220 can you let me know which cmd you used and also which node that you used? |
Hi @mmulji-ic, blockchain call --> shows 2 txs`curl localhost:26657 \
tx_search call --> shows 0 txs`curl localhost:26657 \
And as you can see from the block explorer, it's confirmed that it has 2 transactions. |
Hi @mmulji-ic , |
Hi there @ryujimin220 , indeed your query and mintscan results match. I tried for different heights
This is probably dependent on min-retain-blocks parameter in the CometBFT configuration - which controls whether to keep block data past a certain threshold. See https://docs.cosmos.network/main/learn/advanced/config
To retrieve full historic information, you must use an archive node that has pruning turned off. |
Hi @mmulji-ic , Since it's an archive node, i should be able to retrieve full historic information however, i'm not able to.. and that's why I asked to see if you know what the problem could be.. It's weird how it shows transactions when using Will you please look into this again and keep me posted? Thanks!!!!! |
Hi @mmulji-ic !! |
Problem
I'm trying to query (from cosmos archive node) transactions in block 6754141 but it seems like there's an issue.
Problem details
Block 6754141 shows two transactions using the “blockchain” call which is also confirmed by mintscan (https://www.mintscan.io/cosmos/blocks/6754141). However, when I make the tx_search call, it's returning 0 transactions.
The same issue has occurred not only on the archive node I'm using but also on other Node providers' archive nodes.
I tried the same on block 6754140 (one block before the targeted block) and on block 6754142 (one block after the targeted block) and both worked fine (I was able to get list of transactions when I make the tx_search call.
Any idea what the problem is? Is the a bug? Anyone else facing or have faced similar issue?
Thanks in advance!
The text was updated successfully, but these errors were encountered: