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

Clarify Proof Selection Algorithm for Lambda's AlignedLayer Implementation #1755

Closed
MartinMinkov opened this issue Jul 16, 2024 · 2 comments
Closed

Comments

@MartinMinkov
Copy link
Contributor

We need to gather detailed information about our proof selection algorithm to guide Lambda in their implementation for the AlignedLayer proving in the Mina-EVM bridge project.

Objective:
Provide Lambda with a clear understanding of how our proof selection algorithm works, particularly in the context of verifying the "best block" when checking N blocks (where N < k, the protocol constant).

Key Questions to Address:

  1. How does our current proof selection algorithm verify the "best block" when checking N blocks?
  2. Can the short fork rules be applied directly, or is a more nuanced approach required?
  3. What are the implications and considerations of N being smaller than the protocol constant k?
  4. Are there any specific edge cases or scenarios that Lambda should be aware of?
  5. How does this algorithm interact with or impact the overall consensus mechanism in the bridge context?
@MartinMinkov MartinMinkov changed the title Title: Clarify Proof Selection Algorithm for Lambda's AlignedLayer Implementation Clarify Proof Selection Algorithm for Lambda's AlignedLayer Implementation Jul 16, 2024
@MartinMinkov
Copy link
Contributor Author

As per discussion, this is not needed anymore due to a redesign.

@MartinMinkov
Copy link
Contributor Author

Miscommunication, this is still needed and opening it up again.

@Trivo25 Trivo25 closed this as completed Oct 14, 2024
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

2 participants