Describe "Why" this is needed
Atm of writing, dusk-blockchain repo use to hardcode the values of rusk's state-root and the derived genesis-hash.
This were introduced in order to mitigate the possibility of being error-prone after a breaking change upgrade.
Since we introduced the protocol and rusk versions, the genesis consistency checks should not be required anymore.
ℹ️ Dusk-blockchain shall accept any state-root provided by rusk itself if the chain db is at block 0.
⚠️ The node is expected to fail to accept blocks if the connected rusk is using a wrong genesis state root.
Describe "Why" this is needed Atm of writing,
dusk-blockchain
repo use to hardcode the values of rusk'sstate-root
and the derivedgenesis-hash
. This were introduced in order to mitigate the possibility of being error-prone after a breaking change upgrade. Since we introduced the protocol and rusk versions, the genesis consistency checks should not be required anymore.ℹ️ Dusk-blockchain shall accept any state-root provided by rusk itself if the chain db is at block 0. ⚠️ The node is expected to fail to accept blocks if the connected rusk is using a wrong genesis state root.
Describe alternatives you've considered N/A
Additional context N/A