> For the complete documentation index, see [llms.txt](https://docs.basis.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.basis.pro/whitepaper/metrics-and-reporting.md). # Metrics & Reporting {% 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 %} {% hint style="warning" %} Reporting unit: Dashboard values may be displayed in a USDT-equivalent internal accounting unit for consistency. USDT is not a deposit or withdrawal asset on BASIS. Funding Wallet supports native assets only: BTC, ETH, SOL, PAXG.\ Staking Wallet holds stTokens only: stBTC, stETH, stSOL, stPAXG. {% endhint %} A platform’s credibility depends on whether it reports metrics in a way that: * is internally consistent * cannot be gamed by selective framing * aligns with user outcomes * can be reconciled under stress conditions This section defines how BASIS reports and interprets performance metrics. ## 1) Core reporting principle: net realized yield BASIS focuses on net realized yield. This means: * realized profits from structural alpha capture, funding mechanisms, and onchain yield sources * net of execution costs, venue fees, network fees, and operational overhead * measured first in native asset terms * translated into a USDT-equivalent display unit for reporting consistency Any secondary metric must reconcile to net realized yield. ``` net_realized_yield = realized_gross_profit - execution_costs - venue_fees - network_fees - operational_costs ``` {% hint style="info" %} stTokens are accounting wrappers for staking participation and rewards. Swaps are same-token only at 1:1: * BTC → stBTC * ETH → stETH * SOL → stSOL * PAXG → stPAXG Swap fee: 0.01% {% endhint %} ## 2) APR vs APY {% tabs %} {% tab title="APR" %} APR is a simple annualized rate with no compounding assumption. {% endtab %} {% tab title="APY" %} APY is an annualized rate that assumes compounding. {% endtab %} {% endtabs %} If BASIS reports APY, it must also specify: * compounding frequency * whether compounding is automatic or user-initiated * whether the figure is based on historical windows or live rolling data * whether booster effects are included ### Reporting rule Booster effects must never be blended into a base rate without clear labeling. Booster schedule: | Booster term | Multiplier | | ------------ | ---------: | | 14D | +10% | | 30D | +20% | | 90D | +50% | | 180D | +100% (2×) | For fixed pools, unstaking is only available after the lock-up period ends. There is no early exit option. ## 3) Historical reference vs illustrative example Any numeric example must be labeled as one of the following: | Label | Meaning | | -------------------- | --------------------------------------------- | | Historical reference | Past realized figures from completed periods | | Live rolling metric | Current metric derived from an ongoing window | | Illustrative example | Hypothetical example for explanation only | BASIS should avoid forward-looking promises. Where appropriate, publish ranges or scenario bands instead of single-point expectations. ## 4) Strategy contribution breakdown For sophisticated users, BASIS should report contribution by strategy module. Examples include: * cross-venue structural alpha capture * funding and basis capture * onchain lending or liquidity deployment * PAXG-linked yield modules Costs should also be broken down explicitly: * venue fees * routing slippage * network fees * withdrawal charges * hedging or carry costs This allows users to evaluate where returns came from and how much was consumed by execution. ## 5) Key risk metrics to surface A professional dashboard should track: * system state (Normal / BSCB / DMM) * slippage distribution versus configured bounds * venue incident count and current exposure * funding rate distribution, when perp hedges are used * latency and fill-quality telemetry * intervention count from state machine risk controls * reference price deviation for the USDT-equivalent display unit * spot/reference divergence for PAXG modules {% hint style="info" %} Trust is not created by marketing claims. It is created by deterministic execution, bounded behavior, and transparent exception handling. {% endhint %} ## 6) Reconciliation and auditability For each reporting period, BASIS should be able to reconcile: * starting balances by asset * realized PnL by module * fees and costs by category * ending balances by asset * total rewards credited to users * any pending operational adjustments {% stepper %} {% step %} Record opening balances Capture Funding Wallet and Staking Wallet balances by asset: * BTC, ETH, SOL, PAXG in Funding Wallet * stBTC, stETH, stSOL, stPAXG in Staking Wallet {% endstep %} {% step %} Attribute realized performance Break out realized gains and losses by strategy module, including structural alpha capture, funding, and onchain sources. {% endstep %} {% step %} Deduct costs Deduct execution costs, venue fees, network fees, swap fees, and withdrawal fees. {% endstep %} {% step %} Credit user rewards Rewards accumulate in real time as the same stToken in the Staking Wallet. Upon unstake: * the unstake amount is auto-MAX, full position only * the claimable amount is auto-credited to the Staking Wallet as stToken {% endstep %} {% step %} Verify closing balances Closing balances must reconcile with all credited rewards, fees, and realized strategy outcomes. {% endstep %} {% endstepper %} ## 7) User-facing reporting rules The following conventions must be consistent across the dashboard, statements, and support responses. | Item | Reporting rule | | -------------------------------- | -------------------------------------------------------------------------------- | | Deposit assets | BTC, ETH, SOL, PAXG only | | USDT | Internal accounting and display unit only, not depositable or withdrawable | | BTC deposit flow | Copy the BASIS-assigned BTC address, unique per account, no Web3 wallet required | | ETH / SOL / PAXG deposit flow | Connect a Web3 wallet such as MetaMask | | Minimum BTC deposit | 0.0001 BTC | | Wallet model | Funding Wallet for native assets, Staking Wallet for stTokens | | Reward unit | Rewards accrue as the same stToken in real time | | Swap model | Same-token 1:1 only | | Deposit fee | 0% | | Withdrawal fee | 0.05% | | Swap fee | 0.01% | | BTC withdrawal time | 10 to 60 minutes | | ETH / SOL / PAXG withdrawal time | 1 to 10 minutes | | Unstake behavior | Full position only, auto-MAX | | Fixed pools | Unlock only after the lock-up period ends | ## 8) What credible reporting looks like A credible yield platform does not rely on isolated high-return snapshots. It shows that: * performance reconciles over time * costs are visible * rewards match realized outcomes * risk states are observable * execution quality is measurable * user balances can be audited from start to finish If you want to evaluate whether a yield platform is real, ask whether its numbers still reconcile during volatile markets, degraded venue conditions, and constrained liquidity. That is where reporting standards matter most.