-
Notifications
You must be signed in to change notification settings - Fork 39
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
Transactions root of genesis block is incorrect #1305
Closed
6 of 20 tasks
Labels
t:bug
Something isn't working
Comments
This is a bug, the transactions root in genesis file is empty, however, Axon does not calculate the transactions root when execute genesis block. |
How about other similar fields? For example, p.s. I updated the description of this issue, please select the fields at there. |
|
11 tasks
This was
linked to
pull requests
Sep 26, 2023
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
When calculating the genesis hash as previous hash of block 1, the transactions root is not set.
I'm not sure whether there is any transactions in genesis block.
But, even there is no transactions, the transactions root still could NOT be zeros, since there is a default value
RLP_NULL
.axon/core/consensus/src/engine.rs
Lines 73 to 79 in 8f3eded
axon/protocol/src/types/primitive.rs
Lines 33 to 36 in 8f3eded
Expected Behavior
Transactions root in genesis block should follow the consensus rules.
As a comparison, the receipts root and state root are refreshed before saved.
axon/core/run/src/lib.rs
Lines 168 to 172 in 8f3eded
OS
Not Associated
Axon version
v0.1.0-beta.5
Kernel
Not Associated
Relevant log output
No response
Anything else?
Sadly, if it has a fix, the fix will be a break change.
And, please check all of the following fields again:
axon/devtools/chain/genesis_single_node.json
Lines 4 to 29 in 8f3eded
Which fields should be reset after the genesis block executed?
Select them in the following list:
The text was updated successfully, but these errors were encountered: