# Introducing Helix Terminal: Institutional DeFi on Canton, Cross-Chain Yield on Stellar Helix Terminal is a Bloomberg-inspired interface for institutional DeFi, built on Canton Network. The protocol enables collateralized debt positions using multi-chain liquid staking tokens as collateral, settling on Canton's privacy-preserving infrastructure — the only public blockchain processing $280B/day in real-world financial transactions with native sub-transaction privacy. The core problem: proof-of-stake token holders are forced to choose between earning yield and maintaining governance participation. Helix Vault issues LSTs across multiple L1 chains that preserve governance rights on origin chains while unlocking those assets for DeFi composability through Canton CDPs. Positions, collateral ratios, and liquidation thresholds remain visible only to relevant parties — a requirement for institutional treasuries operating alongside major financial market participants. Cross-chain yield extends to Stellar through a non-rebasing vault token architecture. Helix issues fixed-quantity vault receipts representing locked L1 staked positions and accrued yield, with rebasing isolated on L1. This design maintains clean pool math and authorization compatibility with Stellar's lending infrastructure, channeling institutional LST liquidity into permissionless isolated lending pools. The composability model — protocol as primitive, integrated by wallets and aggregators — mirrors the modular approach driving the highest retention rates in Stellar DeFi today. ## Demo Video V1: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.helixlabs.org/getting-started-on-helix/introducing-helix-terminal-institutional-defi-on-canton-cross-chain-yield-on-stellar.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.