Your own record
You
Everything this server can honestly say is yours: the tables it is holding open for you, the matches you have already finished, the runs the board has under your name, and the receipts your own moves minted. Every link here goes to the page that re-runs the thing rather than to a copy of its result.
Who you are here
You are a visitor label this server minted for this browser the first time it arrived. It is a name, not a login: nothing was proved and nothing is recoverable.
- your label
- visitor-… (not printed in full: on this surface the label itself acts as the credential)
- actor
- b3d59fa66b8ae356…
How durable is this? It is a cookie. Clear your cookies, switch browsers, or open a private window and you are a new person here, with no recovery: the games above would not be reachable from the new identity and nothing on this page could hand them back. That is fixable and opt-in: claim a recoverable identity and you get 24 words that reproduce this player anywhere. You do not have to, and nothing stops working if you never do.
Your moves are attributed by that label, not signed by a key you hold, which is why every receipt below says asserted. The proof on this surface is that the move was re-run against the rules, not that a particular human made it.
Your other accounts
No other account is linked to this one.
Linking needs an identity to link to: a key your own 24 words derive. This browser has a cookie label instead, which nothing can sign a claim with. Claim a recoverable identity first; the link door is one step after it.
Games in progress
Nothing is waiting for you. You have not opened a table yet, or the one you opened has since ENDED, in which case it is in Matches you have finished below rather than gone. Nothing has been lost that this page is hiding.
Start one, and it will appear here the moment it exists:
Play The Descent Open an Automatafl tableOpen a Multiway-Tug table
Matches you have finished
You have not finished a match here yet. A table lands in this panel when it ends (played out, resigned, or forfeited on the clock), and it stays: the moves are kept, so the finished game can be re-executed from them by anyone you send the link to.
A game still in play is in the panel above, not here. Nothing has been thrown away that this panel is hiding.
Finished Descent runs
The board has no run under this label. If you have never finished a descent, that is simply why: the board only holds runs that were submitted and re-verified, and yours would appear here the moment one is.
There is a second reason, and it is ours, not yours: an unclaimed browser signs its runs with a pseudonym that tab keeps in its own local storage, never with the cookie above. So even a run of yours sitting on today's board cannot be claimed for you from the server side: the two names have nothing linking them. Claiming an identity fixes it going forward, because the play surface then signs with your key; the panel below reads the browser-local name out of this tab either way, so you can recognise your own row on the board.
This browser keeps its own Descent name and its unfinished run in local storage. Reading that needs JavaScript; with it off, /descent/play is still the page that holds them.
The day's board is at /descent.
Your receipts
No receipt carries your name yet. A receipt is minted by a move that landed: the executor re-ran it against the rules and accepted it. You have not made one on this identity, so there is nothing here to replay. Make a single move in any game above and this panel fills in.
This is the product's own claim, and it is worth knowing what it does and does not cover: the chain of a session re-executes here, in this server, from its recorded moves. That is a real re-run, not a stored verdict. And it is not a blockchain, not a proof carried off this box, and not evidence about who moved, because a browser move is attributed by an asserted label rather than signed by a key you hold.
How each name on this board was established
- signed
- Every move carried a signature made on the player's own device. This server never held the key that made it.
- signed by the bot
- Every move carried a signature, made with the key the chat bot derives for that account. Whoever runs the bot can derive that key too.
- attributed
- The name is the one the player was signed in as, recorded without a signature. This is how playing in a browser normally works.
All three are real play and all three count. The difference is what was checked, not how good the run was: a signed row is a stronger claim about who played it, and an attributed row is the ordinary way a browser plays. If you want your own rows signed, your identity page has the one switch that does it.