HOME
Frequently_Asked

QUESTIONS
& ANSWERS.

Technical architecture, business model, competitive landscape, and roadmap — answered directly.

1. What are you building and why?

Two industries. Zero overlap.

iGaming — a multi-billion dollar market with real players, real money, and real demand. But every operator runs the same Web2 stack: server-generated outcomes, trust-based solvency, withdrawal queues, annual audits.

Blockchain — the tools to make outcomes verifiable, solvency enforceable, and settlement instant. But no chain was ever designed for gaming. General-purpose L1s treat randomness and solvency as application-layer problems.

Nobody built the bridge.

ExoHash is that bridge — a sovereign L1 where randomness is generated inside consensus by the validator set, solvency is enforced by protocol before every bet, and settlement happens in the next block. The infrastructure that replaces traditional Web2 gaming.

2. Why a new L1? Why not build on Ethereum, Solana, or Cosmos Hub?

We tried. In 2025 we deployed full on-chain settlement on Polygon, then Sei. Thousands of rounds on mainnet. Hit three structural limits:

  • 1. Commit-reveal needed two transactions per round.
  • 2. Gas and nonce management required a dedicated backend.
  • 3. Selective reveal was a real attack vector.

Randomness has to live inside consensus, not in an oracle callback. Solvency has to be a protocol rule, not a smart contract that can be paused or upgraded.

That's why it's a sovereign Cosmos SDK chain — we control the state machine.

3. Where do the validators come from? Is this Cosmos Hub?

ExoHash is a sovereign chain — it has its own validator set, independent of Cosmos Hub. Validators run our custom binary (exohashd), not the Cosmos Hub binary.

Think of it like Osmosis or dYdX — built with Cosmos SDK, but a fully independent network with its own consensus, its own validators, and its own governance.

The Cosmos SDK is the framework (like Rails or Django). The chain is the application. We use CometBFT for consensus and IBC for cross-chain communication, but we are not part of the Cosmos Hub validator set.

Genesis validator set: 32 validators at launch, scaling to independent operators as the network matures. Validators are incentivized with a share of protocol revenue, paid in USDC.

4. Can validators collude? What if someone tries to take over the validator set?

Validators have equal voting power — one validator, one vote. Bond size doesn't matter. The BLS threshold requires 2/3 of validators to produce valid randomness. With 32 validators, an attacker needs to compromise 22 of them.

At genesis, validators are invited by the foundation — similar to how Noble (Cosmos USDC issuer) launched with a permissioned proof-of-authority set. As the network grows, new validators join through governance — existing validators vote to admit new ones.

This is a fundamentally different model from stake-weighted systems where a single entity with enough capital can dominate the validator set.

5. How does the randomness work technically?

Validators run a Distributed Key Generation (DKG) protocol — they collectively create a shared BLS key. No single validator holds the full key.

Every block, each validator signs the block height with their key share. The block proposer combines any 2/3 of these shares using Lagrange interpolation into one aggregate signature. That signature is verified against the group public key.

Randomness = SHA256(aggregate signature). 32 bytes. Deterministic, unpredictable, bias-resistant, and verifiable on-chain.

Partial signatures are propagated via ABCI++ vote extensions and aggregated by the block proposer before finalization.

Same cryptography as drand — used by Cloudflare and Protocol Labs. The difference: drand is an external service. Ours is embedded in consensus. No oracle call. No latency. No external oracle trust assumption.

6. How do games work?

Every game is a WASM plugin — a small binary (~500 lines of Rust or Go) that handles pure math and logic. The game never touches funds — the protocol handles escrow, solvency, and settlement.

Build with the ExoHash Game SDK. Deploy with one transaction. No chain upgrade required.

Before deployment, an auditor agent automatically verifies the binary: checks for deterministic execution, validates house edge bounds, confirms correct use of host functions (reserve, settle, RNG), and verifies no unauthorized fund access. The agent signs the binary with a governed public key stored on-chain — updatable via governance, not controlled by any single party.

Anyone can build and deploy a game — permissionless. The protocol ensures it plays fair before it goes live.

7. What's the business model? How does ExoHash make money?

Protocol takes a fee on every bet settled on-chain — split to validators and EXOH stakers in USDC.

All fees denominated and settled in USDC. Zero inflationary token emissions. Real yield from real wagering volume, not from printing tokens.

Revenue is purely volume-driven with zero exposure to game outcome volatility.

8. Can the house go bankrupt?

The house takes game-outcome risk — if players win more than they lose, the bankroll shrinks. That's normal and expected. Over volume, the house edge ensures the bankroll grows.

What the protocol guarantees: every bet is fully collateralized before it settles. Before a bet enters the ledger, the protocol computes the worst-case payout and reserves that amount from the bankroll escrow. If the bankroll can't cover it, the bet is rejected.

