Chrysalis v1 Overview
Technical overview of Chrysalis v1, a multichain liquid-staking app that routes deposits from supported EVM and Ripple/XRPL networks through CCIP, CCTP, or Axelar ITS.
Chrysalis v1 treats "stake from anywhere" as a routing problem rather than a single-chain integration. Each supported source network is paired with exactly one bridging protocol - Chainlink CCIP, Circle CCTP, or Axelar's Interchain Token Service - chosen for what that network actually supports, and the app exposes only the route that's valid for the network the wallet is connected to. Nothing is inferred at the UI layer; the network-to-protocol mapping is explicit configuration.
How a stake moves
- Wallet connection. EVM wallets connect through Wagmi + ConnectKit; Ripple/XRPL wallets connect through Crossmark.
- Protocol resolution. The app reads the active network and looks up which bridge protocol - CCIP, CCTP, or Axelar ITS - is configured for it, along with the correct source asset, chain ID, and contract addresses.
- Deposit and approval. EVM routes stake USDC; the Ripple route stakes XRP.
- Cross-chain settlement. The deposit is bridged to Ethereum Sepolia, the destination context, through the resolved protocol. A protocol-specific status manager tracks the transfer until it settles - polling CCIP's transaction explorer, Circle's Iris attestation API, or Axelar's transfer status, depending on the route.
- Position becomes visible. Once settled, the destination-side staking position is reflected on the dashboard in ETH/stETH terms. Ripple-originated stakes additionally mint an XRPL NFT as an on-chain staking receipt.
Why three protocols instead of one
No single bridge protocol covers every network Chrysalis wants to support at acceptable cost and finality. CCIP is used where its EVM-to-EVM lane coverage and message guarantees are the strongest fit; CCTP is used for USDC-native burn-and-mint routes where Circle's attestation model applies; Axelar ITS is the one that actually reaches Ripple/XRPL, which the other two don't support at all. The tradeoff is that the frontend has to carry protocol-specific status logic for all three rather than integrating once - covered in the architecture page.
Technical FAQ
What is Chrysalis v1?
Chrysalis v1 is a multichain liquid-staking application that routes staking deposits from supported EVM and Ripple/XRPL networks through the configured bridge for that network.
Which bridge protocols does Chrysalis v1 use?
The visible documentation describes Chainlink CCIP, Circle CCTP, and Axelar Interchain Token Service as route dependencies.
Does the UI infer bridge routes automatically?
No. The original docs state that the network-to-protocol mapping is explicit configuration rather than UI inference.
Which wallets are mentioned for Chrysalis v1?
The docs mention Wagmi and ConnectKit for EVM wallets and Crossmark for Ripple/XRPL wallets.
What should developers verify before production use?
Developers should verify supported networks, bridge contracts, source assets, settlement assumptions, and current dependency versions from the codebase or official Raum sources.