Skip to content

Testnet prover onboarding — third-party participation, gRPC endpoint, SP1 version #222

Description

@coreyhahn

▎ Hi — building a custom prover daemon (Rust + tonic) against the testnet contracts on Sepolia (chain 11155111). The repo's contracts/deployments/11155111.json (https://github.com/succinctlabs/network/blob/main/contracts/deployments/11155111.json) shows a single PROVER address (0x7B77...aEa42), and the recent "testnet is live" blog post (https://blog.succinct.xyz/network/the-succinct-prover-network-testnet-is-live/) is requester-focused. I couldn't find an active community channel (forum is quiet, Discord is unmaintained), so filing here.

▎ Four questions:

▎ 1. Is third-party prover participation open on Sepolia testnet today, or limited to Succinct + selected partners? If the latter, what's the process to be considered?
▎ 2. How do I get testnet PROVE to stake to the SuccinctStaking contract at 0x837D40650aB3b0AA02E7e28238D9FEA73031856C?
▎ 3. What's the canonical gRPC endpoint URL for the network.ProverNetwork service on testnet? (My client connects via tonic against the vendored .proto files from this repo.)
▎ 4. SP1 6.2 (Hypercube) compatibility: will proofs from a Hypercube prover verify against the deployed Sepolia VERIFIER 0x29A39a8Ecd2473FBcD7bfAA2526Fcb1B1F692Eb1? crates/network/rpc/Cargo.toml pins sp1-sdk = "5.2.3" — want to confirm I don't need to downgrade.

▎ Happy to update this thread with what works for future third-party provers.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions