Cross-chain bridge development covers the contracts and off-chain components that move tokens or messages from one blockchain to another, and a bridge security audit checks that nobody can make the destination chain accept a transfer that never happened. On smart-contract.com, you describe the bridge once, receive comparable quotes from vetted developers, then from independent auditors who never worked on the code.
A bridge is one of the most demanding kinds of smart contract project. It holds or controls assets on several chains at once, depends on components that live outside any single chain, and has to agree on what counts as a valid message. For that reason, the site's audit model applies its highest project type factor to bridges.
What a bridge project covers
Most bridges combine the same building blocks, whatever the design:
- Source and destination contracts: lock and release, burn and mint, or liquidity pools on each side, with the accounting that keeps supply consistent across chains.
- Message passing: the format of cross-chain messages, nonces, chain identifiers and the handling of retries, failures and refunds.
- Verification layer: the mechanism that proves a message is genuine. It can rely on an external set of validators or signers, an optimistic model with a challenge window, a light client that checks the source chain's consensus, or zero-knowledge proofs.
- Relayers and off-chain services: the processes that watch events, carry messages and submit proofs or signatures.
- Safety controls: rate limits, per-transfer caps, pause functions, timelocks on upgrades and monitoring.
- Tests and documentation: trust assumptions, roles, key management procedures and incident runbooks.
Why bridges are high risk
A bridge concentrates value and trust in a few places, and each one is a target.
- Message verification: if a signature check, a Merkle proof or a light client verification can be bypassed, an attacker can mint or release assets on the destination chain without any deposit on the source chain.
- Validators and relayers: when a set of signers approves messages, the security of the bridge is the security of their private keys. A threshold that is too low, keys held by one operator or weak key rotation procedures are critical risks.
- Replay and ordering: a message accepted twice, or on the wrong chain, breaks the accounting. Nonces, chain IDs and domain separation must be checked everywhere.
- Finality: acting on a source chain event before it is final can let a reorganization undo the deposit after the release.
- Upgrades and admin roles: an upgradeable bridge controlled by a single key can be changed at any time. A multisig with a timelock reduces that risk.
Rate limits and caps do not prevent a flaw, but they bound the loss: a bridge that can only release a limited amount per period gives operators time to detect an incident and pause. The guide on common smart contract vulnerabilities covers several of these patterns.
How it works on smart-contract.com
- Describe the bridge once. The guided request asks for the chains, the assets, the verification model, the state of the code and your budget (minimum 1,000 EUR or USD). An AI drafts a specification that every vendor quotes against.
- Review and invitations. The platform reviews the request, then invites up to 6 matching vendors automatically.
- Comparable quotes. Every quote gives price, currency, duration, scope, team and whether a re-audit is included. An AI assistant working for you compares them, flags scope gaps and unusual prices, and you can message each vendor.
- Independence. The rule is enforced in the database: a company that developed your bridge can never be invited to audit it, and an audit firm engaged on the project cannot then develop it. After development, you can request an independent audit in one click.
The service is free for clients, with no commitment until you choose a vendor. Vendors pay a commission once a contract is declared and confirmed by both parties; project payments never go through the platform.
What drives the price
Audit. In the site's public audit model, a bridge carries a project type factor of 1.6, against 1.35 for DeFi and 0.7 for a token. For Solidity code with partial tests and documentation, at standard urgency and without other risk factors, the model gives:
| Bridge code size | Independent auditors | Established audit firms |
|---|---|---|
| 1,500 nSLOC | 5,600 to 9,800 EUR (7 auditor-days) | 18,000 to 35,000 EUR (10 auditor-days, 2 weeks) |
| 3,000 nSLOC | 11,000 to 20,000 EUR (14 auditor-days, 2 auditors) | 35,000 to 68,000 EUR (19.5 auditor-days, 2 auditors, 2 weeks) |
External integrations and upgradeable contracts each add 10% to the effort, custom math 20%, and Rust, Cairo and other languages carry a factor of 1.3. A re-audit of the fixes adds about 20% to the first audit price. Enter your own figures in the audit cost calculator.
Development. The development model counts 70 to 150 developer-days for a bridge before options, the largest type in the model. Including 15% for project management and QA, that is 81 to 173 developer-days on an EVM chain, or about 53,000 to 190,000 EUR with a Western European vendor and 32,000 to 130,000 EUR with an Eastern European vendor. Each additional chain adds 3 to 6 days. The development cost calculator combines these parameters, and the guide on smart contract audit cost explains the audit model in detail.
How to choose a bridge vendor
For development and audit alike, look for demonstrated work on cross-chain systems, not only on single-chain contracts.
- Auditors: ask how they will review the verification layer, the off-chain relayer and key management, not only the Solidity contracts. Check whether the scope includes every chain's contracts, and whether fuzzing or invariant tests on cross-chain accounting are part of the method.
- Developers: expect a written threat model, explicit trust assumptions, rate limits and pause functions by design, and tests that simulate forged, replayed and out-of-order messages.
- Several reviews: for a bridge that will hold significant value, complementary audits by different firms are common practice.
Red flags: a scope limited to one side of the bridge, off-chain components excluded without explanation, a single key able to upgrade or release funds, or an audit quote with far fewer auditor-days than the code size implies. Browse audit vendors in the directory and the guide on developer and auditor independence.
Related blockchains
Bridges connect ecosystems, so vendors must know each side. Common combinations involve Ethereum and its layer 2 networks such as Arbitrum, Optimism and Base, or ecosystems with native cross-chain messaging such as Cosmos and Polkadot.
Next step
Describe your bridge once, with its chains, verification model and code, and receive comparable quotes from vetted developers or independent auditors. It is free for clients and you commit to nothing until you choose. Start your request.