> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superearn.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How SuperEarn Works

> From Kaia USDT deposit to EarnUSDT minting, vault aggregation, cross-chain routing, and yield flowing back.

<img width="100%" src="https://mintcdn.com/superearn-fe42391a/fIIBQSFfQpvgwMrw/images/superearn-fund-flow.svg?fit=max&auto=format&n=fIIBQSFfQpvgwMrw&q=85&s=101cd761ec64b731c2add41a51030549" data-path="images/superearn-fund-flow.svg" />

***

<Steps>
  <Step title="Before Deposit">
    Users deposit into pre-configured SuperEarn portfolios. If you’d like to understand how the SuperEarn portfolio is managed, please refer to the
    <a href="https://docs.superearn.io/en/protocol/portfolio-allocation-policy" target="_blank" rel="noreferrer">Portfolio allocation policy</a>
    and
    <a href="https://docs.superearn.io/en/protocol/opportunity-set" target="_blank" rel="noreferrer">Portfolio opportunity set</a>
    documents.
  </Step>

  <Step title="Deposit Stablecoins & Mint EarnUSDT (Kaia)">
    <ul>
      <li>The user deposits Kaia USDT through <strong>SuperEarnRouter</strong>; the router moves the funds to the <strong>CooldownVault</strong> and immediately deposits the resulting shares into the <strong>Super Vault</strong> in the same transaction.</li>
      <li>The CooldownVault keeps a 1:1 share-to-asset price, locks assets for pending withdrawals, and enforces the cooldown/loss‑limit rules.</li>

      <li>
        In return, the user receives
        <a href="https://docs.superearn.io/en/protocol/earn-usdt" target="_blank" rel="noreferrer"><strong>EarnUSDT</strong></a>,
        a yield-bearing token that represents their share of the overall SuperEarn portfolio.
      </li>
    </ul>
  </Step>

  <Step title="Aggregation into Super Vault (Kaia)">
    <ul>
      <li>The Super Vault is the <strong>aggregation vault on Kaia</strong>. It already holds the user’s CooldownVault shares from the router deposit and allocates them via strategies.</li>
      <li>Strategy allocations are keeper-driven. The current live strategy on Kaia routes capital to the cross-chain stack via <strong>OriginVault</strong>; Kaia-native strategies can be added by governance.</li>
    </ul>

    1. Allocation to Kaia-native DeFi protocols

    <ul>
      <li>When capital is allocated to Kaia-native DeFi, the Super Vault sends funds <strong>directly into strategy contracts on Kaia</strong>.</li>

      <li>
        These strategies then:

        <ul>
          <li>Deposit into underlying DeFi protocols on Kaia (e.g. lending markets, RWA protocols).</li>

          <li>
            Report their balances and performance back to the Super Vault, so that portfolio tracking, risk limits, and liquidity remain under control.
          </li>
        </ul>
      </li>
    </ul>

    2. Allocation to Multichain via OriginVault (ERC-7540-like)

    <ul>
      <li>When capital is allocated to multichain strategies, the Super Vault deposits into <strong>OriginVault</strong> on Kaia.</li>

      <li>
        <strong>OriginVault</strong> is the <strong>cross-chain hub</strong>:

        <ul>
          <li>It holds USDT that is earmarked for strategies on other chains.</li>
          <li>It follows an <strong>ERC-7540-like async redemption flow</strong> to manage <strong>queued deposits and withdrawals</strong> that need to move across chains.</li>
          <li>It works with the internal bridge/accounting layer to track all “funds in transit”.</li>
          <li>It acts as the single entry point for sending capital to remote vaults on other chains.</li>
        </ul>
      </li>
    </ul>
  </Step>

  <Step title="Cross-Chain Messaging & Bridging">
    <ul>
      <li>
        A messaging component (the
        <a href="https://docs.superearn.io/en/protocol/runespear" target="_blank" rel="noreferrer">Runespear</a> agent) uses
        <strong>Chainlink CCIP\*</strong> (Cross-Chain Interoperability Protocol) to ask OriginVault to send funds to the target chain and to prepare the
        cross-chain message.
      </li>

      <li>
        The cross-chain adapter then uses <strong>Rhino bridge\*\*</strong> as the underlying bridge to:

        <ul>
          <li>Actually move the tokens (e.g. to Ethereum or another yield chain -  Rhino Bridge does not use a burn-and-mint mechanism, it moves native USDT across chains); and</li>

          <li>
            Keep an internal snapshot of:

            <ul>
              <li>how much is in each vault on each chain; and</li>
              <li>how much is currently “in flight” crossing the bridge.</li>
            </ul>
          </li>
        </ul>
      </li>

      <li>
        The accounting module uses the information from CCIP messages and the Rhino bridge adapter to ensure that all balances line up correctly, even if
        <strong>token transfers and messages arrive at slightly different times</strong>, by reconciling:

        <ul>
          <li>per-chain vault balances,</li>
          <li>assets currently in transit across Rhino, and</li>
          <li>final settled balances after CCIP messages are delivered and processed.</li>
        </ul>
      </li>
    </ul>

    *\*[CCIP](https://chain.link/cross-chain) is built on Chainlink’s decentralized oracle network architecture and is designed with a defense-in-depth model, so that cross-chain messages and token movements are not dependent on a single server,
    key, or validator set.*

    *\*\*Rhino is a [Tether / Bitfinex–backed](https://tether.io/news/tether-and-rhinofi-forge-strategic-alliance-to-enhance-usdt-utility-within-defi-prioritizing-user-experience/) cross-chain infrastructure provider that has processed around 6B USD in cumulative transaction volume and has operated cross-chain infrastructure for roughly six years, delivering enterprise-grade uptime and audited stablecoin rails, including KYT checks at execution.*
  </Step>

  <Step title="Yield Generation in Remote Vaults (e.g. Ethereum)">
    <ul>
      <li>On the remote chain (e.g. Ethereum), a <strong>RemoteVault</strong> receives the bridged USDT.</li>

      <li>
        This vault:

        <ul>
          <li>Keeps a small buffer idle for liquidity and can swap to the strategy asset (currently USDT) if needed.</li>

          <li>
            Deploys the rest into the remote <strong>Super Vault</strong> (via SuperEarnRouter), whose strategies are whitelisted yield sources such as MetaMorpho vaults.
          </li>
        </ul>
      </li>

      <li>
        As these strategies earn yield, the value of the Remote Vault increases. That value flows back through OriginVault and the Super Vault, and
        ultimately <strong>shows up as a higher price per share for EarnUSDT on Kaia</strong>.
      </li>
    </ul>
  </Step>

  <Step title="Cooldown, Withdrawals & Safety">
    <ul>
      <li>When a user wants to exit, they <strong>redeem EarnUSDT</strong> on Kaia via <strong>SuperEarnRouter</strong>, which burns Super Vault shares and creates a <strong>cooldown request</strong> in the CooldownVault (no direct user calls to CooldownVault for redeem/deposit).</li>

      <li>
        During this period, the system:

        <ul>
          <li>Brings back liquidity from remote chains through the same cross-chain path.</li>
          <li>Applies checks on maximum loss, slippage, and bridge safety.</li>
        </ul>
      </li>

      <li>Once the cooldown is over and all funds are settled, the request is claimed (permissionlessly, typically by keepers within the configured loss threshold) and the user can <strong>withdraw their stablecoins on Kaia</strong>.</li>
    </ul>
  </Step>
</Steps>