Summary: Polymer is best cataloged as proof-based interoperability infrastructure rather than as a classic bridge or messaging protocol. Its current official materials focus on giving developers an off-chain Prove API and partner-facing Execute API that let existing application contracts emit events on one chain, generate proofs for those events, and validate or execute against them on another chain via the CrossL2ProverV2 contract. The clearest through-line across the docs is that Polymer wants interoperability to look like proving and reusing app-native events, not deploying bridge-specific contracts or routing messages through bespoke gateway logic.
What it does:
Provides a Prove API that accepts source-chain event references and returns proofs developers can use on destination chains
Exposes an onchain CrossL2ProverV2 contract that validates Polymer-supported state roots and returns validated event data to application contracts
Offers an Execute API that combines proof generation with destination-chain execution, positioning Polymer as both proving middleware and a transaction-submission control plane
Supports a wide set of rollups and chains, with docs emphasizing sub-second to low-second proving/execution latency for many rollups and broader mainnet/testnet coverage across EVM and some non-EVM chains
Frames its developer value proposition as “emit once, prove anywhere,” reducing the contract-pair boilerplate and bridge-specific fee logic of traditional cross-chain messaging systems
Key claims:
The official docs say Polymer makes contracts interoperable by proving app-defined events rather than requiring developers to encode logic into bridge payloads or bridge-owned interfaces
The “Polymer at a Glance” docs describe a four-step flow: emit an event, request a proof, submit the proof to a destination contract, and validate/extract the original event data
The docs position validateEvent as the key primitive that lets apps keep their own event schema and logic while still becoming cross-chain
The Execute API docs show Polymer expanding beyond proof generation into managed execution, with partner API keys, funded execution wallets, and one-call proof-plus-execution flows
The supported-chain tables show an unusually broad interoperability surface spanning major rollups, L1s, and selected non-EVM chains such as Solana and Tron
Whitepaper: No canonical standalone Polymer whitepaper or litepaper was found in this pass. The strongest primary sources were the official docs, the docs GitHub repo, and the contract/interface references; see ../whitepapers/polymer-primary-sources-2026-04-27.md.