An OP Stack L3 Rollup
Technical Architecture Overview for Alchemy & Infrastructure Partners
The Problem
Cross-chain liquidity today is scattered across dozens of ecosystems, each with its own wrapped assets, bridges, and trust assumptions. Developers who want to build seamless multi-chain experiences face brittle infrastructure, inconsistent asset formats, and fragmented liquidity pools that don't compose across chains.
This fragmentation slows innovation, increases user risk, and prevents the OP Superchain from feeling like a unified environment. Instead of a connected ecosystem, builders inherit a maze of bridges, wrappers, and routing logic that adds complexity at every layer.
The Solution
Imagine a world where chains no longer feel like distant islands, but threads in a single, living fabric. Built as a movement-native OP Stack rollup, Chrysalis gathers fragmented liquidity across chains and draws it into one coherent cross-chain layer — quietly, safely, and without the usual friction of bridges or wrappers.
Assets remain anchored in their canonical home-chain vaults, where their integrity is never in question. Inside the rollup, a Base settlement layer lets every asset move and compose with the same clarity, no matter what chain it originates from. Swaps settle internally on Base, vaults update externally, and users receive true native assets — never synthetics, never abstractions.
The result is a cross-chain environment that feels fluid and intuitive where assets move from one chain to another without the risk of fragmentation, all using a single, unified liquidity layer. This creates a foundation where developers can build multi-chain apps that behave as if the entire Superchain were a single, continuous space.
Movement Layer Flow
Deposit, mint, route, burn, and release — the complete lifecycle of cross‑chain movement during a swap.
Core Architecture
1. Vaults on Home Chains
Native assets remain anchored on their canonical chains with 1:1 collateralization.
- ETH → Ethereum
- USDC → Base
- POL → Polygon
- ARB → Arbitrum
- OP → Optimism
2. b-Assets Inside Chrysalis
A b-Asset is the internal, chain‑agnostic representation of a real asset inside Chrysalis. It is not a wrapped token, not a synthetic, and not a bridged copy. Instead, it is the internal form of an asset whose real collateral remains securely locked on its home chain.
For example, ETH stays on Ethereum, USDC stays on Base, ARB stays on Arbitrum, and so on. Chrysalis never moves these assets across chains. Instead, the vault on each home chain mints a matching b[Asset] inside Chrysalis that represents the real asset 1:1.
In one sentence: a b-Asset is a fully collateralized, chain‑agnostic internal representation of a native asset, used exclusively inside Chrysalis for pricing, routing, and settlement.
How b-Assets Behave
- Minted when a vault locks real assets on their home chain
- Used for internal swaps, routing, and accounting
- Burned when a user withdraws to a home chain
- Always backed 1:1 by real collateral
- Never leave Chrysalis — they exist only inside the rollup
3. Movement Layer
The burn‑mint flow enforces one‑way, verifiable release of real assets.
When a user deposits, the home‑chain vault mints the corresponding b-Asset inside Chrysalis. When a user withdraws, Chrysalis burns the b-Asset and instructs the vault to release the real asset. LP liquidity is never burned — only swap‑created b-Assets can be redeemed.
- Vaults mint b-Assets directly into Chrysalis
- b-Assets move internally through unified pools
- Only swap‑minted b-Assets can be burned for withdrawal
- LP b-Assets remain permanently in the system
4. Unified Liquidity Layer
All liquidity inside Chrysalis is held in b-Asset pools. This creates a single, unified liquidity layer that prices every cross‑chain swap internally. Because everything settles inside the rollup, swaps feel instant and consistent across chains — no fragmentation, no wrapped tokens, no bridge hops.
5. Router
The router orchestrates the entire lifecycle of movement: requesting vault mints, executing internal swaps, burning b-Assets for withdrawals, and coordinating the release of real assets on their home chains. All routing and pricing occur locally on Chrysalis, enabling fast, predictable, sub‑second execution.
In later phases, the router will become yield‑aware: it will be able to route directly between b-YieldAssets, compare yield profiles across providers, and preserve yield‑accruing exposure while moving the assets across chains and staking systems.
The Kinetic Utility Tokenomics of Butterfly (BTFY)
BTFY is the kinetic heartbeat of Chrysalis. Rather than inflating on a fixed schedule, the token emerges in rhythm with the network’s movement. When cross‑chain activity surges, emissions expand. When the ecosystem rests, emissions soften. The supply grows like a living organism responding to its environment.
Every day, Chrysalis observes how liquidity flows across chains and assigns a weight to each pool based on how vital it was to routing. Pools that carry more movement earn a greater share of BTFY. After the first 24 hours of network activity, liquidity providers begin receiving BTFY continuously, second by second.
Circulating supply increases only through these daily emissions, and the market determines BTFY’s value based on the amount released and the demand for it.
Markets Chrysalis Unlocks
| Market Type | Example Pairs |
|---|---|
| Governance ↔ Governance | ARB ↔ OP, POL ↔ ARB, OP ↔ ETH |
| Stable ↔ Governance | USDC ↔ ARB, USDC ↔ OP, DAI ↔ POL |
| Culture ↔ Infrastructure | DEGEN ↔ ETH, TOSHI ↔ OP, BRETT ↔ ARB |
| Infrastructure ↔ Infrastructure | ETH ↔ OP, ETH ↔ ARB, ETH ↔ POL |
| Emission‑Directed Markets | BTFY ↔ ETH, BTFY ↔ USDC, BTFY ↔ OP |
| Combinatorial Expansion | Each new vault unlocks N↔N markets across Ethereum, Base, Polygon, Arbitrum, and Optimism |
Swap Performance & Latency
- Underlying assets never bridge
- b[Assets] are minted instantly
- Routing executes locally on OP Stack
- Vault release is one‑way, not round‑trip
The Yield-Bearing Market Phase
Chrysalis will enable direct routing between yield‑accruing assets across chains. Instead of swapping into non‑yielding intermediaries, users can move from one yield‑bearing position to another with no wrapping, rebasing, or fragmentation. Each vault mints a b-YieldAsset that tracks value growth internally while the underlying asset continues earning yield on its home chain.
| Yield Asset | Yield ↔ Yield Markets |
|---|---|
| stETH (Lido) | stETH ↔ rETH, stETH ↔ wstETH, stETH ↔ sfrxETH |
| rETH (Rocket Pool) | rETH ↔ stETH, rETH ↔ wstETH, rETH ↔ sfrxETH |
| wstETH (Lido Wrapped) | wstETH ↔ stETH, wstETH ↔ rETH, wstETH ↔ sfrxETH |
| sfrxETH (Frax) | sfrxETH ↔ stETH, sfrxETH ↔ rETH, sfrxETH ↔ wstETH |
| cbETH (Coinbase) | cbETH ↔ stETH, cbETH ↔ rETH, cbETH ↔ wstETH, cbETH ↔ sfrxETH |
Yield‑bearing routing turns Chrysalis into a unified yield layer, where users can shift between staking providers, yield profiles, and risk models across chains — all without ever leaving a yield‑accruing position.
Why OP Stack?
OP Stack provides EVM equivalence, native messaging, modular rollup architecture, and L1 security inheritance — all essential for Chrysalis’s unified liquidity model.
As a movement‑native rollup, Chrysalis depends on predictable execution, fast settlement, and a shared security model that spans the entire Superchain. OP Stack delivers this through standardized tooling, cross‑chain interoperability, and a battle‑tested upgrade path that ensures long‑term stability.
By building on OP Stack, Chrysalis becomes instantly composable with the broader Superchain — enabling seamless routing between Ethereum, Base, Optimism, Arbitrum, Polygon, and other chains without reinventing infrastructure.
Why Alchemy?
Alchemy provides high‑performance RPC, cross‑chain indexing, analytics, and rollup hosting required to operate Chrysalis at scale.
Chrysalis relies on precise vault state, fast block propagation, and reliable cross‑chain data to coordinate minting, burning, and routing. Alchemy’s infrastructure ensures that every vault update, swap event, and liquidity movement is captured instantly and consistently across chains.
With Alchemy’s Rollup‑as‑a‑Service stack, Chrysalis gains enterprise‑grade uptime, observability, and developer tooling — allowing the protocol to scale from early routing volume to a global liquidity layer without re‑architecting its foundation.
Deployment Plan
Phase 1 — Rollup Initialization
- Launch Chrysalis OP Stack rollup with base configuration
- Deploy core registries (Vault Registry, Movement Registry)
- Deploy Router contract and internal accounting modules
- Deploy genesis liquidity pools (bETH ↔ bUSDC, bUSDC ↔ bUSDT, etc.)
Phase 2 — Vault Deployment Across Chains
- Deploy vault contracts on Ethereum, Base, Polygon, Arbitrum, and Optimism
- Register each vault with the Chrysalis Vault Registry
- Enable minting of b-Assets for each supported native asset
- Begin cross‑chain movement validation and burn‑mint flow testing
Phase 3 — Liquidity Activation
- Open LP deposits into unified b-Asset pools
- Enable internal routing and native‑to‑native swaps
- Activate arbitrage and routing incentives for price alignment
- Begin real‑time monitoring of pool health and vault collateralization
Phase 4 — Yield‑Bearing Expansion
- Onboard yield‑bearing vaults (stETH, rETH, cbETH, wstETH, sfrxETH, mETH, etc.)
- Introduce b-YieldAsset representations for yield‑accruing collateral
- Enable cross‑chain movement of yield‑bearing assets without wrapping or fragmentation
- Display real‑time yield growth inside Chrysalis via internal accounting
- Allow LPs to earn both native yield and BTFY emissions simultaneously
- Unlock new markets: stETH ↔ OP, rETH ↔ ARB, wstETH ↔ POL, sfrxETH ↔ ETH
- Integrate yield‑aware routing so swaps consider both price and yield opportunity
Phase 5 — Chain Expansion
- Add new vaults for additional EVM assets as demand grows
- Expand routing graph and unlock new N↔N cross‑chain markets
- Integrate partner dApps via the Routing API and SDK
- Prepare for non‑EVM expansion (Cosmos, Solana) in later phases