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

Evidence handling and submission #49

Open
ethanfrey opened this issue Feb 17, 2021 · 0 comments
Open

Evidence handling and submission #49

ethanfrey opened this issue Feb 17, 2021 · 0 comments
Labels
Library Functionality in the core library
Projects
Milestone

Comments

@ethanfrey
Copy link
Member

If you try to update the client to header H, but a different header was previously submitted, we have a clear case of a byzantine network (> 2/3 voting for different blocks at the same height). In this case, the relayer should be able to repackage it's knowledge into evidence of cheating on the source chain (the one who's header we were submitting, not the chain we were submitting to).

This will be hard to test without a real Byzantine testnet, so this is mainly a placeholder until there is a good test environment for this.

@ethanfrey ethanfrey created this issue from a note in Relayer (To do) Feb 17, 2021
@ethanfrey ethanfrey added this to the v2 milestone Feb 17, 2021
@ethanfrey ethanfrey added the Library Functionality in the core library label Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Library Functionality in the core library
Projects
No open projects
Relayer
To do
Development

No branches or pull requests

1 participant