Things need to be done in Darwinia/Crab 2.0 #843
Replies: 3 comments
-
Next version of Staking: #912 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Considering beefy mandatory relay costs, change and make era period larger. (Darwinia 4 days? Crab 1 days?) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Move the beefy support to Darwinia 2.0, and use EcdsaAuthorities for the Ethereum theMerge plan. (And wait for BLS support) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Darwinia 2.0 means that the chain is required to be restarted as a new chain, but the chain state of current Darwinia(1.0) will be reserved and exported as the genesis state of Darwinia 2.0. During the stop of Darwinia 1.0 and start of Darwinia 2.0, block production will stop.
The time of Darwinia 2.0 launch is unknowable and unpredictable for now, it is not on the plan, and something we should avoid in near future due to its very low priority.
This thread is to track the things need to be done in 2.0 we know now, the other parts in the scope is still unclear and to be researched.
block.number
as the block environment of ethereum tx, especially block.number could be reset to zero. They should useblock.timestamp
instead. Warning the smart contract developers should NOT use block.number crab-docs#140Other things to discuss.
Beta Was this translation helpful? Give feedback.
All reactions