Bridging
Miden applications can use third-party interoperability providers to move assets between Miden testnet and Ethereum Sepolia.
These are provider integrations available to Miden developers, not Miden-owned bridge products or APIs.
Choose an integration
Agglayer bridge
Integrate directly with Agglayer's bridge lifecycle and the Miden-specific account and note flow.
Epoch intents
Request a quote, authorize the source asset, and let Epoch coordinate destination fulfillment.
| Agglayer | Epoch | |
|---|---|---|
| Typical testnet time | 10–20 minutes | 1–3 minutes |
| Current reference asset | Sepolia ETH ↔ Miden ETH | Epoch test USDC on Sepolia ↔ Miden USDC |
| Integration model | Agglayer bridge transaction and lifecycle | Quote-and-solve intent SDK |
| Provider boundary | Agglayer and its Miden-side integration service | Epoch allocator and solver |
| Best fit | Direct Agglayer interoperability | Faster intent-based USDC movement |
The timing ranges are observations, not service-level agreements. Source finality, provider observation, proof or solver availability, destination settlement, and Miden note synchronization can all affect the final duration.
Choose by asset support, provider trust boundary, recovery model, and the states your application must expose—not timing alone.
Model completion correctly
A cross-chain transfer is not one status. Your application should distinguish:
Source authorization and submission — the user approves and submits the source-chain action.
Provider acceptance — Agglayer observes the bridge action or Epoch accepts the intent.
Destination settlement — the provider completes its destination-chain transaction.
Funds become spendable — the destination wallet discovers and, on Miden, consumes the delivered note.
On Miden, delivery can create a note that the recipient's wallet still needs to discover and consume. Do not report spendable funds only because the provider reports a successful destination transaction.