The cross-chain conversation usually fixates on fees, latency, and security. But as the number of chains accelerates—especially application-specific chains (appchains)—the most practical bottleneck has become distribution: how quickly an interoperability stack can add new chains without weeks of negotiation, governance cycles, or bespoke engineering. Concero Labs’ Lanca Bridging Framework (LBF) is designed around that reality, because it is built on Concero V2 Messaging—a messaging layer explicitly engineered for permissionless, rapid chain onboarding.
The new bottleneck is not “bridging”—it’s “chain support”
Interoperability is increasingly constrained by an uncomfortable gap: the ecosystem has expanded into hundreds (and now thousands) of networks, while major interoperability providers still integrate chains at a far slower pace. Concero’s own analysis points to the scale of the mismatch—over a thousand EVM-compatible chains, while even the largest interoperability stacks cover only a fraction.
This matters because liquidity, users, and applications no longer cluster on a small handful of L1s and rollups. Appchains are launched to own execution, distribution, or specialised environments—and they expect infrastructure to keep up. When chain onboarding takes weeks, interoperability becomes the limiting reagent for expansion.
Concero Messaging: a distribution layer built for appchain-scale growth
Concero V2 Messaging (also referred to as “Motherboard”) reframes interoperability as a modular marketplace of specialised actors—relayers, verifiers, and RPC providers—assembled per transaction, rather than a closed network controlled by a single integration gatekeeper.
The practical consequence—and the part that matters most for LBF—is chain onboarding. Motherboard explicitly targets non-discriminatory distribution with permissionless scaling to new chains in under 20 minutes, with deployment cost stated as less than $1. Lanca co-founder and CTO Oleg Kron describes the same direction of travel: turning chain onboarding into a modular, repeatable process intended to remove “integration as a bottleneck,” with an emphasis on reducing the business-model friction that typically surrounds chain additions. (blog.okron.cc)
In other words, Concero Messaging is built for an “internet-like” expansion curve—where new networks can join quickly and permissionlessly—because the system assumes appchains will keep multiplying. (Concero Blog)
Why this is LBF’s biggest advantage
LBF is not “just another bridge.” It is a bridging framework whose core operations are powered by Concero V2 Messaging. Lanca’s documentation is explicit: LBF’s Parent–Child Pool architecture (and its dynamic IOU mechanism) runs on top of Concero V2 Messaging for secure cross-chain communication. (docs.lanca.io)
That inheritance is decisive. Most bridge stacks must first clear an internal decision process to add a chain (often involving commercial terms, validator-set coordination, or governance timelocks), and only then ship the technical integration. LBF, by contrast, is positioned to follow Concero Messaging onto new chains at the tempo appchains demand: if a chain can be onboarded to the messaging layer in minutes, the bridge is no longer stuck in a multi-week onboarding queue.
This is a structural advantage, which brings:
- Faster chain coverage reduces “unsupported chain” dead ends for applications expanding to new networks.
- Earlier presence on emerging chains increases the chance of becoming the default liquidity route before fragmentation hardens.
- A credible path to permissionless expansion reduces a hidden cost of interoperability: the time and uncertainty of getting added.
Minutes vs. weeks: how onboarding compares in practice
To understand why “permissionless onboarding in minutes” is meaningfully different, it helps to look at the constraints competitors inherit. The point is not that every integration always takes the same amount of time, but that the processes are not designed for consistent, appchain-scale onboarding.
- Wormhole: its governance proposal process (WIP-2) imposes a minimum multi-step timeline—community comment period, snapshot/temperature check, review, formal voting, delays, and timelocks—that totals ~22 days before counting any engineering, testing, or guardian coordination. Separately, Wormhole’s Guardian Set model requires operational coordination to run and validate new chain infrastructure, which adds practical latency beyond governance minimums.
- Axelar: chain onboarding is explicitly coupled to governance approval and validator readiness. Axelar’s Interchain Amplifier governance materials outline a forum discussion period and voting cycle, followed by operational provisioning across validators—steps that make “under a month” integrations unrealistic in typical conditions. (Axelar) The Monad integration illustrates this compounding overhead: multiple governance proposals were required for distinct onboarding components before activation could proceed. 7 8 9 10 11
- LayerZero / Stargate (2025 EVM evidence): LayerZero does not publish a standardised chain onboarding process, so the most reliable public proxy is a three-event sequence: (1) Endpoint deployment on the target chain → (2) Stargate repository update → (3) official announcement. This ranges from single-digit days in best cases (e.g., 0G: 3 days, Unichain: 6 days) to multiple weeks (e.g., Camp: 18 days, Doma: 33 days, Apex Fusion: 55 days) and longer in outliers (e.g., Hedera: 88 days, Sophon: 166 days). 12 13 14 15 16 17 18 19 20 21 Importantly, these figures exclude any time spent in private negotiations and do not capture engineering effort for non-EVM environments—meaning the measured latency is a conservative, public-facing baseline rather than a worst case.
Against that reality, a <20-minute, <$1, permissionless chain onboarding target is not a small UX improvement. It is a different distribution model.
The compounding effect: scalable chain support amplifies LBF’s other strengths
The chain-onboarding edge is not isolated; it multiplies the value of LBF’s bridging design.
Because LBF uses a unified Parent–Child liquidity system with a dynamic IOU mechanism, it is architected to reduce liquidity fragmentation as it expands—so adding chains does not inherently mean recreating siloed liquidity islands on every network. (docs.lanca.io)
That matters because many bridging systems can add chains only by accepting one (or both) of these outcomes:
- slow chain integration (coverage lags demand), or
- fast integration that produces shallow, fragmented liquidity on new networks.
LBF’s roadmap pairing—rapid chain onboarding via Concero Messaging plus capital-efficient liquidity via Parent–Child + IOUs—is explicitly aimed at avoiding that trap.
Why the market should care
In a world where new chains appear continuously, the “best bridge” is increasingly the one that can show up everywhere, quickly, without permission, while still behaving like serious infrastructure. Concero Messaging was built to make chain onboarding cheap, fast, and modular. LBF is built to capitalise on that distribution layer by turning new-chain reach into usable bridging capacity, rather than a long tail of partially supported networks.
If appchains are the dominant scaling path, then interoperability winners will be chosen as much by integration velocity as by security engineering. LBF’s most defensible innovation is that it treats chain support as a first-class design constraint—then solves it at the messaging layer, where the integration bottleneck actually lives.
