BadBeats
sha256(server seed), published before you pick1HMAC-SHA256(server, seed:nonce:level)[0..4] mod 3The house commits before you pick.
- RoleFounder, design, build
- ShipsFrom the spec
- DataPlay money. The verification is the product's code.
sha256(server seed), published before you pick1HMAC-SHA256(server, seed:nonce:level)[0..4] mod 3The house commits before you pick.
Each level's bust tile is derived, not drawn: HMAC-SHA256 keyed with the server seed over your seed, the round number and the level, first four bytes modulo three. The server seed is secret during the round and revealed after it.
Verification needs nothing from the house. Hash the revealed seed and compare it to the commitment; recompute each level and compare it to what you saw. The Verify button above does exactly that, with Web Crypto, in your browser.
The scheme in five lines. Nothing hidden, including the edge.
Phase one is this: email sign-in, the Tower, no blockchain. Phase two puts it on Base with wallet sign-in and real stakes. Phase three is growth. The order is fixed so the fairness scheme is proven before any money touches it.
Planning is complete: product, game logic, the cryptographic scheme, the schema. The build is next, and the Tower on this page is its first running piece.
From the project's planning documents.
The proof is the product; the game is the demo of it. Writing the commitment scheme first made every later screen a matter of showing it, not inventing it.
The drawing below was the plate until tonight. The playable version above replaced it in one evening because the scheme was already decided.
The plate, as drawn before the Tower ran.
Piece 2 of 6. Left and right arrow keys move between pieces.