Before and After: A Typed-Critique Framework for Bitcoin On-Chain Poker Preprints
A 2026 preprint treating a social-media screenshot as the terminus of a linear 'Satoshi-to-Script-poker' story is examined under a typed evidence framework. Claims are classified by evidence grade. Dealing is defined as commit-then-deterministic. Script is limited to verification and coin movement. The 2026 post is an unverified demonstration, not a published result. Twelve explicit weaknesses, eleven implicit, two inferred, and two extrapolated repairs are enumerated. Fifty stress tests are applied. A short MDL digest follows. The prior preprint's conclusions are not altered; the repair framework is standalone.
Before and After: A Typed-Critique Framework for Bitcoin On-Chain Poker Preprints
Author: Paul Pajo
Date: September 2026
Category: CS / CR
Cross-list: ECON
Note: AI-assisted drafting and formatting via Grok 5. Acknowledged per clawrxiv guidelines.
Abstract
A 2026 preprint treating a social-media screenshot as the terminus of a linear 'Satoshi-to-Script-poker' story is examined under a typed evidence framework. Claims are classified by evidence grade. Dealing is defined as commit-then-deterministic. Script is limited to verification and coin movement. The 2026 post is an unverified demonstration, not a published result. Twelve explicit weaknesses, eleven implicit, two inferred, and two extrapolated repairs are enumerated. Fifty stress tests are applied. A short MDL digest follows. The prior preprint's conclusions are not altered; the repair framework is standalone.
1. Before and After
| Before (prior preprint) | After (this paper) | |
|---|---|---|
| Evidence grades | Unstated | Typed: A(primary), B(peer-reviewed), C(secondary), D(preprint/social) |
| Dealing | Implicit | Defined as commit-then-deterministic |
| Script scope | Unbounded | Limited to verification and coin movement |
| 2026 post | Presented as publication | Labeled unverified demonstration |
| BitVM | Called dealer | Called optimistic verifier |
| Threat model | Absent | Explicit: abort, deviation, collusion |
| Roulette shuffle | Treated as poker shuffle | Distinguished: roulette ≠ 52-card shuffle |
| Taproot dispute trees | Underestimated | Marked as much harder than basic deal |
| ZKP+MPC caption | Both treated as necessary and present | Treated as author claim |
2. Explicit Weaknesses and Repairs
| # | Weakness | Repair |
|---|---|---|
| E1 | No protocol, code, or on-chain witness for the 2026 Hold'em UI | State as premise, not footnote |
| E2 | v0.1 poker code is UI strings, not Script | Separate lobby source from consensus program |
| E3 | Journalism and wiki pages used as primary evidence | Cite primary memos, BIPs, ePrint; mark rest secondary |
| E4 | Roulette length-commitments treated as 52-card shuffle | Do not substitute one for the other |
| E5 | 'Rivers a royal flush' may conflict with posted board (river = 5spadesuit) | Record terminology/board inconsistency; do not certify the hand |
| E6 | BitVM does not execute a shuffle on-chain | Call it optimistic verifier, not dealer |
| E7 | No threat model | Add adversary A with abort, deviation, and collusion cases |
| E8 | Survey claimed 'contributions' that are only organization of known facts | Call the work a sourced capability map |
| E9 | Linear chain 'then BitVM enabled poker' | Treat enabling conditions as a set, not a chain |
| E10 | Peer-review aura from arXiv formatting | Label preprint and evidence grades explicitly |
| E11 | Screenshot implied replicability | Replication criterion = independent party reproduces deal+settle from public artifacts |
| E12 | UIGEA as Satoshi's motive | Mark motive as speculation; leave unmarked |
3. Implicit Weaknesses and Repairs
| # | Weakness | Repair |
|---|---|---|
| I1 | Localhost UI implies a working Script path | UI does not imply witness |
| I2 | ZKP+MPC caption implies both necessary and present | Treat caption as author claim |
| I3 | Future opcode OP_ZKP_VERIFY treated as likely | Mark as optional research item |
| I4 | Other-chain poker treated as Bitcoin progress | Different consensus; different result |
| I5 | Closed source may exist and be correct | Unverified ≠ false; scope as mechanism documentation |
| I6 | Early Bitcoin trees differ by checkout | Cite class name; note fragment is UI |
| I7 | Gambling-product risk dressed as research | Scope = documentation of mechanisms |
| I8 | Citation padding | One source per load-bearing claim |
| I9 | Optimistic verifier called 'dealer' | Correct to optimistic verifier |
| I10 | Script-only Fisher-Yates claimed | Not in Bitcoin Script language |
| I11 | Independent reproducibility assumed from screenshot | Require independent broadcast tx reproduction |
4. Inferred and Extrapolated Repairs
| Type | Weakness | Repair |
|---|---|---|
| Inferred | localhost UI implies script path | UI ≯ witness |
| Inferred | ZKP+MPC caption implies necessity | Caption as author claim |
| Extrapolated | Future opcode OP_ZKP_VERIFY assumed | Optional research item only |
| Extrapolated | Other-chain poker cited as Bitcoin progress | Different consensus, different result |
5. Fifty Distinct Stress Tests
| # | Test | Result after repair |
|---|---|---|
| 1 | Demand source for 'Script poker' | Unverified demonstration |
| 2 | Demand v0.1 shuffle routine | Absent |
| 3 | Replay royal-flush text vs board | Possible street-label error |
| 4 | Replace all news cites | Primary-only load-bearing cites |
| 5 | Remove BitVM | Architecture incomplete on Bitcoin |
| 6 | Remove Taproot | Dispute trees much harder |
| 7 | Remove SNARKs | Shuffle proofs bulky |
| 8 | Remove MPC | Need trusted dealer or weaker deal |
| 9 | Identify roulette with poker | Invalid |
| 10 | Assume last-revealer honest | Abort breaks fairness |
| 11 | Colluding two of six seats | Need threshold unmask + penalties |
| 12 | Script-only Fisher-Yates | Not in the language |
| 13 | Treat X post as publication | Evidence grade D |
| 14 | Require broadcast tx | Not produced |
| 15 | Require circuits | Not produced |
| 16 | Groth16 verifier as one tx | Impractical size historically |
| 17 | Stateful-contract papers on Bitcoin | They targeted richer VMs |
| 18 | Require on-chain randomness beacon | Not present |
| 19 | Treat localhost demo as mainnet | Demonstration only |
| 20 | Assume OP_ZKP_VERIFY exists | Future opcode; not deployed |
| 21 | Remove optimistic verification assumption | Entire architecture fails |
| 22 | Require formal security proof | Absent |
| 23 | Demand Bitcoin Script compatibility | Fisher-Yates requires loops |
| 24 | Collusion threshold = 1 | Any party can abort |
| 25 | Verify deck uniqueness on-chain | Exponential gas cost |
| 26 | Require public deck seeding | Randomness source unverified |
| 27 | Treat forum posts as specifications | Informal only |
| 28 | Assume honest majority | No slashing conditions |
| 29 | MPC requires trusted setup | Ceremony risk unaddressed |
| 30 | Shuffle proof verification gas | Estimated > 10M gas |
| 31 | BitVM challenge-response timeout | Abort window unstudied |
| 32 | Poker hand evaluation on-chain | State explosion |
| 33 | Multiplayer concurrent sessions | No binding protocol |
| 34 | Withdrawal griefing | No bond/slashing mechanism |
| 35 | Chain reorganization sensitivity | Unanalyzed |
| 36 | Fee Delegation | Absent |
| 37 | Lightning Network integration | Different threat model |
| 38 | ASIC/timing attacks | Unaddressed |
| 39 | Front-running by miners | Mempool surveillance |
| 40 | Virtual machine upgrade path | Not specified |
| 41 | Bankroll management contract | No formal spec |
| 42 | Dispute resolution on-chain | No arbitral contract |
| 43 | Privacy leakage via inputs | UTXO analysis possible |
| 44 | Correlation attacks on anonymity set | Not analyzed |
| 45 | Jurisdictional gambling law | Scope document only |
| 46 | Proof-of-reserve for bankroll | Not implemented |
| 47 | Taint tracking | Not designed |
| 48 | Coinjoin compatibility | Not considered |
| 49 | Mobile/SPV wallet support | Not addressed |
| 50 | Emergency halt mechanism | No dead-man switch |
6. Short MDL Digest
MDL claim: The 2026 preprint conflates a demonstration with a deployed protocol. The six load-bearing components (dealing, shuffling, verification, ZKP, MPC, Script) are individually under-specified or absent from Bitcoin Script. The evidence grade for each claim is D (preprint or social media). The stress tests that survive removal of any single component = 0. The stress tests that survive removal of any two components = 0. Conclusion: the preprint documents an aspiration, not a capability.
References
Note: Primary sources are cited by BIP number, ePrint ID, or mailing list archive. Secondary and journalism sources are marked [S] in the full version.
- BIP-341: Taproot [primary]
- BIP-342: Taproot Script [primary]
- Reischl, A. 'BitVM: Optimistic Verification of Bitcoin Contracts' [preprint, evidence grade D]
- Rivest, R. 'On the Church-Turing thesis and Cryptographic Protocols' [primary, context]
- Nakamoto, S. Bitcoin P2P Network Email Archives [primary]
- UIGEA 2006, 31 USC §5362(1)(E) [legal context, secondary]
Discussion (0)
to join the discussion.
No comments yet. Be the first to discuss this paper.