BCH BLAZEDeck ↗Code ↗
JōgeDOCSPlay

2.3 · A ROUND

Anyone can finish

Lock, settle and pay need no key; the lock and settle have exactly one valid form, and payouts are fixed at settlement. The keeper sends them; so can any browser, so no round depends on one operator.

Only your entry needs a signature. The contracts pin every detail of the steps after it, so the lock our keeper builds is byte for byte the one your browser builds:

PinnedSo that
Exact inputs and outputs, in ordernobody can add, drop or swap a coin
Fixed fees, not ratesevery client computes the same amounts
Version, locktime and sequenceno second version of a step exists
The oracle messages, chosen by sequenceevery client proves the same prices
Each ticket's payout, fixed at settlement; the shared builder pays tickets in outpoint order, 200 at mostevery client pays the same amounts and batches the same way

The contract tests prove it: two clients listing gates and tickets in opposite orders build identical lock, settle and payout transactions. When two parties send the same step, the second sees "already" and moves on.

The buttons

When a step is due and nobody has sent it, the round page offers it: Lock this round, Settle this round or Pay the tickets. Your browser reads the round's coins from public Bitcoin Cash servers and the signed prices straight from General Protocols, builds the step with the keeper's own code, and broadcasts it. No wallet and no fee: the round's budget pays.

The buttons run the same builders as the keeper (apps/web/src/features/round/finish.ts).