CIPHER
CONNECTING…The arcade game on the Favilla KEY. Every score is signed inside the device and checked in your browser. What is the Favilla KEY?
Today's board · —
Seal 5 blocks. Fastest time wins.
New board in
—
On the KEY, open Scan and point it here. The KEY checks the block's proof of work itself, so it doesn't need to trust this page.
- Scanning relays for signed runs…
How the boards work
Daily speed run. A CIPHER day is 144 Bitcoin blocks, about a day. Each day's board comes from the hash of its first block, so every KEY gets the same board and nobody can know it in advance. Everyone plays the same two skills, and about one day in three is a boss day. Seal five blocks as fast as you can; your best time that day counts. A new board starts when the next day's first block is mined, so the change-over time moves a little from day to day.
Free run ATH. Free play has a random board and a random pair of skills each run. This board keeps each player's highest score.
Daily winners. The fastest time on each finished block day.
One entry per player per board. Only runs from the current game rules are ranked, so scores from the old game never mix in.
Free run ATH. Free play has a random board and a random pair of skills each run. This board keeps each player's highest score.
Daily winners. The fastest time on each finished block day.
One entry per player per board. Only runs from the current game rules are ranked, so scores from the old game never mix in.
How a score is checked
A shared run is a Nostr
kind:1888 event tagged t: favillacipher. Your browser checks three things before a run is ranked:
(1) the Nostr signature, so the player's key posted it;
(2) the attest signature from the KEY's secure element over the run's stats (score, blocks sealed, run length and the rest), tied to that player's key;
(3) that the attestation key is on Favilla's signed list of made devices.
For the daily board it also checks the Bitcoin block the run names: that it is the real block at that height, that the run's board comes from that block's hash, and that the run was shared during that block day. It checks that all five blocks were sealed (signed) and that the run's time agrees with the signed run length.
The block a run was played on and its exact time are signed by the player's Nostr key, not by the secure element. Anyone who rewrites their own KEY's firmware could still sign a made-up run. We're fine with that: they had to break into their own device to do it.