Skip to content
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

Implement commitment chain forking test with different forking points. #781

Open
piotrm50 opened this issue Feb 28, 2024 · 0 comments
Open
Labels
team-consensus Issues for Consensus Team test Hardening of all things
Milestone

Comments

@piotrm50
Copy link
Collaborator

piotrm50 commented Feb 28, 2024

Currently we have engine switching tests where we have either two competing chains, or three chains forking at the same slot (EngineSwitching_Tie).
We should implement a test in which we have three competing chains, each forking at different slot (like drawn below).
We should have 3 variations of that test, each with different winning chain.

                  /---------------- | C1
       / ------------------------ | C2
o------------------------------ | C3
@piotrm50 piotrm50 converted this from a draft issue Feb 28, 2024
@piotrm50 piotrm50 added test Hardening of all things team-consensus Issues for Consensus Team labels Feb 28, 2024
@piotrm50 piotrm50 added this to the v1.0.0-beta milestone Feb 28, 2024
@piotrm50 piotrm50 moved this from Product Backlog to Backlog in iota-core Mar 4, 2024
@piotrm50 piotrm50 moved this from Backlog to In Progress in iota-core Mar 7, 2024
@piotrm50 piotrm50 moved this from In Progress to Product Backlog in iota-core Mar 18, 2024
@piotrm50 piotrm50 modified the milestones: v1.0.0-beta, v1.0.0-rc Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-consensus Issues for Consensus Team test Hardening of all things
Projects
Status: Product Backlog
Development

No branches or pull requests

2 participants