Fairness, odds & authority
The rules the programs enforce, the costs the interface quotes, and the powers the deployer still holds—stated plainly.
outcomes win
Rolls 55 through 100 win. Rolls 1 through 54 lose. The payout is 2× the entered stake net to the player under the supported token tax.
wallets win
One oracle result selects either the creator or joiner. There are no ties, rerolls, or browser-controlled results.
What happens to 100 DICE?
The token’s proposed 3% transfer tax applies as DICE moves. The game uses actual received amounts for solvency, while the advertised winner payout stays net.
The examples use the launch defaults. The game screen reads current rules, and each accepted wager keeps its committed win threshold even if an admin changes future rules.
Accepted in one transaction
- 1Measure the received stakeThe program uses the amount that reached the vault.
- 2Reserve the payout liabilityA wager cannot be accepted beyond configured capacity.
- 3Request ORAO randomnessIf that request fails, the whole acceptance rolls back.
- 4Settle and preserve winningsA failed token delivery leaves a payable claim; it cannot erase a win.
Admin and upgrades
- One deployer wallet initially controls admin functions and program upgrades.
- Configuration locks are independent, one-way, and survive admin transfer.
- Renouncing admin disables remaining admin functions in the current code.
- Removing a Solana program’s upgrade authority makes that deployed code immutable.
Keeping upgrade authority means the deployer can change program code. Configuration locks constrain the current code; they are not the same as program finalization.
Chain configuration and indexed state
- Cluster
- Not configured
- Indexer observation
- No verified onchain snapshot
- Game program
- Not configured
- Reserve program
- Not configured
- DICE mint
- Not configured
- ORAO program
- VRFzZoJdhFWL8rkvu87LpKM3RbcVezpMEc6X5GVDr7y
- Game vault balance
- — DICE
- Reserve vault balance
- — DICE
- Observed transfer-fee rate
- Unknown
- Transfer-fee validation
- Not verified
An observed configuration means the public addresses, transfer-fee configuration, vault balances, and indexer snapshot are readable. It does not prove a live ORAO request or payout; those require a completed onchain game and its transaction history.