LightBridge
Near-instant cross-chain bridge across 6 networks. $1M+ moving through it, continuously.
Boba Network is a hybrid Layer 2 blockchain delivering native off-chain data and compute through Account Abstraction. An optimistic rollup rooted in Ethereum and BNB Chain for mass-adoption apps.
Overview
Boba Network is a hybrid Layer 2 blockchain delivering native off-chain data and compute through Account Abstraction. An optimistic rollup rooted in Ethereum and BNB Chain for mass-adoption apps.
What's the challenge?
Optimistic rollups secure value with wait periods; mainstream users want speed. The existing bridge UX was too slow and too complex for the audience Boba wanted to reach. Cross-chain transfers had to feel instant without breaking the trustless fallback, alongside an NFT launch and ongoing Gateway DApp work.
Inherited the prototype, paid the maintenance tax, then paid it down.
We didn't start from a blank slate. We got a prototype never built for the real requirements, and a list of requirements it didn't meet. Each release closed prototype-baked bugs and added what the spec asked for on day one. Maintenance-heavy by design, every fix sat on decisions that weren't ours. So in parallel we simplified the surface sprint by sprint, until what we shipped wasn't patched. It was clean.
What We Did
Constraint: instant feel without giving up trustless settlement. The call: a TypeScript polling service watching AssetReceived events on source chains, batching up to 10 transfers, and submitting AWS-KMS-signed disburseAsset() calls to the destination chain, the disburser key never leaves AWS. Concretely: official LightBridge, TuringMonsters NFT launch, sustained Gateway DApp contributions, plus Account Abstraction, DevOps, and DevRel work. Trade-off: liquidity to mask the wait period.
Outcomes
Cross-chain bridge architecture
The diagram illustrates a simplified high-level architecture and omits confidential implementation and security details.
Cross-chain disbursement flow
sequenceDiagram autonumber participant U as User participant SC as Source Contract participant SG as GraphQL Subgraph participant SV as LightBridge Service participant K as AWS KMS participant DC as Dest Contract U->>SC: deposit(asset, amount, destChainId) SC-->>SG: emit AssetReceived SV->>SG: poll events (60s) SG-->>SV: new AssetReceived[] SV->>SV: batch ≤10, estimate gas SV->>K: sign disburseAsset(tx) K-->>SV: signed tx SV->>DC: submit signed tx DC->>U: release asset to recipient DC-->>SV: tx receipt SV->>SV: persist depositId · emit metrics
What We Learned
Optimistic rollup bridging has an inherent UX tension: security wants wait periods, users want speed. LightBridge taught us how to architect liquidity-provider layers that mask latency for most users while keeping the trustless fallback intact.
Want outcomes like this?
Tell us what you're building. We'll tell you whether we're the right team for it.
Book a call