There's a strange economic inefficiency sitting at the heart of every Ethereum L2.
Billions of dollars of ETH and stablecoins sit idle in bridge contracts, generating zero yield. They have to be there — they're the exit liquidity guaranteeing that users can always bridge back to L1. But they're just... sitting.
That's the problem we set out to solve with Nexus Network.
The insight
The core insight was simple: bridge funds don't need to be idle to be liquid.
If you can stake 80% of the bridge ETH while keeping 20% as a withdrawal buffer — and you can instantly unstake if that buffer approaches a threshold — you've given the L2 a perpetual yield engine with no additional risk to users.
The tricky part is that most L2 bridge contracts weren't designed with this in mind. They're custodial, single-purpose contracts. Making them "staking-aware" without modifying them directly required a different approach.
The SSV network piece
SSV (Secret Shared Validators) is a protocol that distributes validator key management across multiple operators using Distributed Validator Technology (DVT). Instead of one machine holding a validator key, the key is split across a set of operators using Shamir's secret sharing, and threshold signatures are used to produce validator attestations.
Why does this matter for Nexus?
Because it means we can achieve non-custodial staking from a smart contract. The validator keys are never held by a single party — they're distributed across the SSV operator network. The bridge contract can trigger staking without trusting any intermediary with the validator keys.
The implementation looks roughly like this:
- The L2 bridge contract holds ETH in excess of the withdrawal buffer threshold
- A keeper monitors the balance and triggers a
depositToSSV()call when the surplus is large enough to fill 32 ETH validators - The SSV protocol handles key generation and operator distribution
- Yield flows back to the bridge contract automatically
- If withdrawals are needed, a
triggerUnstake()call queues an exit
The triggerUnstake() → withdrawal queue → available ETH loop takes about 2-4 days on mainnet (the standard Ethereum validator exit period). This is the constraint that determines the withdrawal buffer size.
Raising $1M
We raised a $1M pre-seed from Hashed Emergent, Mask Network, CoinIX, BreakOrbit Ventures, and foundershead.
The fundraising was interesting. Our first 10 conversations with VCs went like this:
Us: "L2 bridge funds are idle and generating no yield." VC: "Yes." Us: "We're going to make them yield-bearing." VC: "How does that help L2 teams?" Us: "They get a revenue stream. They can pass it to their community, use it to fund development, or subsidise gas." VC: "Interesting. But why would they change their bridge architecture?" Us: "They don't have to. We integrate without modifying their contracts."
That last point was the unlock. Once we could demonstrate that adoption required zero changes to existing bridge contracts — just a governance vote to deploy our module — the conversation changed.
The VCs who got it immediately were the ones who understood that L2 teams are essentially running banks without an asset management strategy. Nexus was the asset management layer.
What we built
The final architecture supports:
- ETH staking via SSV network (native staking, not liquid staking derivatives)
- Stablecoin yield via Aave and MakerDAO supply markets
- A configurable withdrawal buffer per asset
- An emergency exit mechanism that can unwind all positions within 7 days
- On-chain attestation of yield distribution to LPs
We deployed on Optimism, Polygon CDK, and Arbitrum Orbit. Each had slightly different bridge contract architectures, which meant writing chain-specific adapters — but the core staking logic is shared.
Lessons
The technical problem was the easy part. The harder problem was convincing L2 teams that this was a priority. Most teams are heads-down on chain performance, developer tooling, and ecosystem growth. "Your bridge funds could be earning yield" doesn't rank high on most sprint backlogs.
DVT changes what's possible. SSV network made this protocol viable. Without non-custodial staking at the smart contract level, you'd need a trusted intermediary — and the trust assumption kills the value proposition for institutional L2 operators.
Under-promise on timelines, especially cross-chain. We underestimated the SSV integration by three weeks. Cross-chain protocols have documentation gaps that you only discover mid-implementation.
Nexus is still live and growing. If you're running or advising an L2 team that wants to put their bridge funds to work, get in touch.
— Rohit