jetedrow 

SnapCall is a high performance poker hand evaluation library.

Serial port transport for SmileySecure.Net. Opens a System.IO.Ports.SerialPort using SSP's wire defaults and exposes it as a Stream.

.NET library for integrating with devices using SSP (Smiley Secure Protocol). Transport-agnostic: drive a device over any Stream, whether serial, network or in-memory.

Interfaces and the message and transcript model for CryptoCard. Contains no cryptography and no dependencies, so a transport, a game engine or a third-party verifier can reference it without pulling... More information

Participant identity, P-256 message signing, the signed envelope and the byte-level wire codec - the part of CryptoCard a companion protocol (such as a ledger) shares with the card protocol. Base... More information

Deck ordering and digests, the wire codec, HMAC_DRBG, HKDF and commitments. Every byte CryptoCard puts on the wire is encoded here, by our own spec, never by a dependency (DESIGN.md C6).

The secp256k1 adapter and multi-scalar multiplication for CryptoCard. This is the only project in the repository permitted to reference BouncyCastle.

Schnorr and Chaum-Pedersen proofs, Bayer-Groth shuffle proofs, and batch verification for CryptoCard.

The CryptoCard protocol state machine, the message-driven session API and the hand archive. This is the package a game developer references.

Texas Hold'em built on CryptoCard. DESIGN.md §8.12 makes this the documentation: a complete, working, tested game rather than a snippet, and the first thing to break if the public API is awkward.

Roslyn analyzers that enforce the misuse-resistance rules in DESIGN.md §8. They ship with CryptoCard so a game developer gets the warnings without opting in.

A table's cradle-to-grave history: the CryptoCard hand archives and the CryptoCard Ledger replayed together, so every bet, payout, shuffle and revealed card can be read in one timeline per hand and... More information

The offline ledger verifier: takes a stored ledger and no secrets, replays every entry, and reports what it could and could not prove. The ledger's counterpart to CryptoCard.Verify.

The offline CryptoCard transcript verifier. Takes a published transcript and no secrets, and reports what it could and could not prove.

Five-card draw built on CryptoCard. Exercises multi-batch dealing (DESIGN.md §2.4): the draw round is a second BeginDeal/ObserveDeal batch, not new protocol surface.

A signed, replay-verified ledger of deposits, wagers, transfers, payouts and withdrawals for tables played over CryptoCard. Every entry is a CryptoCard extension envelope signed by the same... More information