# Experimental YLT emission laboratory Research only, 22 October 2026. No final tokenomics decision. Entry point: [`site/experiments/index.html`](../site/experiments/index.html). The landing page adds one navigation link; `simulator.py`, assumptions, historical files, investor cabinet and its engine are unchanged. Open the experiment HTML directly or serve `site/` with any static server. No build, CDN chart dependency or network needed. ## Inputs reviewed and provenance Reviewed current README, `assumptions.yaml`, `simulator.py`, browser treasury engine/export, data sources/validation, August audit (outdated), October simulation report, decision register and emission allocation discussion, and existing tests. The live landing page at https://yieltop.com returned HTTP 200 and matched the repository landing before the added link. The old audit's “not integrated” claims are superseded by current code. Working documents disagree: older README refers to 48M mining, while 12 October allocation and browser engine use 55M. Experiment default is 55M, editable, with a separate external seed of 5M YLT/$500k. This does not ratify either allocation. Other team/DAO/airdrop/early buckets are excluded. `NAV/YLT` divides by experimental minted supply plus seed, **not total 100M FDV**. Remaining supply means remaining LP mining budget only. The experiment calls the **existing** `YieltopEngine.simulate` over the checked-in `site/app/data.js`, not invented historical data. It retains BTC/ETH prices, Curve/Convex/Stake DAO and Pendle pools, Yield Basis yields, CRV/sdCRV/SDT/CVX/ cvxCRV/YB prices, veYB/vlSDT yields, boost, acquisition costs and CRV routing in that historical calibration run. The UI displays its actual date window, export date, BTC/ETH source, primary/secondary totals and terminal treasury NAV. Current export BTC/ETH source is `yield_basis_file`; this is explicit inherited fallback metadata, not a fresh Yahoo/Binance fetch. Existing CSV simulation results are references, not falsely relabeled future observations. The regression suite checks the browser treasury engine against Python. For each scenario TVL and strategy, re-run that historical engine. Primary monthly rate = mean(income / portfolio TVL); secondary monthly yield = sum(secondary) / sum(treasury NAV). Thus changing TVL recalibrates historical stable dilution and execution effects. All projection months are **synthetic**, use those average rates, and do not repeat or splice historical dates/prices. Future treasury is an aggregate balance, not a future per-asset replay. No future BTC/ETH capital gains are implied. Growth/decline changes external TVL, not a claimed strategy return. Underlying limitations remain: Yield Basis V3 reconstruction before launch; pre-listing YB stand-in and pre-history median locker yields; Curve survivorship; Pendle issuer concentration; fixed locked SDT; assumed execution depths; no Yield Basis capacity dilution. See [data sources](data-sources.md) and [validation](data-validation.md). This is especially material at 500M TVL. ## Emission formulas Monthly zero-based t; S = mining supply; N = selected horizon × 12; q = (1 − annual decay)^(1/12). Scheduled budget b_t = S(1−q)q^t/(1−q^N), or S/N for zero decay. All emissions are capped by unspent supply R_t. - A: scheduled declining quantity b_t, independent of revenue and market price. - B: primary revenue / predetermined reference USD per YLT. This is an explicitly unsafe lifetime comparator; **never** revenue divided by endogenous spot. - C: E_t = min(R_t, carry_t + b_t, primary_t / reference_t, cap_t). - D: same C bounds, with revenue demand multiplied by g_t. For protected duration L (120/180/240 months), cap_t = R_t/(L−t) while t