Why every token gets its own Lighter account
Separate accounting for each strategy makes balances, funding and redemption liabilities easier to inspect. It does not remove shared infrastructure risk.
Development note · The public app offers a simulated demo and public data views. Lean's real-money launch, trading and redemption services are not enabled. This article explains the implementation being built.
Every Lean token can choose different exposure and launch terms. Keeping those strategies distinguishable is fundamental to showing a holder what their units represent.
The current factory creates a dedicated venue-account contract for each token. The ledger records that token's venue equity, funds in transit, buffer cash and redemption liabilities separately. The intent is to prevent one token's ordinary accounting from silently consuming another token's reserves.
Public venue data is useful evidence, but an API response by itself does not prove a withdrawal or authenticate every NAV input. The implementation checks account and chain identity, tracks finalized receipts and requires separate verification for specific state changes. The full production worker and verifier operation is still being completed.
Separate accounts also have limits. A contract defect, compromised operator, bad shared price input, chain outage or venue failure could affect multiple tokens. Account separation is an accounting boundary, not a promise that every loss is isolated.
When verified records exist, the public token and wallet pages expose the relevant identities and accounting state. Unknown values stay unknown rather than appearing as zero. That distinction is part of making the system inspectable.