Poker Protocol

Fully on-chain poker, powered by ZK. Be the shuffler. Be the dealer. Be the house. A trustless poker protocol for players, apps, and platforms.

[Poker Protocol @PokerProtocol]

Fully on chain poker contracts are coming together! Generating Groth16 proofs still too slow in the testing framework but we have some tricks to speed it up.

Major Milestones Completed:

Core Protocol & Cryptography:

✅ Full Barnett-Smart mental poker implementation with zero-knowledge proofs
✅ Complete zkSNARK circuit suite (keyownership, shuffle, reveal, initial encryption)
✅ Multi-party cryptographic key generation and secure deck shuffling
✅ Gas-optimized proof verification with split initial encryption circuits

Game Implementation:

✅ End-to-end Texas Hold'em gameplay from join to showdown
✅ Complete state management (9 game states, 4 betting rounds)
✅ Automated blinds, betting mechanics, and pot distribution
✅ Trustless community card reveals using decryption shares

Smart Contract Architecture:

✅ Modular contract system (PokerTable, DeckManager, Rules Registry)
✅ On-chain hand evaluation and winner determination
✅ Player management with buy-ins and stack tracking
✅ Integration-ready with external pot managers and rule sets

Testing & Verification:

✅ Full end-to-end test suite covering complete poker hands
✅ Cryptographic proof generation and verification testing
✅ All game phases validated from key submission to payout

[Poker Protocol @PokerProtocol]

Been deep in the tank figuring out how to get v0 of poker protocol out on testnet.

React SDK is written and now on to the tricky part of making sure the client works in a web environment. Going to have to make sure circomjs is able to use web workers appropriately and stays in sync with the protocol.

The hardhat test environment proved to be tricky when adding lots of concurrency since there were many unknown tx reverts when running in a single nodejs process. Finally got a basic test harness working but will likely need more sophistication for testing with more sdk clients.

State is tracked locally with zustand so in theory we should be able to make a snappy reactive UI when that’s all hooked up.

[Poker Protocol @PokerProtocol]

Layer 3 (appchains) are interesting and may be the ultimate home for Poker Protocol. Ty @Guz_MassAdopt for the idea.

It’s likely the best way to get the tps required for homomorphic encryption when allowing each player to apply their own randomness. Less messy code optimizations required.

[Poker Protocol @PokerProtocol]

🃏 Major milestone reached! Phase 1 of our mental poker protocol client is complete! ✅

🔐 Cryptographic foundation: BabyJubJub, ElGamal encryption, ZK-SNARK proof generation
🔗 Blockchain layer: TypeChain integration, event subscriptions, reactive state management
🧪 27 tests passing with @bunjavascript

Next up: Protocol flow orchestration and transaction management!

Getting ready to shuffle some encrypted cards on-chain! 🚀

[Poker Protocol @PokerProtocol]

Monorepo migration is complete! Claude 4 in cursor has gotten much better at assisting with devops setup and tool calls. That was much less painful then I thought it was going to be.

Some of the most pleasant surprises:

1. It picked up on the incompatibility of bun with snark generation very quickly. That could have been a really deep rabbit hole if it didn't give me that insight.

2. Relative path changes in scripts can be done with one ask, and it searches and finds all the references and changes it even with multiple relative directory changes.

3. Claude 4 has now gotten as good as gemini at planning and execution of changes, as well as printing enough context to the last output so it can better retain context in long chats.

[Poker Protocol @PokerProtocol]

Migrating to a monorepo structure today… wish me luck 🤞

[Poker Protocol @PokerProtocol]

To make the protocol flexible it needs to support multiple on chain identity providers.

It should be configurable by the platform that creates the table, allowing for compliance requirements to be enforced on chain as well.

The protocol should be as permissionless as the host desires.

[Poker Protocol @PokerProtocol]

5/
Another path:
No token.
Vertically integrate the protocol + app.
Simpler… but less composable and harder to decentralize.

[Poker Protocol @PokerProtocol]

1/
Lots of great discussion at BTC Vegas!
Can’t wait to start building the poker client when I’m back.

Still exploring the best revenue model for the protocol…

[Poker Protocol @PokerProtocol]

4/
But there are tradeoffs:
– Adds token overhead
– Might require premine unless a bonding curve model works
– Needs governance — or fully immutable contracts (hard)

[Poker Protocol @PokerProtocol]

At BTC Vegas chatting about self-sovereign poker.

No house, no trusted shuffler, just code.

If you’re here and into this idea, let’s chat!

[Poker Protocol @PokerProtocol]

Most poker platforms ask you to trust the server.
Even “provably fair” still means: trust us.

I’m building a protocol where:
– No one holds the cards
– Shuffles are verifiable
– Incentives are on-chain

Follow the journey 🃏