Skip to content
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

Closed
Tracked by #2617
ryujimin220 opened this issue Aug 17, 2023 · 6 comments
Closed
Tracked by #2617

Missing transactions in block 6754141 #2694

ryujimin220 opened this issue Aug 17, 2023 · 6 comments
Assignees
Labels
S: ImprovingThings Improving things: Customer requests, performance improvements, reliability and usability type: bug Issues that need priority attention -- something isn't working

Comments

@ryujimin220
Copy link

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!

@ryujimin220 ryujimin220 added the status: waiting-triage This issue/PR has not yet been triaged by the team. label Aug 17, 2023
@mpoke mpoke removed the status: waiting-triage This issue/PR has not yet been triaged by the team. label Aug 22, 2023
@mpoke mpoke added S: ImprovingThings Improving things: Customer requests, performance improvements, reliability and usability type: bug Issues that need priority attention -- something isn't working labels Sep 15, 2023
@mmulji-ic
Copy link
Contributor

Hi @ryujimin220 can you let me know which cmd you used and also which node that you used?

@ryujimin220
Copy link
Author

Hi @mmulji-ic,
I used my archive node, it's currently running at v13.0.0

blockchain call --> shows 2 txs

`curl localhost:26657 \

--header "Content-Type: application/json"
--request GET
--data '{"jsonrpc":"2.0", "id":0, "method":"blockchain", "params":["6754141","6754141"]}'
{"jsonrpc":"2.0","id":0,"result":{"last_height":"17481129","block_metas":[{"block_id":{"hash":"A43D7646212CD7781568BA2D8F3FEB045EF312898BB322356989DE5A36DB789C","parts":{"total":1,"hash":"251525748D218AB4F0E4E969DF7EC8230FA64DCB0778CAE5B5A2E5476915810A"}},"block_size":"14438","header":{"version":{"block":"11"},"chain_id":"cosmoshub-4","height":"6754141","time":"2021-06-29T10:09:52.790318277Z","last_block_id":{"hash":"01C7EA94231B932E399BEB9D7E8242AF25A3A614B996569635B35007825BBDAE","parts":{"total":1,"hash":"BE0EA43A2ED93A2952ED35951A1D81367088817885E335DB3F13C6475DEF73F4"}},"last_commit_hash":"42803B7727ED43B1F17F1223EB4A7AE75F6980C0C487CDD15A58F1951CC84B5B","data_hash":"2226775513103302CB081C6BD2E52C7B4CFC2B050DBD36F35A0315FE71A44755","validators_hash":"F80B2048D40E062DAD3CF770D91067E0E5206C6CFCB9A41BBE79C121870662FE","next_validators_hash":"F80B2048D40E062DAD3CF770D91067E0E5206C6CFCB9A41BBE79C121870662FE","consensus_hash":"0F2908883A105C793B74495EB7D6DF2EEA479ED7FC9349206A65CB0F9987A0B8","app_hash":"DEAE8FAAF1B604DD94477E3979A4BC7760B0C7A567C602542013E656F91FB724","last_results_hash":"63BE60C199831621F0E72DEAAC28B2E6A70B731322258A071AA13874454717A2","evidence_hash":"E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855","proposer_address":"818964B4FB36D28109C3E853778B33231B27C5FC"},"num_txs":"2"}]}}`

tx_search call --> shows 0 txs

`curl localhost:26657 \

--header "Content-Type: application/json"
--request GET
--data '{"jsonrpc":"2.0", "id":0, "method":"tx_search", "params":["tx.height=6754141" , true, "1", "100", "asc",true]}'
{"jsonrpc":"2.0","id":0,"result":{"txs":[],"total_count":"0"}}`

And as you can see from the block explorer, it's confirmed that it has 2 transactions.
https://www.mintscan.io/cosmos/block/6754141

@ryujimin220
Copy link
Author

Hi @mmulji-ic ,
Any updates on this? T_T

@mmulji-ic
Copy link
Contributor

Hi there @ryujimin220 , indeed your query and mintscan results match.
I tried a couple other rpc endpoints from the chain registry and they also return 0 txs for the block height you specified.

I tried for different heights 17875455 and 17075455. The former returns data and the later is further back in time, though not as far back as your initial query.

curl https://rpc-cosmoshub.blockapsis.com \
--header "Content-Type: application/json" \
--request GET \
--data '{"jsonrpc":"2.0", "id":0, "method":"tx_search", "params":["tx.height=17075455" , true, "1", "100", "asc",true]}' \
∙
{"jsonrpc":"2.0","id":0,"result":{"txs":[],"total_count":"0"}}%

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

# MinRetainBlocks defines the minimum block height offset from the current
# block being committed, such that all blocks past this offset are pruned
# from Tendermint. It is used as part of the process of determining the
# ResponseCommit.RetainHeight value during ABCI Commit. A value of 0 indicates
# that no blocks should be pruned.

To retrieve full historic information, you must use an archive node that has pruning turned off.

@ryujimin220
Copy link
Author

ryujimin220 commented Nov 23, 2023

Hi @mmulji-ic ,
As I mentioned above, I AM using archive node.. and pruning is set to "nothing"
pruning = "nothing"

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 blockchaincall .. but not when I make tx_searchcall ..

Will you please look into this again and keep me posted? Thanks!!!!!

@ryujimin220
Copy link
Author

Hi @mmulji-ic !!
Any updates on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S: ImprovingThings Improving things: Customer requests, performance improvements, reliability and usability type: bug Issues that need priority attention -- something isn't working
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants