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 🃏

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!

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

Migrating to a monorepo structure today… wish me luck 🤞

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

🃏 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

Layer 3 (appchains) are interesting and may be the ultimate home for Poker Protocol. Ty Jeremy Guzman 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

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