This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Finality Gadget Handoff #864
Assignees
Milestone
Comments
|
Closed in #1014 |
liuchengxu
pushed a commit
to chainx-org/substrate
that referenced
this issue
Aug 23, 2021
* erc20 instance interface * provide root interface for erc20 * provide new selector mode * call erc20 for runtime api * erc20 call rpc * convent to erc20 contract success * check gas_limit for Exec Error in wasm contract * add erc20 fee check for compute_dispatch_fee * provide a new asset type to store erc20 asset * Revert adding addr in convert_to_asset * remove "camelCase" for ERC20Selector * erc20 info rpc * adjust gas cost, gas price and fee * add ERC20Selector item * add type for `contract_erc20_info` in rpc
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In runtime
The finality gadget will restrict its voting based on digest events in blocks communicating that the set of voters will soon change.
The format is roughly
finality_authoritiesto be applied.The runtime should create one of those events, and then after some number of blocks update the
finality_authoritieslist internally.In gadget
Voters, upon encountering a block
Bwith aHandoffEvent(new_v, m)will refuse to vote for chains longer thannum(B) + mcontainingB. This will require modification in thebest_chain_containingoperation.Once
Band a block withnum(B) + mare finalized, the validator set handoff is complete and voters should update their set.The text was updated successfully, but these errors were encountered: