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

Handle unexpected chain reorgs #8

Open
matthiasgeihs opened this issue Aug 12, 2021 · 0 comments
Open

Handle unexpected chain reorgs #8

matthiasgeihs opened this issue Aug 12, 2021 · 0 comments
Labels

Comments

@matthiasgeihs
Copy link
Contributor

Problem: Even with a reorg resistant subscription, it may happen that reorg with a larger depth than expected happens and the client may be subject to an attack.

Proposal: We should think about how we can deal with such a situation. A simple mitigation is to monitor such events and at least inform the client. More advanced mitigation measures may involve protocols for reacting to such unexpected events.

@matthiasgeihs matthiasgeihs transferred this issue from hyperledger-labs/go-perun Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant