Skip to main content

Prove API

Overview​

The Prove API takes inspiration from Superchain's native interop to define an identifier. This version of the API is designed to prove an entire transaction receipt, with capabilities to prove individual logs or multiple logs within the receipt.

Current Capabilities:​

  • Prove an Entire Receipt: You can prove an entire transaction receipt from a source blockchain.
  • Prove Logs within Receipt: As an application, you can prove a single log or multiple logs within the provided receipt.

User Flow​

Before an on-chain message can be sent, the "solver" must first query the Prove API.

  1. Request Proof: Use the receipt_requestProof method to request a proof, which returns a jobID.
  2. Poll for Proof: Use the receipt_queryProof method with the jobID to poll for proof responses.

Find info here to:

  • Access the functions with POST requests to API end point
  • Submit requests and experience the API
  • Track your request from the our explorer

Note: Polymer is a rollup that continuously builds blocks and updates its state. As a result, proofs are most cost-effective within a recent time window. Currently, for testing purposes, we provide proofs for the last 3–4 hours, as proof retrieving data deeper in the rollup trie becomes increasingly expensive.