0.42.0 — 2026-08-26
A back office, so an account can be fixed rather than apologised for
An admin panel: who has signed up, what they are holding, what they spent it on, and a screen that can put tokens back — with every change recorded against the person who made it.
Features:
- There is an admin panel. Signups and how many verified, tokens outstanding across every account against tokens spent, generations in the last day and how many of them failed, and the accounts themselves — searchable by address, name or id, each one showing its balance, its plan, and how much it has made.
- Tokens can be granted or taken back from a screen, with a note attached. Grant and Deduct are separate buttons rather than a sign in the amount field, because the way that goes wrong is granting minus five hundred while meaning to grant five hundred. A deduction cannot take a balance below zero: every route that charges tests the balance against the price, so a negative one would leave an account that quietly refuses to do anything with nothing on screen to say why.
- Every change made from the panel is written down — who did it, to whom, and what moved. It is recorded inside the same transaction that moves the tokens, so the ledger row and the account of who caused it commit together or not at all. An adjustment that happened without a record of who made it is the one thing a back office must not be able to produce.
- An address can be marked verified without the email. Verification mail that bounced, or landed in spam, leaves somebody unable to collect the hundred free tokens the account is entitled to — and until now the only way to give them to that person was a database client.
- A stolen laptop can be signed out everywhere, and an account can be deleted for somebody who asks. Deleting takes the balance, the ledger, the generations, the projects and the links with it, so it asks for the address to be typed back before it will do anything.
- The token ledger and every generation, across all accounts, both filterable. "Which generations failed today" and "where did this person's tokens go" were questions with no answer short of writing SQL.
Improvements:
- What the panel does shows up in the account it was done to, in that person's own words. An adjustment reads as Admin Grant or Admin Deduction in their token history — the operator's address and their note stay in the audit log, which is not the same thing as the customer's account page.
Changed:
- The account page carries an Admin link for the people who have one, and renders nothing at all for everybody else. The panel answers not-found to anyone who is not an administrator, signed in or not, so it does not confirm its own existence to whoever is trying the URL.