Cross-chain Security Is a Chain Design Decision Now

tl;dr

• Cross-chain failures are usually accounting failures, as most cross-chain systems still rely on an external party to report that a source-chain event happened correctly.
• We built Agglayer, a cross-chain protocol that unifies liquidity and state across connected chains, on a different assumption: every connected chain could be wrong, and the bridge ledger has to balance before value moves.
• Agglayer enforces this with pessimistic proof, a security model that uses cryptography to check the math of every cross-chain movement before it settles, so a faulty chain cannot spend funds it does not have.
• The Open Money Stack is where this matters most: Agglayer is the interop layer beneath every product in the stack, including Polygon CDK chains institutions are already building with.

Cross-chain infrastructure used to be a product checkbox.

• Can users move assets in and out?
• How many chains are supported and how long does it take? 
• How much does it cost?

Those questions still matter. But for institutions, asset issuers, and high-value DeFi teams we work with, they are not the first questions.

The number one question is simpler, but harder to show in production: what security assumptions come with any particular bridge?

Agglayer's answer sets it apart from all cross-chain infrastructure in crypto.

Book a call

From bridge integrations to chain architecture

Most cross-chain systems start as integrations. An application or token issuer chooses a messaging layer, configures a route, selects a verifier model, deploys contracts, and monitors the setup over time.

That can work. It also moves a lot of infrastructure judgment onto the application team.

The team has to understand verifier assumptions. It has to monitor source and destination state. It has to know what happens if one dependency gives a wrong answer. It has to decide whether the same setup is appropriate for a small governance message, a high-value token transfer, or collateral that may end up inside a lending market.

At institutional scale, this is the wrong abstraction.

Cross-chain security should not live as a loose integration next to the chain. For serious money movement, we believe it has to be part of the architecture itself.

That is why we built Agglayer.

Agglayer's security model starts from a different assumption

Agglayer is not another point-to-point bridge.

It is built for connected chains, designed to enable access to shared liquidity and cross-chain execution while preserving each chain's sovereignty. A connected chain keeps its own architecture, rules, governance, and operating model. Agglayer provides the shared infrastructure for assets and messages to move across the network.

The important part is the security model.

Traditional cross-chain systems often depend on a trusted party or group of parties to observe one chain and attest to another. We have seen many versions of this. The names vary. The assumption is similar: some external actor must report that a source-chain event happened correctly.

Agglayer begins with a more pessimistic assumption. Any connected chain could be wrong.

That is why we built Agglayer's pessimistic proof, a security model that assumes every connected chain could be malicious or mistaken and uses ZK to enforce correctness. The proof system tracks bridge accounting across connected chains and enforces a hard constraint: a chain cannot withdraw more than it has deposited. Before a state transition is accepted, Agglayer checks the relevant balances, nullifiers, exit roots, and signatures.

If the math does not work, the transition fails.

That matters because many cross-chain failures are not obvious when you inspect one transaction on one chain. A destination transaction can look valid in isolation while the broader cross-chain accounting is broken. Agglayer verifies the accounting relationship itself.

In plain English: the bridge ledger has to balance before value moves.

Proofs, not operational hope

Agglayer's pessimistic proof generation runs through native validation and zkVM proof generation. It executes the same state transition logic and then proves it cryptographically, using Succinct's SP1 verifier for proof verification.

Constraints include balance conservation, nullifier uniqueness, root consistency, and signature validity.

With Agglayer, invalid cross-chain state cannot settle just because an off-chain actor reported the wrong thing. The proposed state has to satisfy the proof program's accounting constraints. A compromised or faulty chain is contained by its own deposits rather than becoming a network-wide problem.

Why this lives inside the Open Money Stack

The best cross-chain architecture is the one your team does not have to rebuild from scratch.

That is the point of the Open Money Stack, our full platform for moving money onchain through stablecoin settlement, wallets, fiat access, routing, compliance, and dedicated chain infrastructure. Agglayer is an interoperability layer with a proof-verified security model.

With the Open Money Stack, payments and tokenized assets do not need one vendor for wallets, another for ramps, another for compliance, another for routing, another for settlement, and another for cross-chain infrastructure.

Our thesis is to bring all this into one open stack, where each layer hands off cleanly to the next, with teams able to pick and choose what they need.

When a team launches a CDK chain, they get out-of-the-box Agglayer connectivity, if they choose.

The chain can be private by design, configured for institutional controls, optimized for high-throughput payments, and connected to global liquidity without making the operator assemble a separate bridge stack after launch.

Agglayer is a better bridge, because it enables money movement infrastructure that an institution can actually operate on.

The institutional pattern

The clearest signal is what happened during the rsETH exploit in April 2026. A single forged signature on KelpDAO's LayerZero bridge drained $292 million in rsETH, left up to $230 million in bad debt on Aave, and triggered $6.6 billion in withdrawals from Aave inside 24 hours. Lido, SparkLend, Fluid, Upshift, and Ethena paused markets or bridges. rsETH on more than 20 chains became collateral of uncertain backing overnight.

Agglayer kept running and processed roughly $200 million in bridge volume over that window with zero incidents.

Katana, the DeFi chain built on Polygon CDK with native Agglayer connectivity, had zero exposure throughout the weekend. Users could access their funds. Liquidity was where they needed it. Bridging to and from Katana through Agglayer never paused, because there was nothing to pause. The pessimistic proof would have rejected the attack vector before anything moved: a withdrawal of 116,500 rsETH with no corresponding deposit on the ledger fails the accounting check and never settles.

That is the difference between a security model that depends on a committee staying honest under pressure and a security model that requires the math to balance.

The same pattern applies well beyond DeFi, with demand surfacing across every category.

Stablecoin issuers need distribution without fragmented controls. Restaking assets need cross-chain reach without making every destination a new operational risk surface. RWA issuers need a compliance and ownership reference that holds across chains without forcing each chain to rebuild it. Payment companies need dedicated rails without losing access to the networks where liquidity already lives.

Agglayer solves the connection problem with proofs.

The Open Money Stack carries that solution across the layers institutions actually integrate against: chains, wallets, ramps, routing, settlement, and compliance.

From committees to math

Cross-chain infrastructure has entered its institutional phase.

The winning architecture gives risk officers, asset issuers, and chain operators the clearest answers to four questions.

What proves a cross-chain transition is valid?

What prevents a chain or route from spending funds it does not have?

How is damage contained when something goes wrong?

Is cross-chain connectivity native to the architecture, or another integration to manage?

All four get positive checks in Agglayer. The Open Money Stack is how that answer reaches across the layers of money movement, from chains to wallets to settlement.

That is the architecture serious onchain finance needs now.

Build with Polygon CDK: https://polygon.technology/chain-development-kit

Explore Agglayer docs: https://docs.polygon.technology/interoperability/agglayer

Book a call

Disclosures

Certain compliance controls, certifications, and program features are entity-specific and may be subject to change as the Open Money Stack evolves.

Payments services are provided by Coinme, Inc., a licensed U.S. Money Services Business. Polygon Labs provides blockchain infrastructure and wallet technology. Regulatory status, certifications, and program features vary by entity and jurisdiction.