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

fraud: handle not verified fraud proofs #6

Open
vgonkivs opened this issue Jun 13, 2022 · 0 comments
Open

fraud: handle not verified fraud proofs #6

vgonkivs opened this issue Jun 13, 2022 · 0 comments

Comments

@vgonkivs
Copy link
Member

vgonkivs commented Jun 13, 2022

There are case when we are not able to ensure the Fraud Proof is valid. Mainly, It could happened due to a network issue when we can't fetch an ExtendedHeader. In a private discussion with @Wondertan we discussed several ways to resolve this:

  1. start an infinite routine that will fetch header until it will not be available;
  2. add proof with Not Verified state to FraudStore;
  3. consider this case during FraudSync implementation(#536);

IMO, the second way will make FraudStore structure more complicated. I think we should store only verified and correct Fraud Proofs.

@Wondertan Wondertan transferred this issue from celestiaorg/celestia-node Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: TODO
Development

No branches or pull requests

1 participant