-
Notifications
You must be signed in to change notification settings - Fork 724
New issue
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
Remove DAG based consensus #1359
Conversation
…into linearize-on-start
if err := stopVertex.Verify(ctx); err != nil { | ||
return fmt.Errorf("failed to verify stop vertex: %w", err) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unlike block or tx verify, vertex verification was stateless, so this doesn't need to exist anymore
@@ -433,16 +247,6 @@ func (vtx *uniqueVertex) Height() (uint64, error) { | |||
return vtx.v.vtx.Height(), nil | |||
} | |||
|
|||
func (vtx *uniqueVertex) Epoch() (uint32, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was already dead code... apparently
"github.com/ava-labs/avalanchego/utils" | ||
"github.com/ava-labs/avalanchego/utils/hashing" | ||
) | ||
|
||
// Builder builds a vertex given a set of parentIDs and transactions. | ||
type Builder interface { | ||
// Build a new vertex from the contents of a vertex | ||
BuildVtx(ctx context.Context, parentIDs []ids.ID, txs []snowstorm.Tx) (avalanche.Vertex, error) | ||
// Build a new stop vertex from the parents | ||
BuildStopVtx(ctx context.Context, parentIDs []ids.ID) (avalanche.Vertex, error) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically we should be able to remove the below Build
function, but it's used for testing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What a change. So long and thanks for all the fish
// BetaRogue to be equal. Therefore we use the more conservative | ||
// BetaRogue value for both BetaVirtuous and BetaRogue. | ||
// | ||
// TODO: After the X-chain linearization use the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we still need this TODO?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup
Co-authored-by: Stephen <stephen@avalabs.org>
Why this should be merged
All consensus instances are now chain based.
How this works
Removes the Avalanche consensus engine and avalanche consensus instance.
How this was tested
CI + TODO: local testing