> For the complete documentation index, see [llms.txt](https://cassowary.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cassowary.gitbook.io/docs/architecture-and-100-backing.md). # ⚙️ Architecture & 100% Backing ## Architecture & The 100% Backing Mechanism For experienced DeFi investors, the most critical question is always: *"How is the token backed, and what are the risks?"* Unlike centralized RWA platforms that ask you to blindly trust an off-chain vault, Cassowary uses a transparent, mathematically verifiable architecture powered by Decentralized Perpetual Futures. ### The 50/50 Collateral Split Mechanism To ensure that every minted token (e.g., SPCXw) is 100% backed at all times while maintaining capital efficiency, we utilize a **50/50 Collateral Split** combined with a 2x leverage position on the backend. Here is the exact flow when a user mints 1 SPCXw at a market price of $100: 1. The user deposits **$100 USDC**. 2. The protocol splits this collateral 50/50: * **$50 USDC** is kept securely in the Cassowary Smart Contract Vault. * **$50 USDC** is deployed to Hyperliquid DEX as margin to open a **2x Long Position** (giving exactly $100 of market exposure). Because the exposure ($100) perfectly matches the token supply (1 SPCXw), the system is delta-neutral regarding the backing. 1 SPCXw will always equal the exact value of 1 SPCX share. ### Concrete Examples: Price Variations Let's look at how the 100% backing holds up under different market conditions. #### Scenario A: The Price Goes Up (+50%) * **Market Event:** SPCX price rises from $100 to $150. * **Hyperliquid Position:** The 2x Long position generates a +$50 Profit (PnL). The margin account now holds $100 USDC ($50 initial + $50 PnL). * **Vault:** Holds the original $50 USDC. * **Total Protocol Backing:** $100 (Hyperliquid) + $50 (Vault) = **$150 USDC**. * **User's Token Value:** $150. * **Status:** 100% Backed. #### Scenario B: The Price Goes Down (-40%) * **Market Event:** SPCX price drops from $100 to $60. * **Hyperliquid Position:** The 2x Long position generates a -$40 Loss (PnL). The margin account now holds $10 USDC ($50 initial - $40 PnL). * **Vault:** Holds the original $50 USDC. * **Total Protocol Backing:** $10 USDC (Hyperliquid) + $50 USDC (Vault) = **$60 USDC**. * **User's Token Value:** $60. * **Status:** 100% Backed. ### The Liquidation Scenario (And Why It Doesn't Matter) What happens in the extreme event of a sudden 50% market crash? First, a sudden 50% flash crash is highly uncommon for large-cap equities like SpaceX. Furthermore, as an extra security measure, our protocol actively monitors margin health to rebalance funds and prevent liquidations. However, **even if a liquidation occurs, the system remains 100% solvent.** * **Market Event:** SPCX price drops exactly 50% (from $100 to $50). * **Hyperliquid Position:** The 2x Long position loses $50. The $50 margin is wiped out, and the exchange liquidates the position. Hyperliquid balance is now $0. * **Vault:** Still holds the untouched $50 USDC. * **Total Protocol Backing:** $0 (Hyperliquid) + $50 (Vault) = **$50 USDC**. * **User's Token Value:** $50. * **Status:** 100% Backed. No debt, no insolvency. The math is unbreakable. ### ZERO Liquidation Risk for the User This is the most crucial advantage of **Cassowary**. In older DeFi synthetic models (like MakerDAO or Synthetix), users had to overcollateralize their positions (e.g., deposit $150 to mint $100) and actively manage their own health factor. If the market dropped, the *user* was liquidated and lost their funds. At Cassowary, the user simply holds a spot-equivalent token. **The user can NEVER be liquidated.** The protocol manages the futures architecture on the backend. If you hold 1 SPCXw, you will always hold 1 SPCXw, regardless of market volatility. ### Why Hyperliquid & Arbitrum? We built this architecture using a specific, highly optimized tech stack: * **Hyperliquid (The Engine):** We exclusively use Hyperliquid because it is the deepest, fastest, and most transparent decentralized perpetual exchange in the world. It provides fully on-chain order books, zero centralized manipulation, and the exact liquidity needed to hedge our RWA tokens instantly, with HIP-3 providers such as trade.xyz. * **Arbitrum (The Infrastructure):** We deploy on Arbitrum One because it offers institutional-grade Ethereum security with ultra-low fees. Furthermore, Arbitrum serves as the primary gateway and liquidity bridge to the Hyperliquid ecosystem, ensuring seamless and instant cross-chain operations. ### Cassowary's Advantage By combining Tokenized Futures with a 50/50 collateral split, we offer an RWA platform that is: * **Permissionless & Free:** Anyone can mint, anywhere in the world. * **No KYC:** Total privacy and anonymity. * **No Waiting:** Instant minting directly to your wallet. * **No Opaque Intermediaries:** No centralized brokers holding physical shares. * **No User Liquidation Risk:** Hold your assets with peace of mind. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://cassowary.gitbook.io/docs/architecture-and-100-backing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.