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

Ensure protocol configurations encapsulate their valid record members to avoid breaking convergence #335

Closed
csuwildcat opened this issue May 1, 2023 · 1 comment
Assignees
Labels
duplicate This issue or pull request already exists feature New feature or request

Comments

@csuwildcat
Copy link
Member

Presently, if you reconfigure an already installed protocol that has records that fell under it, and the new configuration changes some things that would make previously valid records under the old protocol rules invalid under the new rules, it can create a split brain state if old records are replayed against new rules. To avoid this, we must tie records to a given protocol configuration and seal up the records that are to be retained against them when reconfiguration occurs.

@csuwildcat csuwildcat added this to DWN May 1, 2023
@csuwildcat csuwildcat converted this from a draft issue May 1, 2023
@frankhinek frankhinek moved this to Backlog in Web5 Roadmap May 1, 2023
@thehenrytsai thehenrytsai moved this from High Priority Backlog to In Progress in DWN May 1, 2023
@thehenrytsai thehenrytsai moved this from In Progress to High Priority Backlog in DWN May 23, 2023
@thehenrytsai thehenrytsai added duplicate This issue or pull request already exists feature New feature or request labels Sep 14, 2024
@thehenrytsai
Copy link
Contributor

Dupe of #740.

@github-project-automation github-project-automation bot moved this from Backlog to Done in Web5 Roadmap Sep 14, 2024
@github-project-automation github-project-automation bot moved this from High Priority Backlog to Done in DWN Sep 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants