We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Total difficulty always be zero, but every block difficulty always be one.
It doesn't make sense.
axon/protocol/src/types/block.rs
Line 151 in 4cf06e5
axon/core/api/src/jsonrpc/web3_types.rs
Line 322 in 4cf06e5
Same situation (just be constant) for Header.nonce:
Header.nonce
Line 337 in 4cf06e5
Line 847 in 4cf06e5
Proposals:
Should Axon just remove difficulty field from Header?
difficulty
Header
Then set Web3Block.difficulty to be constant U256::zero().
Web3Block.difficulty
U256::zero()
The nonce field in Header is useless, too.
nonce
Should Axon just remove nonce field from Header?
Then set Web3Block.nonce to be constant U256::zero().
Web3Block.nonce
Break changes:
The fields difficulty and nonce in Header are used when calculates its hash.
If Axon want to remove them, they have to be removed before release a no-break-changes version.
Ref: #1332 (comment)
The text was updated successfully, but these errors were encountered:
BlockHeader
KaoImin
yangby-cryptape
Successfully merging a pull request may close this issue.
Current Behavior
Total difficulty always be zero, but every block difficulty always be one.
It doesn't make sense.
axon/protocol/src/types/block.rs
Line 151 in 4cf06e5
axon/core/api/src/jsonrpc/web3_types.rs
Line 322 in 4cf06e5
Same situation (just be constant) for
Header.nonce
:axon/core/api/src/jsonrpc/web3_types.rs
Line 337 in 4cf06e5
axon/core/api/src/jsonrpc/web3_types.rs
Line 847 in 4cf06e5
Expected Behavior
Proposals:
Should Axon just remove
difficulty
field fromHeader
?Then set
Web3Block.difficulty
to be constantU256::zero()
.The
nonce
field inHeader
is useless, too.Should Axon just remove
nonce
field fromHeader
?Then set
Web3Block.nonce
to be constantU256::zero()
.Break changes:
Anything else?
The fields
difficulty
andnonce
inHeader
are used when calculates its hash.If Axon want to remove them, they have to be removed before release a no-break-changes version.
Ref: #1332 (comment)
The text was updated successfully, but these errors were encountered: