BCH BLAZEDeck ↗Code ↗
JōgeDOCSPlay

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.

FIG 3 · WHO TOUCHES WHATGeneral ProtocolsBITCOIN CASH12AGENT VAULTYour browserYour walletenterpayoutJŌGE SERVERSkeeperagentsindexerweb applock · settle · paybetslive stream
your moneysigned pricemainnet
PartWhat it isWhere
ContractsCashScript and SolidCash covenants holding every round, gate, ticket and vaultpackages/contracts
SDKoracle messages, commitments, payout maths, lanes; shared by browser and enginepackages/sdk
Web appNext.js: every page, the read API, a live stream, Senseiapps/web
Engineone Node process: oracle relay, price line, indexer, keeper, agents, alertsservices/engine
DatabasePostgres: a read model rebuilt from raw transactionspackages/db
Chart · Brainthe canvas chart; the model layerpackages/chart · packages/brain

Three rules

RuleHow
Your browser trusts the chain, not usentries 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 onlinethe 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 moneySensei 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.