PikoPoker was announced on the DFINITY Forum on 2026-10-02 as a fully on‑chain implementation of Texas Hold'em running on the InternetComputer (ICP).
What “fully on‑chain” means
In plain terms, a fully on‑chain game keeps core game processes—such as card dealing, bet handling, pot settlement and the record of each hand—inside blockchain smart contract code rather than on external servers. That makes the rules and outcomes auditable from the ledger and reduces dependence on centralized service operators for core game state.
Technical context for the InternetComputer
The InternetComputer platform runs WebAssembly-based smart contracts (often called canisters) that execute deterministically on‑chain. Developers building games on ICP must design their canisters to manage game state, player actions, and transaction flow through the chain’s execution model. On‑chain gaming also raises practical design questions common to all blockchains—most notably how to produce fair, verifiable randomness and how to balance on‑chain transparency with user experience and throughput.
What this announcement means, and what it does not
The forum post introduces PikoPoker as an on‑chain Texas Hold'em project for the InternetComputer ecosystem. The announcement identifies the project concept but does not, in that post, specify implementation details such as randomness mechanisms, fee models, user onboarding, or a live launch schedule. Those technical and operational choices determine how closely a given implementation can match the responsiveness and privacy expectations of traditional off‑chain poker platforms.
Why it matters to users and builders
For players, fully on‑chain poker can increase the ability to verify game history and outcomes independently. For builders and ecosystem observers, the project is an example of developers exploring on‑chain applications that require low-latency state changes and strong fairness guarantees—areas where design tradeoffs between decentralization, performance and usability are particularly visible.
For the original announcement and protocol information, see the DFINITY Forum post referenced below and the InternetComputer dashboard.