> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How the Polymer Prover Works

> Cross-chain verification using Polymer's IBC-based messaging

The Polymer Prover enables cross-chain intent verification using Polymer's IBC-based messaging infrastructure. It uses light client proofs for settlement verification, extending `MessageBridgeProver` for common proving functionality.

## Architecture

```mermaid theme={null}
graph LR
    subgraph Destination [Destination Chain]
        DP[Portal] --> DPr[PolymerProver]
        DPr --> DIBC[Polymer IBC]
    end

    DIBC -->|"Light client proof"| SIBC[Polymer IBC]

    subgraph Source [Source Chain]
        SIBC --> SPr[PolymerProver]
        SPr --> SP[Portal]
    end
```

## How It Works

1. **Fulfillment**: Solver fulfills the intent on the destination chain Portal
2. **Proof dispatch**: The Polymer Prover on the destination chain sends a message via Polymer's IBC transport
3. **Light client verification**: Polymer uses IBC light client proofs to verify the message on the source chain, no external validator set required
4. **Settlement**: The source chain Polymer Prover receives the verified message and marks the intent as proven, allowing the solver to withdraw rewards

## Security Model

Polymer's security derives from IBC light client proofs, the same cryptographic verification mechanism used across the Cosmos ecosystem. Rather than relying on a set of external validators or an attestation service, light clients verify state transitions directly, providing trust-minimized cross-chain communication.

## Message Format

Polymer Prover uses the same standardized message format as other Eco bridge provers:

* **8 bytes**: Destination chain ID
* **64 bytes per intent**: `[intentHash (32 bytes)][claimant (32 bytes)]`

Multiple intents can be batched into a single IBC message.

## When to Use Polymer Prover

**Ideal for:**

* Cross-chain intents where IBC-based verification is preferred
* Chains with Polymer IBC support
* Use cases that benefit from light-client-based trust minimization

**For other cross-chain options, see:**

* [Hyperlane Prover](/routes/architecture/provers/hyperlane)
* [LayerZero Prover](/routes/architecture/provers/layerzero)
* [Local Prover](/routes/architecture/provers/local) for same-chain intents