# Super OETH (superOETHb)
## Introduction to Super OETH Super OETH combines liquid staking yield from Ethereum with AMM rewards found on Base. Super OETH offers users ETH staking rewards bridged to Base using CCIP. As a supercharged version of Origin's flagship liquid staking token, Super OETH inherits most of its code from [OETH](https://docs.originprotocol.com/yield-bearing-tokens/oeth) and benefits from its multi-year track record of safety and numerous [audits](https://docs.originprotocol.com/security-and-risk/audits). Super OETH shares Origin's unified governance framework. Protocol upgrades, strategy changes, and parameter updates are governed by xOGN holders on Ethereum Mainnet, consistent with OETH and all other Origin products. Both products are rebasing ERC-20 tokens that grow automatically in your wallet as ETH yield is harvested and auto-compounded. While Super OETH's staking yield comes from Ethereum via Chainlink's [CCIP](https://chain.link/cross-chain), its peg is ensured by the protocol maintaining a deep liquidity on a native AMM pool pairing WETH with Super OETH. This allows for anyone to sell Super OETH for WETH with low slippage at any time. It also enables the protocol to earn incentives from AMMs, which are harvested back into WETH and distributed to Super OETH holders. This combination of Beacon Chain yield and auto-compounded rewards create a safe and compelling yield token that is fully backed by ETH. As with all of Origin's products, protocol revenue and other value generated by Super OETH accrues back to [OGN](https://docs.originprotocol.com/ogn/staking). ## Super OETH Design Origin's Supercharged liquid staking token on Base is superOETHb, which derives Beacon Chain yield from bridged Wrapped [OETH](https://docs.originprotocol.com/yield-bearing-tokens/oeth) and earns rewards from AMMs through a protocol-owned liquidity positions on Base. ### **Protocol Owned Liquidity** The rewards generated by Super OETH are closely tied to AMM flywheels and Beacon chain staking rewards. By deploying protocol owned liquidity on AMMs, Super OETH is able to ensure an extremely tight peg to ETH. The Super OETH [AMO](https://docs.originprotocol.com/yield-bearing-tokens/core-concepts/amo) holds a portion of the protocol's underlying collateral in liquidity pools, ensuring instant exits with low slippage. This allows anyone to sell superOETHb into the pool for nearly 1.00 ETH before trading fees. As a result of these large liquidity positions, Super OETH earns incentive tokens that are harvested and distributed to superOETHb holders every day in the form of additional yield. Combined with Beacon Chain staking yield from bridged wOETH, these rewards generate strong APYs for Super OETH never before seen in a low-risk liquid staking token. ### Redemptions For most exits, superOETHb can be swapped for WETH through the superOETHb/WETH Curve pool on Base at near 1:1 with low slippage. For redemptions that exceed available AMM depth, the Super OETH Vault processes exits through a tiered sequence: 1. Vault buffer — 10 minutes. Redemptions are first sourced from liquidity held in the vault buffer. If the buffer covers the requested amount, the redemption is processed 10 minutes after the request is initiated. 2. Curve AMO withdrawal — up to 10 days. If the buffer is insufficient, the Guardian multisig (2-of-8) may withdraw liquidity from the protocol-owned superOETHb/WETH Curve pool on Base to satisfy the redemption when liquidity conditions permit. 3. Beacon chain unstaking — up to 10 days. Wehn liquidity conditions do not permit for AMO funds to be withdrawn from the pool, ETH is sourced from staked validator balances on Ethereum Mainnet. Redemptions processed through this path are subject to Ethereum's validator exit queue and may take up to 10 days. Users can initiate redemption requests through the , which routes to the most efficient available exit path automatically. ### Chainlink CCIP: Security & Resilience Super OETH relies on Chainlink's Cross-Chain Interoperability Protocol (CCIP) to deliver ETH staking yield from Ethereum Mainnet to Base, where it is distributed to superOETHb holders through the daily rebase. CCIP is the sole bridge used for yield delivery. Chainlink CCIP has undergone rigorous, multi-party security audits, including reviews by Code4rena, Deloitte & Touche (SOC 2 Type 1 and Type 2), and Chainlink's internal security team. The protocol is built on defense-in-depth principles and is powered by Chainlink's oracle infrastructure, which has a demonstrated track record of securing tens of billions of dollars in assets and enabling over $14 trillion in onchain transaction value. Super OETH collateral is held on Ethereum Mainnet rather than bridged to Base. This limits the value in transit over CCIP at any given time: collateral is only bridged when vault liquidity is required to process redemptions that AMO pool depth cannot satisfy. Under normal conditions, the value exposed to CCIP is a small fraction of total TVL. In the event of a CCIP outage, yield updates to superOETHb balances would pause until the bridge resumes and the next rebase occurs. Yield continues to accrue at the validator level on Ethereum during any outage; it is the delivery of that yield to Base that is temporarily suspended. The peg is unaffected: Super OETH maintains its ETH parity through protocol-owned AMO liquidity on\ Base, which operates independently of CCIP. Holders can continue to exit at near 1:1 through the AMO pool regardless of bridge status. ### Performance Fee Origin charges a 20% performance fee on yield generated on Super OETH. This fee is deducted from gross yield before distributions are made to depositors; it does not apply to principal. Net protocol fees after operating expenses are directed to OGN buybacks, which flow to xOGN stakers, creating a direct link between protocol revenue and token holder value. The APYs displayed on Origin's analytics dashboard and third-party tracking platforms reflect net returns after this fee has been applied, so the figures represent what depositors actually earn. --- # 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.originprotocol.com/yield-bearing-tokens/super-oeth-superoethb.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.