Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

What is Concero?

Concero is an open, permissionless messaging protocol that enables secure, cross-chain communication.

Originally conceived as a tightly integrated system, Concero has evolved into a modular platform where applications choose how messages are delivered and verified between supported networks.

Why Concero?

  • Open composition — Applications can choose their own relayer and verifier modules per message.
  • Secure by design — Messages are cryptographically verified and then authenticated/asserted by destination contracts.
  • Cross-chain compatibility — Concero connects multiple blockchains through a unified interface.
  • Composable architecture — Developers can integrate Concero at different levels: infrastructure, protocol, or application layer.

How it works

Concero is built around the concept of flexible message security — empowering applications to define their own trust and verification assumptions.

Every message passing through Concero can be independently configured with a custom security stack, giving developers granular control over how messages are verified and accepted.

Key features of Concero Messaging:

  • Customizable block confirmations Each message can specify its own finality rules. Applications may require a certain number of block confirmations (e.g. 6 on Ethereum, 12 on Polygon), or rely on native chain finality mechanisms like BFT consensus or finalized checkpoints.

  • Multi-RPC verification Verification pipelines can use one or more RPC endpoints to fetch and cross-check chain state, reducing reliance on a single provider.

  • Verifier diversity Messages can be verified using one or more pluggable verifier libraries — from simple block hash matching to full signature-based verification or even light clients. Verifier modules are fully modular.

  • App-defined quorum rules Applications can define their own consensus logic — such as "at least 2 of 3 trusted verifiers must agree".

Concero does not enforce a single trust model. Instead, it provides the primitives — verifiers (currently named validatorLibs in the contract interface), codecs, relayers, and message rules — allowing developers to assemble the security architecture that matches their risk profile and application needs.

Use cases

  • Decentralized applications that need secure cross-chain function calls
  • Token bridging protocols requiring trust-minimized relaying
  • Oracle networks for cross-chain data feeds

Concero is not a service — it's a protocol that anyone can run and extend.