The First L1 Where the House
Can't Cheat — and Can't Go Broke.
ExoHash is a Layer 1 blockchain infrastructure for on-chain gaming. Randomness is generated inside consensus. Every bet is collateralized by protocol before it settles.
$100B+ WAGERED ON-CHAIN. FAIRNESS AND SOLVENCY LEFT TO THE APP LAYER.
TODAY: On-chain casinos built on general-purpose chains. None designed for it.
General-purpose blockchains do not provide native randomness.
Current solutions are workarounds:
- • Commit-reveal
- • Oracle-based VRF
- • Contract-level schemes
All introduce latency, cost, or trust assumptions.
Solvency is enforced at the contract level — not the protocol level.
Contracts can be:
- • Poorly audited
- • Incorrectly implemented
- • Blind to worst-case exposure
There is no protocol-enforced solvency standard.
THE SOLUTION IS A CHAIN,
NOT AN APP.
A purpose-built Cosmos SDK L1. Randomness and solvency enforced at consensus — no operator can override them.
RANDOMNESS IN CONSENSUS
Validators collectively generate entropy every block using threshold cryptography. No oracle. No external RNG. No trust in any single party.
The outcome is unknowable until the block finalizes — typically in ~500ms. No one can observe, predict, or manipulate it beforehand.
GUARANTEED SOLVENCY
Before any bet enters the ledger, the protocol computes the worst-case payout and checks the bankroll can cover it.
If the house can't pay, the bet is rejected.No undercollateralized positions. No surprise insolvencies.
WHY COSMOS SDK
ExoHash requires control over the consensus layer.
CometBFT's ABCI++ vote extensions allow validators to generate randomness during block production — not after it. This is typically not feasible without modifying consensus.
IBC provides native bridging for USDC and cross-chain interoperability.
WE DIDN'T WRITE A WHITEPAPER.
WE BUILT THE PROTOCOL.
Live on devnet. WASM game pipeline proven end-to-end. Anyone can build and deploy a game — permissionless.
Provably fair randomness. Built into consensus.
No oracle. No external RNG. No trust in any single party.
Guaranteed solvency. Enforced at the protocol level.
If the house can't pay, the bet is rejected at consensus.
Permissionless game deployment. Pure logic, never touches funds.
WASM binaries, not smart contracts. Anyone can build and deploy — permissionless.
WHO BENEFITS
AND HOW.
The house edge converges to revenue over volume. That revenue flows directly to the participants who secure and capitalize the network — not to a treasury or team wallet.
FROM DEVNET
TO MAINNET.
Two parallel tracks converge at genesis. Growth follows.
Harden. Audit. Launch.
- •Protocol stability and state management
- •Slashing rules and DKG resilience
- •External security audit
- •Tokenomics finalization
- •IBC bridge (USDC)
- •Genesis block
Community ready at genesis.
- •Testnet with production UI and faucet economy
- •UI builder program — open applications
- •Public bankroll LP onboarding
- •Genesis validator set recruitment
From community-driven to operator-driven.
At launch: community-driven system — public bankroll, community UIs, organic traffic.
External operators join permissionlessly.
Own capital. Own traffic. Own frontend.
They use the protocol for what they can't build: randomness, solvency, WASM game layer.
They pay the protocol fee. Each operator adds volume.
GET IN TOUCH.
Pre-mainnet. Recruiting validators, UI builders, and liquidity partners.
Investors, validators, operators, contributors — one form, we'll route it.
- • Strategic investment (seed conversations open)
- • Genesis validator set applications
- • UI builder and operator partnerships
- • Core team (Go, Cosmos SDK, DevOps)
Technical discussion, gaming, protocol updates.