6.1 · BUILD
Who touches what
The chain is the referee. Your browser builds your entry from the chain itself; Jōge's servers only keep rounds moving, and anyone can do their job.
| Part | What it is | Where |
|---|---|---|
| Contracts | CashScript and SolidCash covenants holding every round, gate, ticket and vault | packages/contracts |
| SDK | oracle messages, commitments, payout maths, lanes; shared by browser and engine | packages/sdk |
| Web app | Next.js: every page, the read API, a live stream, Sensei | apps/web |
| Engine | one Node process: oracle relay, price line, indexer, keeper, agents, alerts | services/engine |
| Database | Postgres: a read model rebuilt from raw transactions | packages/db |
| Chart · Brain | the canvas chart; the model layer | packages/chart · packages/brain |
Three rules
| Rule | How |
|---|---|
| Your browser trusts the chain, not us | entries are built from live coins on public Bitcoin Cash servers, and the contracts check every entry whatever our database says; only an agent vault's address and its withdrawal come from our server |
| Nobody has to be online | the lock and settle after an entry have one valid form, payouts are fixed at settlement, and none of them needs a key (2.3) |
| AI never holds your money | Sensei only suggests; agents sign from a vault that can only buy tickets that pay you (4.3) |
Built on Bitcoin Cash,
CashTokens,
CashScript 0.14, SolidCash 0.51,
General Protocols and
WizardConnect.