Atomic execution for cross-chain agents. No bridges. No custodians.
Tesseract is the open-source atomic-composability protocol for cross-chain agents and DeFi. Autonomous agents route across many L2s at once — Tesseract settles their intents all-or-nothing across Ethereum, Polygon, Arbitrum, Optimism, and Base: MEV-protected, flash-loan resistant, resolved in under thirty seconds. No bridges, no wrapped IOUs.
Tesseract is an open-source, cross-rollup atomic-composability protocol that gives agents and DeFi all-or-nothing execution across Ethereum L2s. It is the atomic-execution layer for cross-chain intents — not a bridge. Users and agents keep native assets on each chain, and a swap group either resolves everywhere within a deadline window or refunds everywhere.
It is built on seven audit-grade Vyper contracts and a high-performance Rust relayer, with commit-reveal MEV protection and flash-loan-resistant resolution delays — without bridges, wrapped assets, or custodial intermediaries. It maps to the 2026 agent-economy narrative of atomic composability and intents: autonomous agents operate across many rollups at once and need deterministic, all-or-nothing outcomes, not fragile bridge hops. Supported at launch: Ethereum, Polygon, Arbitrum, Optimism, and Base. MIT-licensed.
Agents act across many rollups. Execution isn't atomic.
Liquidity — and increasingly autonomous agents — are spread across every rollup. To act across the gap you either bridge (locking real assets in a honeypot vault and taking a wrapped IOU with depeg risk) or chain multiple hops, each with its own latency and its own way to strand you mid-flight. For an agent executing one decision across three chains, a leg that lands here and reverts there leaves a broken, half-executed position. The two dominant answers — custodial bridges and generic messaging fabrics — both bottom out on someone off-chain staying honest.
The Tesseract solution
One intent. Atomic outcome. No trusted party.
Tesseract expresses a cross-rollup trade or agent intent as an atomic swap group bound by a shared swap_group_id. Every leg commits as a hash first (MEV bots see nothing), reveals a block later, and resolves after a 2-block delay. All legs resolve within the deadline, or all refund — a deterministic, all-or-nothing outcome an agent can rely on. Assets never leave their home chain; there is no vault to drain and no quorum to socially engineer.
Architecture
Seven Vyper contracts. One Rust relayer. Zero off-chain trust.
Tesseract is built deliberately small. Every feature below is enforced in code on the rollup itself — not gated by a multisig, a validator quorum, or an optimistic dispute window.
Commit-reveal MEV shield
Every swap is buffered as a hash commitment first and revealed only after the next block. Searchers, sequencers, and sandwich bots see nothing useful in the mempool — your trade lands at the price you signed for, not the price someone reorganised the block for.
Atomic swap groups — intent settlement
Express a cross-chain intent as one atomic group: a multi-leg trade across three rollups either executes everywhere or refunds everywhere. The TesseractBuffer contract enforces group atomicity at the protocol layer, so an autonomous agent gets an all-or-nothing outcome — partial fills, stranded collateral, and half-finished cross-chain routes simply cannot happen.
Built for autonomous cross-chain agents
Agents that route capital across many L2s at once cannot afford a leg that lands on one chain and reverts on another. Tesseract gives them a single primitive — commit the group, get resolve-everywhere-or-refund-everywhere — so an agent submits one intent and settles a deterministic outcome, not a pile of independent bridge transactions each with its own failure mode.
Flash-loan resistance, built-in
A mandatory 2-block resolution delay (configurable up to your chain finality) makes single-block flash loan exploits structurally impossible. Combined with role-gated resolution and a circuit breaker after 50 consecutive failures, the buffer hardens the surface attackers usually target.
Rust relayer with chain-aware finality
A high-throughput Rust relayer monitors 4+ chains in parallel over WebSocket with HTTP failover, tracks per-chain confirmation rules, and recovers stuck nonces automatically. Auto-scales 2–10 instances on CPU and persists state in PostgreSQL — not in someone's memory.
No bridges. No wrapped IOUs.
Tesseract coordinates native swaps directly on each rollup. Users hold real assets, not bridge receipts. There is no honeypot multisig, no canonical-vs-wrapped fragmentation, and no $600M failure mode waiting to be exploited.
Order book + partial fills
AtomicSwapCoordinator gives makers and takers a real on-chain order book with configurable slippage tolerance and partial fill support. Settle 500 USDC of a 1000 USDC order without forcing the entire trade through.
On-chain governance & staking
The TESS token powers protocol governance, fee discounts up to 50%, and staking rewards from 5% to 15% APY based on lock duration. Fees flow through an on-chain FeeCollector — transparent, auditable, no opaque off-chain treasury.
Three phases, all enforced by Vyper on each rollup. The relayer submits transactions; it never authorises them.
01
Commit
Each leg submits keccak(payload ‖ secret) with a shared swap_group_id and a deadline. The mempool shows only opaque bytes — nothing to front-run.
02
Reveal
One block later, the user reveals the plaintext. The contract checks the hash. Block ordering is already settled, so the reveal is safe to make public.
03
Resolve or refund
After the 2-block delay, every leg resolves — or, if any leg misses its deadline, every leg becomes refundable. No stuck mid-flight state.
create a swap group · relayer client (Rust)
let group = SwapGroup::new()
.leg(Chain::Arbitrum, give(usdc, 1_000))
.leg(Chain::Base, take(weth, 0.31))
.deadline(Duration::from_secs(30));
// commit-reveal is handled per leg
let receipt = relayer.submit(group).await?;
assert!(receipt.resolved_or_refunded());
What is atomic composability, and why do cross-chain agents need it?
+
Atomic composability means an action that spans multiple rollups either completes everywhere or completes nowhere — no state where one leg has settled and another has not. Autonomous agents in 2026 route capital and execute strategies across many L2s simultaneously; a bridge hop that lands on one chain and reverts on another leaves them holding a broken position. Tesseract gives agents a single all-or-nothing primitive: submit a cross-chain intent as an atomic swap group and get a deterministic resolve-everywhere-or-refund-everywhere outcome.
How is Tesseract different from a bridge?
+
A bridge moves an asset from chain A to chain B by locking the original and minting a wrapped copy. Tesseract never moves assets across chains — it coordinates simultaneous, atomic swaps already happening on each chain. There is no lock contract to drain, no wrapped IOU to depeg, and no validator quorum that can be socially engineered. That is the difference between a message-passing bridge and an atomic-composability layer.
Can I use Tesseract as the execution layer for an agent or intent framework?
+
Yes — that is the primary design target. An agent (or an intent solver on its behalf) expresses the desired cross-chain outcome as an atomic swap group bound by a shared swap_group_id and a deadline. The Vyper contracts enforce that the whole group resolves or the whole group refunds, so the agent settles a deterministic outcome rather than orchestrating and unwinding independent bridge transactions. The Rust relayer submits the legs but has no authority to force a resolution the contracts do not already permit.
What stops MEV bots from front-running my swap?
+
Swaps are submitted as a keccak commitment hiding the payload. The reveal can only happen after the commitment is included on-chain, and resolution requires a further 2-block delay. A searcher reading the mempool sees opaque bytes; by the time the payload is public, the block ordering is already settled.
Which chains are supported?
+
At launch: Ethereum, Polygon, Arbitrum, Optimism, and Base — both mainnets and their testnets (Sepolia, Amoy). Adding a new EVM rollup is a matter of deploying the seven Vyper contracts and pointing a relayer instance at the RPC.
Clone the repo, run the 135-test suite, deploy to testnet in fifteen minutes. The protocol is open source, the contracts are audit-ready, and the documentation is honest about what's done and what isn't.