# BIVB & stTokens (1:1 Quantity Peg) {% hint style="info" %} Operator and jurisdiction: BASIS is operated by BASIS DIGITAL INFRASTRUCTURE LTD, a Seychelles IBC (LEI: [254900IX2F2KCWNSSS64](https://lei.bloomberg.com/leis/view/254900IX2F2KCWNSSS64)). Research Partner: Base58 Labs contributes execution research, systems modeling, and risk design. {% endhint %} BASIS uses a tokenized staking representation layer so users can: * deposit native assets * move capital from the Funding Wallet into the Staking Wallet * track principal and rewards with deterministic accounting * withdraw through controlled on-chain procedures This layer is called BIVB, BASIS Iso-Value Bridge. ## Wallet model | Wallet | Holds | Purpose | | -------------- | --------------------------- | --------------------------------------------------- | | Funding Wallet | BTC, ETH, SOL, PAXG | Deposit and withdraw native assets | | Staking Wallet | stBTC, stETH, stSOL, stPAXG | Stake, track rewards, and manage productive capital | ## 1) What BIVB does BIVB converts native assets in the Funding Wallet into staking representations in the Staking Wallet. | Native asset | Staking representation | Deposit method | Swap rule | | ------------ | ---------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------- | | BTC | stBTC | Copy your BASIS-assigned BTC address. Each account receives a unique deposit address. No Web3 wallet is required. | 1 BTC ↔ 1 stBTC | | ETH | stETH | Connect a Web3 wallet such as MetaMask or another compatible wallet. | 1 ETH ↔ 1 stETH | | SOL | stSOL | Connect a compatible Solana wallet such as Phantom. | 1 SOL ↔ 1 stSOL | | PAXG | stPAXG | Connect a Web3 wallet such as MetaMask or another compatible wallet. | 1 PAXG ↔ 1 stPAXG | Only same-token swaps are supported. | Asset | Staked Token | | ----- | ------------ | | BTC | stBTC | | ETH | stETH | | SOL | stSOL | | PAXG | stPAXG | Cross-asset conversion is not part of BIVB. ## 2) The 1:1 peg is about quantity, not fiat value BIVB enforces quantity preservation: * 1 BTC ↔ 1 stBTC * 1 ETH ↔ 1 stETH * 1 SOL ↔ 1 stSOL * 1 PAXG ↔ 1 stPAXG This is a quantity peg, not a fiat-value guarantee. If a user increases BTC quantity through rewards, the displayed USDT-equivalent value can still decrease if the BTC market price falls. The same logic applies to ETH, SOL, and PAXG. {% hint style="warning" %} USDT is used for internal valuation and interface display only. It cannot be deposited, swapped in from outside, or withdrawn from BASIS. {% endhint %} ## 3) Why BASIS uses stTokens instead of simple balances stTokens provide: * explicit separation between available capital and allocated capital * deterministic accounting for staking principal and rewards * clean same-token exit semantics, swap back to native asset, then withdraw on-chain * auditable state transitions under math-constrained system rules * compatibility with BASIS execution infrastructure for structural alpha capture This separation is important for system safety. BASIS runs proprietary routing infrastructure designed for execution precision, including BHLE characteristics such as sub-50μs latency and 100K+ OPS. Even with high-throughput execution, asset accounting remains deterministic at the token-quantity level. ## 4) Practical user flow {% tabs %} {% tab title="Deposit" %} 1. Move native assets into your Funding Wallet. 2. For BTC, send funds to your BASIS-assigned BTC deposit address. 3. For ETH, SOL, and PAXG, connect a compatible Web3 wallet and deposit on-chain. 4. Deposit fee is 0%. No minimum deposit {% endtab %} {% tab title="Swap and stake" %} 1. In the Funding Wallet, swap the native asset to its matching stToken. 2. Swap is always 1:1 within the same asset line. 3. Swap fee is 0.01%. 4. The resulting stToken appears in the Staking Wallet. 5. Stake from the Staking Wallet into the selected pool. Rewards accumulate in real time as the same stToken in the Staking Wallet view. {% endtab %} {% tab title="Unstake and withdraw" %} 1. Fixed pools can be unstaked only after the lock-up period ends. 2. Early exit is not available. 3. Unstake is full-position only. The interface applies auto-MAX to the entire staked position. 4. On unstake, the full claimable amount is auto-credited to the Staking Wallet as the same stToken. 5. Swap the stToken back to the matching native asset at 1:1. 6. Withdraw the native asset from the Funding Wallet. Withdrawal fee is 0.05%. {% endtab %} {% endtabs %} ## 5) Fees and processing times | Action | Fee | Notes | | ---------- | ----- | --------------------------------- | | Deposit | 0% | Native assets only | | Swap | 0.01% | Same-token only, native ↔ stToken | | Withdrawal | 0.05% | Native assets only | | Asset | Typical withdrawal time | | ----- | ----------------------- | | BTC | 10 to 60 minutes | | ETH | 1 to 10 minutes | | SOL | 1 to 10 minutes | | PAXG | 1 to 10 minutes | ## 6) Booster and rewards context BIVB defines how principal and rewards are represented. Reward multipliers are applied at the staking layer, not by changing the 1:1 quantity peg. Current Booster schedule: | Lock period | Booster | | ----------- | ------- | | 14D | +10% | | 30D | +20% | | 90D | +50% | | 180D | +100% | The 1:1 swap rule remains unchanged regardless of Booster selection. ## 7) Risk and trust implications Because stTokens represent allocated capital: * the risk profile is tied to the active strategy framework and operational controls * reward generation can slow or pause under protective system states * on-chain withdrawals follow asset-specific processing windows * quantity accounting remains deterministic even during stressed conditions BASIS is designed around: * deterministic execution * math constraints * state machine risk controls * auditable wallet separation * research-backed systems design through Base58 Labs These controls support structural alpha capture while keeping principal representation clear and operationally constrained. {% hint style="success" %} Key rule To exit, the sequence is always: stToken → matching native asset → on-chain withdrawal {% endhint %} BIVB defines how principal is tracked. The Risk Model explains how the system behaves under stress. --- # 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.basis.pro/whitepaper/bivb-and-sttokens.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.