Bankroll funds are held in on-chain escrow — not in an operator's wallet, not in a multisig, not in a database. Payouts are capped to the reserved amount. The bankroll balance can never go negative.

No undercollateralized bets. No IOUs. No "pending balance." Every payout is backed by locked funds before the bet even starts.

9. How do you handle regulation?

Separation of concerns — three entities:

  • ExoHash Foundation — protocol governance & token oversight
  • ExoHash R&D — certified infrastructure (RNG, solvency). B2B licensed.
  • ExoGames — game studio. Licenses games to operators.

GLI-19 certification path confirmed with GLI leadership — first in class.

Licensing process in progress — jurisdiction research, regulatory conversations, compliance mapping.

10. What's the competitive landscape?

The iGaming stack has three layers. Nobody competes across all three.

Traditional platform providers (SoftSwiss, EveryMatrix, BetConstruct) supply game content and back-office to operators. Licensed, GLI-certified, battle-tested — but entirely Web2. Server RNG, database balances, withdrawal queues.

Crypto casinos (Stake, BC.Game, Rollbit) bolt crypto payments onto the same Web2 stack. Their in-house games use self-attested "provably fair" RNG — no GLI-19 audit, no independent testing. The operator is both the house and the RNG provider.

On-chain RNG solutions exist but don't solve the full problem:

  • Chainlink VRF — GLI-19 certified by BMM Testlabs, but it's an oracle callback: two transactions per outcome, too slow and too expensive for high-frequency casino games
  • WINR Protocol — EVM chain for gambling, no B2B license, no RNG certification
  • Crypto Gambling Foundation — self-regulatory body founded by Stake's co-founders to certify provably fair sites. 14 sites verified in 6 years. No regulatory recognition.

ExoHash is the first project pursuing all three: consensus-level RNG (not oracle), protocol-enforced solvency, and a path to B2B licensing and GLI-19 certification. The architecture is designed to be licensable from day one.

11. Do players actually care about provably fair?

They do. Look at the Bustabit community — thousands of players in Telegram channels dissecting game fairness. Browse BitcoinTalk — years of threads with disputes about locked funds, delayed payouts, and rigged outcomes.

Players care deeply when real money is on the line. And every one of those disputes lands on the operator's desk.

Provable fairness isn't a feature for marketing decks — it's dispute elimination infrastructure. When every outcome is verifiable on-chain, there's nothing to argue about. No support tickets. No "contact us." The proof is in the block.

The question isn't whether players care about fairness. It's whether operators can afford to keep pretending they don't.

12. What about token listing? What's the EXOH token model?

EXOH has zero inflation. No emissions. No staking rewards paid in newly minted tokens.

Protocol revenue is distributed in USDC to stakers. EXOH also governs protocol parameters — fee splits, game configurations, and upgrades. The token value comes from real yield and governance rights, not speculation.

Listing is a post-mainnet conversation. We want the token to have real utility and real revenue behind it before it trades.

13. How do players deposit? What about payments?

USDC via IBC. Native Cosmos interoperability. Deposit from any connected chain, one transfer.

No card processors, no chargebacks, no PSP stack. Native crypto payments from day one.

14. What's the team?

Solo founder. PhD in Nuclear Physics from TU Delft. Started in high-frequency trading in 2007 — statistical arbitrage, market making.

Then institutional risk management — Partners Group at $1.5B AUM, Assura at $3.2B AUM under FINMA regulation.

Since 2021, full-time blockchain — MEV strategies, DEX arbitrage, execution-layer protocols. Built and deployed on Polygon and Sei before building ExoHash from scratch.

Every role was about the same thing: systems that handle money at speed under adversarial conditions. HFT taught me execution. Risk management taught me solvency. Both taught me that when real money moves in real time, you can't rely on audits — you need the math to enforce the rules. That's what ExoHash does.

Hiring: WASM game developer (Rust/Go — new games, game math), frontend developer (real-time game UI), community managers (Discord, Telegram, X).

15. What's the timeline to mainnet?

Protocol is built — BLS consensus RNG, WASM game SDK, games, devnet, block explorer, player UI. All running.

Next: hire specialists to accelerate.

  • WASM game developer — new games, game math (Rust/Go)
  • Frontend developer — real-time game UI
  • Community managers — Discord, Telegram, X

Protocol hardening, security audit, and organic community growth run in parallel.

Mainnet launches in guarded mode: capped wagering limits, whitelisted LPs and players, progressive removal of guardrails as the protocol proves itself in production.

The protocol is already built and running — this isn't starting from zero.

© 2026 EXOHASH PROTOCOL