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

fix(examples): use new version of the SDK on validating public input example #1798

Open
wants to merge 1 commit into
base: staging
Choose a base branch
from

Conversation

JuArce
Copy link
Collaborator

@JuArce JuArce commented Feb 12, 2025

Use new version of the SDK on validating public input example

Description

closes #1797

Due to changes in Network parameter, Validating public inputs example needs to be updated to use the correct version

This is only affected on STAGING branch

How to Test

You can follow the guide available hiere (https://github.com/yetanotherco/aligned_layer/blob/0faf6e152229113bd0a2029e5e29e2054d6f105d/docs/3_guides/3_validating_public_input.md)

This guide uses Holesky Testnet and you will need a wallet with some funds in Holesky

You can deploy your own Fibonacci validator, or use 0xFE5aBfb5E754e4AeFE1e8eC413ca6D2CCF99d5Ed in Holesky

Risc0

  1. Generate a Risc0 proof
make generate_risc0_fibonacci_proof
  1. Submit the Risc0 proof to Aligned
make submit_fibonacci_risc0_proof KEYSTORE_PATH=<KEYSTORE_PATH>
  1. Verify the batch inclusion
make verify_risc0_batch_inclusion FIBONACCI_VALIDATOR_ADDRESS=<FIBONACCI_VALIDATOR_ADDRESS> DATA_FILE_NAME=<DATA_FILE_NAME>

SP1

  1. Generate an SP1 proof
make generate_sp1_fibonacci_proof
  1. Submit the SP1 proof to Aligned
make submit_fibonacci_sp1_proof KEYSTORE_PATH=<KEYSTORE_PATH>
  1. Verify the batch inclusion
make verify_sp1_batch_inclusion FIBONACCI_VALIDATOR_ADDRESS=<FIBONACCI_VALIDATOR_ADDRESS> DATA_FILE_NAME=<DATA_FILE_NAME>

Type of change

  • Bug fix

Checklist

  • “Hotfix” to testnet, everything else to staging
  • Linked to Github Issue
  • This change depends on code or research by an external entity
    • Acknowledgements were updated to give credit
  • Unit tests added
  • This change requires new documentation.
    • Documentation has been added/updated.
  • This change is an Optimization
    • Benchmarks added/run
  • Has a known issue
  • If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
    • This PR adds compatibility for operator for both versions and do not change batcher/docs/examples
    • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

@JuArce JuArce self-assigned this Feb 12, 2025
@JuArce JuArce marked this pull request as ready for review February 13, 2025 14:15
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

Successfully merging this pull request may close these issues.

1 participant