Product status and MVP scope
This is an initial documentation site based on Lots PRD v4, 11 September 2026. Its working description is intended behavior. Neither the PRD nor this site verifies live deployment, successful economic trials, completed audits or legal clearance.
No Lots production contract addresses, transaction links, live support endpoints or audit badges have been invented. A docs build passing is evidence about this website, not the protocol.
Approved MVP behavior
The design includes one-stock or 2–10-stock basket quotes, canonical basket reuse, fully funded minting and complete healthy redemption, fixed-template meme launches, supported buys/sells, same-quote rotation, creator claims, bounded optional buybacks, holdings/recovery views and discovery/moderation.
Existing self-custody wallets are in scope. Compatible multisig and contract-wallet settlement require validation. ETH is the initial routed payment/output option; basket, direct-stock and complete-component routes remain.
Validation still outstanding
| Area | Evidence still needed |
|---|---|
| Launch economics — TBC01 | Exact range/deposit math, both currency orders, first/last trades, endpoints, max/zero creator buys, fixed supply and protected residue |
| Prices and routes — TBC02 | Pinned tokens/feeds/pools/units; valid references; numerical depth/history/deviation/expiry thresholds; complete routes and refunds |
| Rotation — TBC02 | Registered identity checks, same-vault and same-stock cases, rejection of lookalikes/mixed types/self-rotation, both fees and atomic rollback |
| Recovery — TBC03 | Activation denominator, deficits/seizure, early/late claims, later proceeds, permanence and pool-held B under the principal lock |
| Healthy coverage — TBC03 | Floor-rounded aggregate liability at fractional atomic boundaries, split redemption, zero supply and true deficits |
| Legal — TBC04 | Entity, jurisdiction, audience, issuer compatibility, eligibility matrix, lawful exits, full terms and privacy |
| Roles, fees and integration — TBC05–TBC07 | Two-step ownership everywhere including the hook; threshold preservation; prospective fee-wallet changes; version isolation; actual fee reconciliation |
| Opening and buybacks — TBC05–TBC07 | 50 actual-L2-block clock, one-use fee exemption, authenticated caps, 90% hook accounting, bounded execution and atomic burns |
| User experience — TBC08 | Complete journeys and surfaces, mobile/accessibility, novice creator comprehension, immutable uploads, discovery and moderation |
| Independent security | Contract audit and web/API review, critical/high closure, no indirect principal withdrawal or hidden discretionary pool pause |
| Independent in-kind access | Verified interfaces and a minimal client usable without the main site, indexer or offchain signature service |
The referenced initializer's documented dynamic LP-fee update is capped at 10%; this does not by itself implement Lots' approved 90% opening buy fee. Separate hook accounting and integration must be validated. Recovery's current pool-held-basket direction is explicitly unproven, not merely awaiting a UI.
Outside the initial scope
- Basket rebalancing, component substitution and recipe royalties.
- Different-basket, different-stock or mixed-type dedicated rotation.
- User-facing stablecoin payments/outputs and broader unapproved quote assets.
- Funded basket/ETH markets or market-maker programmes.
- Embedded email/social wallets, fiat onramps and integrated bridges.
- Chat, comments, live streams and community takeover of fee rights.
- Integrated creator vesting and post-launch metadata editing.
- An operator-controlled emergency official-pool trading pause.
Separate voluntary token locks are allowed; that does not add integrated vesting to the launch flow. Some current choices have future review items, but those items do not authorize changing an existing launch's committed terms.
What this docs release supplies
The site supplies product explanations, examples, user journeys, mechanics, risks and source context. It uses Docusaurus with standard navigation and minimal styling. It does not implement a trading platform, deploy contracts, supply a minimal contract client or establish a public hosting destination.
As release evidence becomes available, update the relevant claims with verified addresses, version-specific evidence and actual availability. Retain the distinction between approved policy and validated behavior.