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

Why not use tx_hash as trace id? #80

Open
fishTsai20 opened this issue Sep 13, 2024 · 0 comments
Open

Why not use tx_hash as trace id? #80

fishTsai20 opened this issue Sep 13, 2024 · 0 comments

Comments

@fishTsai20
Copy link

void McBlockEmulator::create_trace(const TransactionInfo& tx, td::Promise<Trace *> promise) {
Trace *trace = new Trace();
trace->emulated = false;
trace->workchain = tx.account.workchain;
trace->transaction_root = tx.root;
trace->id = tx.initial_msg_hash.value();
trace->node_id = tx.in_msg_hash;

Why use the in msg hash of the first tx as the id of the trace, instead of the tx hash of the first tx?
The same msg hash may belong to a different tx. How can I find his tx through this msg hash?
https://tonscan.org/tx/dda06042340501f32cb9cd0357167174067d5efd3e86a4f5c1b8cc753b6783b0
Such as tx: 84dRUUkH2DIfD98x0Lrt3cbVdG+2b/hiU9l4qdAZl+M= and tx: 00Mc+vAtxtsjzoXzFZV9gttbxEYwQf8+GlkamFjnL+Y= have same msg hash:wnbiJ48KLJva9Aal8+8GZN8PMxlKVxJx3Hw3fx6r+AI=

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant