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

Spec question: what to do if signers process peg-in during bad state? #35

Open
MarvinJanssen opened this issue Aug 2, 2023 · 1 comment

Comments

@MarvinJanssen
Copy link
Member

A current gap in the spec is the question of what to do if the signers process a deposit anyway while in a bad state?

Situation is as follows:

  1. Protocol is a bad state due to whatever reason.
  2. User manages to create a deposit request successfully.
  3. Signers should not process the deposit request but do it anyway, thus moving the Bitcoin from the escrow address to the peg wallet. (It is on Bitcoin so we cannot prevent it.)
  4. Since the protocol is frozen, the protocol will not accept the proof that the Bitcoin was moved.
  5. The user now has no Bitcoin and no sBTC.

We had consensus that the protocol would effectively be frozen during a bad state, not allowing deposits and withdrawals. However, that can leave us in an awkward state as seen above.

I think that when the protocol is in a bad state, the onus is on the signers not to process deposits. If they do it anyway for whatever reason, then the protocol should still mint sBTC. In other words, there should be no guard in the deposit processor that would prevent sBTC minting when the protocol is in a bad state.

@MarvinJanssen MarvinJanssen changed the title Spec question: what to do if signers process peg-in during bad state Spec question: what to do if signers process peg-in during bad state? Aug 2, 2023
@MarvinJanssen MarvinJanssen self-assigned this Aug 4, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Stacks Core Eng Aug 4, 2023
Copy link

stale bot commented Mar 17, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Status: 🆕 New
Development

No branches or pull requests

1 participant