Architecture
The browser model, wallet connection and contract reference have separate boundaries.
The current release has no live transaction path for the stock, market or reward features. A single deterministic browser ledger powers the app. The native-ETH contract reference is a separate implementation.
System boundaries
| Layer | Responsibility | Cannot do |
|---|---|---|
| Browser engine | Integer accounting, quotes, balances and receipts | Move real funds or fetch live prices |
| Browser storage | Preserve this browser’s ledger between visits | Prove on-chain ownership or shared global state |
| Wallet connection | Read approved address/network; explicit network switch | Sign messages, approve spending or submit FOLD trades |
| ETH contracts | Source implementation for ETH reserve and related roles | Provide the app’s stocks, AMM or staking rewards |
Simulation quantities use six decimal places. The standalone Solidity FOLD token uses 18 decimals. Browser accounting units must not be submitted as on-chain token amounts.
State and persistence
All app pages use the same ledger. Swaps, LP positions, staking, routing, stock trades and redemption update it together. Refresh restores a validated, versioned snapshot from local browser storage.
The app coordinates writes across tabs where browser Web Locks are available. If persistence fails, it shows the failure and keeps current in-memory state; durable saving is not guaranteed. Clearing site data or resetting the model removes the stored scenario.
Receipts and history
Activity retains the latest 500 action receipts, alongside up to 100 epoch records and 120 NAV snapshots. Cumulative account totals are maintained independently of the trimmed display history. Exported JSON identifies the data as a simulation.
A browser receipt is not an on-chain transaction hash. No explorer should be presented as proof of a simulated trade.
Moving beyond the browser
Real deployment requires contract implementations for the desired capabilities, reviewed addresses and bytecode, verified asset/venue connections, funding and transaction handling. A connected EVM address does not complete those integrations.