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 shard retirement #1598

Open
brenzi opened this issue May 1, 2024 · 0 comments
Open

implement shard retirement #1598

brenzi opened this issue May 1, 2024 · 0 comments

Comments

@brenzi
Copy link
Collaborator

brenzi commented May 1, 2024

We need a way for governance to shut down a sidechain without waiting for all account holders to withdraw their funds. One possible use case is migrating to a different logic that may be controversial: in that case we would not want to force anyone to participate.
Another use case could be a panic mode: setting the shard in maintenance mode and retire it entirely because fixing might not even be possible or practical.

From a security & privacy perspective it should actually be fine if we simply unshield all L2 accounts to identical L1 accounts. The privacy lies in the transactions, not in the balances of accounts which have no linkability anywhere.

Open questions:

  • what contidions must be met to retire a shard?
  • edge cases: what if final dump extrinsics fail?
  • in maintenance mode, no more blocks should be produced. how to implement idempotent retirement? How to make sure each account is only unshielded once?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant