Strengthen your bridge with ZK verification.
Most cross-chain systems still rely on offchain observers to say an origin-chain event happened and is final. Boundless adds a cryptographic verification layer to that model, starting with out-of-the-box LayerZero DVN support today.
Most cross-chain systems diversify operators. They still share similar trust assumptions.
LayerZero calls them DVNs. Wormhole calls them Guardians. Others use validators or DONs. The pattern is similar: offchain actors observe an origin-chain event, decide it is irreversible, and attest to it on the destination chain.
The KelpDAO exploit made the failure mode plain. An attacker poisoned the RPC nodes a configured LayerZero DVN relied on for source-chain data. The attestation looked valid to the destination system because the observer had already been fooled.
That is not unique to one bridge. Most modern cross-chain systems still reduce to operator honesty and infrastructure integrity at the moment they decide what happened on the source chain.
Boundless changes the evidence, not just the operator set. A ZK-backed verifier path reduces to validator signatures, proof verification, and circuit soundness. It is slower than the fastest trust-based path, but it is materially harder to spoof in the same way.
The point is not just more walls. The point is walls whose holes do not line up.
If the main hole is poisoned observation, there is only one wall to get through.
Three walls are better than one. If all three still depend on similar observation infrastructure, one path can remain.
The trust-based walls can stay. Once the last wall reduces to proof verification and validator signatures, the same RPC path no longer makes it through end to end.
The goal is not to remove every trust-based path. The goal is to build a system where high-value routes can require stronger evidence, while faster routes still keep practical latency. Boundless-DVN is the current LayerZero packaging of that model.
Same packet flow. Stronger evidence at the verification step.
Out-of-the-box LayerZero support is live in alpha today.
This Sepolia ↔ Base Sepolia corridor proves the packaged LayerZero path today: packet emission, proof request, destination verification, and delivery. Boundless is the broader cross-chain verification product; this alpha shows the current LayerZero implementation surface.
Safe cross-chain systems should be tiered: faster paths for routine flow, heavier proofs for higher-value routes.
The mistake is to talk about ZK as if it were one fixed latency profile. It is not. Trust-based paths remain the speed tier. Helios, Steel, and similar systems are the fast cryptographic tier. Full finality is the premium tier. The numbers below come from measured or benchmarked paths we use for this product.
The right system mixes these modes instead of forcing one proof depth everywhere. Fast routes can keep trust-based attestation. Higher-value routes can require a Helios-class proof. The routes that justify it can step up again to full finality. That is how the system becomes both safer and practical.
Destination-side on-chain verify() remains roughly ~35K gas on L2s, with L1 routes quoted separately. That cost sits underneath every proof tier.
One proof covers every message in its window. Batch your outbound flow and per-message cost collapses toward the verify gas.
A Helios proof covers a ~27-hour sync-committee window. A Signal proof covers a finality event on Ethereum mainnet. A blobstream0 proof can cover 1,000+ Cosmos headers at the same cycle cost as one. You don't pay per-message — you pay per proof, and the proof is shared across every message the verifier path attests in that window.
These are current benchmark-backed ranges, not promised sticker prices. Actual route pricing depends on proof tier, message frequency, destination-chain gas, and whether the route warrants dedicated capacity.
The proof systems are audited, the proving market is live, and the integration model already works.
One LayerZero setConfig() tx. No bridge replacement.
Boundless is the broader cross-chain verification product. Boundless-DVN is the packaged LayerZero integration today. On supported LayerZero routes, you add it as an enforced verifier layer without replacing your bridge or touching OApp code. Snippet below is illustrative — exact values depend on your OApp's DVN set and route set.
- Live alpha
- Ethereum Sepolia → Base Sepolia
- Packaged today
- LayerZero OFTs on enabled routes
- Route rollout
- Corridor by corridor, based on proof path
- Pricing
- Proof-tier dependent, marketplace pass-through
- SLAs / volume terms
- By conversation
// 1. Boundless-DVN is already deployed for you on the destination chain.// Share the route you want to secure and we provide the current addresses.address constant BOUNDLESS_DVN = 0x0000_...9AF2; // Base mainnetaddress constant LZ_LABS_DVN = 0x589D...5BE8; // keep your existing required DVNUlnConfig memory cfg = UlnConfig({confirmations: 15,requiredDVNCount: 1,optionalDVNCount: 1,optionalDVNThreshold: 1, // message cannot commit without ZK proofrequiredDVNs: toArray(LZ_LABS_DVN),optionalDVNs: toArray(BOUNDLESS_DVN)});SetConfigParam[] memory params = new SetConfigParam[](1);params[0] = SetConfigParam({eid: BASE_EID,configType: 2, // ULN configconfig: abi.encode(cfg)});// 2. One tx, OApp-owner signed.ILayerZeroEndpointV2(ENDPOINT_V2).setConfig(oapp, receiveLib, params);