Run Highroll

Deploy the contracts

Deploy, check every link, then open the first round.

Check your version

The contracts still use the working name Gigapot (for example Gigapot and GigapotLens). This reference follows contract code e1056f7. The test network runs older code from 19 September (8a20efb). The launch contracts add fee bands, a Backer allowlist, prize minimums and the 25% jackpot; their calls will be listed here once the audited ABI is final. Use the ABI that matches the contracts you call.

The three steps#

Deploy and link. The core, its modules, three linked libraries, the verifier and program keys.
Stop and review. Bytecode, custody, roles and ABI, before anyone gets control.
Fund and start. Add starting money, open the first round, then test a purchase all the way to payment.

Deploy and link#

Link TierPricing, EpochAccounting and RoundPipeline into the Gigapot core contract. Deploy TicketRights, FeeVault, PythDrawSource, RelayGateway, GigapotLens, the SP1 Groth16 verifier and, if used, EarnVault.

Wiring steps
Part	Call	Check
Verifier	Set the three SP1 program keys	Compiler, proof system, source version and public-value formats match.
FeeVault	`initialise(core)`	Then `core.setFeeVault(...)`. Don’t skip either.
Core	`setTicketRights / setDrawSource`	Rights and randomness point at this core.
Roles	`setTreasuryRoute / setProtocolFeeRecipient / setGuardian`	Also review `setSettlementOperator` and ownership.
Record	Save the evidence	Compiler and link settings, all three library addresses, ABIs, source commit, constructor inputs, keys, roles and receipts.

Review#

Verify every linked bytecode and module pointer. The launch plan separates a Safe and timelock owner, a pause-only guardian, limited treasury roles and an optional settlement operator. Confirm only the owner can unpause. Don’t assume the plan is what’s deployed.

Fund and start#

Approve the core. The starting Backer approves the exact amount.
deposit(amount) Fund the starting pool while currentRound is 0.
start(firstCloseTime) The owner opens round 1 with reviewed settings and a future deadline.
Test everything. Buy, queue, prove, draw, settle, verify, publish a claim tree, claim a slice and withdraw.

Heads up

A deployed verifier isn’t a finished end-to-end test. Run the full test on the exact deployment, then get an independent review.