Cross-Chain

Cross-Chain Bridge Development

We engineered Boba Network's official bridge with their team and kept it running. Most teams asking for a bridge do not need one, and we will say so.

Get in touch → See case studies →

Cancel any week. Last week refunded if we didn't blow you away. No hours tracked.

6 chains Networks supported by LightBridge, Boba Network's official bridge See the case study
$1M+ Moving through it, secured in production See the case study
Live Inherited as a prototype, hardened into production infrastructure See the case study

// 01

What We Do

Bridges are the highest-consequence infrastructure in Web3. The first question is always whether you need one at all.

Build, Integrate, or Neither

The assessment that comes before any bridge work.

Existing messaging protocol versus custom infrastructure
Canonical bridge where one already exists
Designs that remove the cross-chain requirement
Honest read on whether the bridge is the product

Bridge Implementation

The architecture we ran in production on LightBridge.

Event watchers on source chains
Batched transfers with replay protection
Signed disbursement on the destination chain
Multi-network support without per-chain forks

Key Custody and Signing

Bridges get drained through keys far more often than through clever maths.

Signing keys in AWS KMS, never leaving the boundary
Least-privilege operational access
Rate limits and per-transfer caps
Pause conditions and incident runbooks

Liquidity and Finality

The operational reality that decides whether a bridge feels instant.

Liquidity provisioning and rebalancing
Finality assumptions per chain
Reorg handling and confirmation depth
Fee model and relayer economics

Takeover and Stabilization

We inherited LightBridge as a prototype rather than starting clean.

Audit of an existing bridge codebase
Maintenance debt paid down while live
Weak architectural decisions replaced progressively
Monitoring and on-call under retainer

// 02

How we approach cross-chain work

LightBridge is Boba Network’s official cross-chain bridge: six networks, near-instant transfers, seven figures secured on mainnet. We did not start it from scratch, and we did not do it alone. Engineering inside Boba’s build, we inherited a prototype, paid down its maintenance debt, and replaced the weak decisions while it stayed live and held real money. That experience is mostly why we start engagements by trying to talk clients out of custom bridges. Our reasoning on the security trade-offs is in the cross-chain bridge security decision, and the hub is Web3 and blockchain development.

// 03

When your product should not use a bridge

A custom bridge is the most dangerous thing you can build in this space, and the historical losses are not subtle. Do not build one when a canonical bridge already connects your chains, when an existing messaging protocol covers your case, or when the real requirement is that users hold an asset on one chain rather than move it between two. Often the honest answer is to deploy on fewer chains. We would rather lose the engagement than build infrastructure that becomes the largest single risk in your product.

Considering a bridge, or running one already?

Tell us which chains and what has to move. The first answer is often that you do not need to build it, and that answer is free.

Get a quote

// proof

Proof, not promises

6 chains Network support

Engineered Boba's official LightBridge with their team: 6-chain near-instant transfers, $1M+ secured in production.

Typescript Python GraphQL

2 months Concept to Pilot-Ready

PoS + web crypto checkout, multi-chain, wallet-agnostic, pilot-ready for merchant integration in 2 months.

React Typescript NestJS

3 SDKs Backend · Contract · Frontend

Three-layer Hybrid Compute SDK suite (backend, contract, frontend), built with Boba's team against undocumented infra, still in …

Typescript Solidity Hardhat

These are selected projects, not our full portfolio. We have shipped 75+ products since 2018.

What clients say

Google

THE agency to go for blockchain development. Super experienced and highly professional team. Love to work with them.

Richard Leitgeb

Original

For technical questions on blockchain and NFT, I always come back to Kevin. He has familiarized himself very well in this area, and the expertise he brings is certainly essential for projects like these. I can only recommend everyone get in touch with Kevin on these topics.

Fritz Fahringer Klarheit vor KI

Trustpilot

Experts in smart contract development.

Original

Independently rated 4.5/5 on Trustpilot Read the reviews

Clutch Top Blockchain Company in Austria 2026 award for Wavect

Verified on Clutch · 2026 Top Blockchain Company in Austria View our Clutch profile

Clutch Top Web3 Development in Austria 2026 award for Wavect

Verified on Clutch · 2026 Top Web3 Development in Austria View our Clutch profile

FAQs

Honest answers about bridge delivery

How does the weekly cancellation actually work? +

End any week, with one message. No notice period, no exit interview, no fine print. We invoice weekly, so the most you’re ever committed to is the current week.

What if I'm not blown away by the work? +

It’s in your contract: tell us, and we refund that week. No questions, no invoices to dispute, no calls to escalate. The only rule: refunds apply to the most recent week.

Why don't you track hours? +

Because hours are the wrong metric. If we’re optimizing for hours billed, we’re not optimizing for your outcome. The deal is simpler: every week, we earn the next one. If we don’t, you don’t pay. We’re free to spend zero hours or sixty. What matters is whether you’re blown away.

What does 'expectations detached from reality' mean? +

We work with operators, not lottery winners. If a request would require breaking physics, the law, or a third party’s systems, we say so, and if we can’t align, we walk. The guarantee is mutual: you can fire us any week; we can also fire ourselves.

Should we build a custom bridge or integrate an existing protocol? +

Integrate, in most cases. A general-purpose messaging protocol or the canonical bridge for your chains carries a fraction of the risk and effort. Custom becomes justified when you are the chain, when the flows are unusual enough that no protocol fits, or when the bridge itself is the product. We start every engagement with that assessment rather than with an implementation quote.

What does a cross-chain bridge cost to build and operate? +

Custom bridge work is infrastructure, so it starts around €100k and 3-6 months, and that is only the build. The part teams underestimate is operation: liquidity you have to fund, relayer gas, monitoring, on-call, and the audit you cannot skip. Budget for the running cost before you commit to the build, because a bridge nobody is watching is worse than no bridge.

How do you keep the signing keys safe? +

On LightBridge the disburser key never leaves AWS KMS. A polling service watches AssetReceived events on the source chains, batches transfers, and submits KMS-signed disbursement calls on the destination chain. Most bridge losses come from key compromise and privileged access, not from exotic cryptography, so that is where the design effort goes.

Can you take over a bridge somebody else built? +

Yes, and we have. LightBridge came to us as an inherited prototype and we hardened it into production infrastructure while it kept running. We begin with a read of the codebase, the key custody model, and the monitoring, then give you an honest assessment of whether hardening or replacing is the cheaper path.

How many chains can you support? +

LightBridge runs across six networks. The limit in practice is not the code, it is the operational burden: each additional chain adds liquidity to fund, finality behaviour to handle, and another surface to monitor. We would rather support the chains where your users actually are than advertise a longer list.

// More in

More in Web3 & Blockchain

Web3 & Blockchain

The hub: dApps, payments, scaling and the chains we ship on. Routes to the capability you actually need.

Smart Contract Development

Solidity and Rust from architecture through mainnet, with third-party audit coordination and monitoring.

Account Abstraction

ERC-4337 smart accounts, paymasters, session keys and recovery. Three production SDKs behind us.

Web3 Wallets

Smart, embedded and invisible wallets, plus MetaMask Snaps. Non-custodial by default.

Zero-Knowledge

Privacy by cryptographic proof, not policy: ZK identity, private transactions, and ZK rollups.

// Get to know us

Get to know us

Long-term relationships over quick wins.

Read our Blog

No BS Around Tech Podcast

Get some Impressions