Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Substrate: Alternative consensus engines #420

Closed
gavofyork opened this issue Jul 25, 2018 · 3 comments
Closed

Substrate: Alternative consensus engines #420

gavofyork opened this issue Jul 25, 2018 · 3 comments
Labels
J0-enhancement An additional feature request. Z5-epic Can only be fixed by John Skeet.
Projects
SDK Node (deprecated)
Milestone
Polkadot

Comments

@gavofyork
Copy link
Member

Substrate currently uses only Rhododendron. The consensus algorithm should instead be stored in the :consensus key of the database (defaulting to rho if it doesn't exist) and substrate should use that algorithm to determine what consensus protocol to use for the given block. Since some consensus algorithms are non-final or require multiple blocks to reach finality, then any block whose state-transition function alters the :consensus key to anything other than rho will use rho to finalise that block as a handoff procedure.

The consensus algorithm is free to require arbitrary other storage keys for its operation.

In principle, in the future, there may be a handoff to dot.
@gavofyork gavofyork added this to the PoC-3 (AFG) milestone Jul 25, 2018
@gavofyork gavofyork added J0-enhancement An additional feature request. Z5-epic Can only be fixed by John Skeet. labels Jul 25, 2018
@gavofyork gavofyork modified the milestones: PoC-3 (AFG), As-and-when Aug 30, 2018
@gavofyork gavofyork modified the milestones: As-and-when, 1.x series Dec 18, 2018
@Demi-Marie
Copy link
Contributor

It seems that this has already been fixed. We already use AuRa and GRANDPA, and BABE is being worked on.

@Demi-Marie
Copy link
Contributor

@gavofyork can this be closed?

@tomaka
Copy link
Contributor

tomaka commented Jul 24, 2019

Triage. This looks like a duplicate of #1304, which contains more details.

@tomaka tomaka closed this as completed Jul 24, 2019
liuchengxu pushed a commit to chainx-org/substrate that referenced this issue Aug 23, 2021
@koushiro @gguoss
Migrate cli to 2018 edition (paritytech#420)
d5c51ec 
* Migrate cli to 2018 edition

Signed-off-by: koushiro <koushiro.cqx@gmail.com>

* Remove useless dep

Signed-off-by: koushiro <koushiro.cqx@gmail.com>

* Update wasm

Signed-off-by: koushiro <koushiro.cqx@gmail.com>
liuchengxu pushed a commit to chainx-org/substrate that referenced this issue Aug 23, 2021
@atenjin
Use 0 instead of returning Error in sign script check (paritytech#420)
412e808 
in chainx 1.0, the script check is just use 0, not return error. But in 2.0 I use Error to return directly. However this cause create_withdraw_tx could not create an empty sign tx. Thus, we recover this part to push a zero in result, not return Error directly.
liuchengxu pushed a commit to subspace/substrate that referenced this issue Jun 3, 2022
@nazar-pc
Merge pull request paritytech#420 from subspace/update-rse
3b41ea1 
Switch back to upstream reed-solomon-erasure library
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
J0-enhancement An additional feature request. Z5-epic Can only be fixed by John Skeet.
Projects
No open projects
SDK Node (deprecated)
  
Awaiting triage
Milestone
Polkadot
Development

No branches or pull requests
3 participants
@gavofyork @tomaka @Demi-Marie