The operator console#

The console at /blargdash is where the people running a deployment look after it: settings, relayers, health, the review queue, support, who is connected, the catalogue, the background jobs and the mail log. It is not a customer surface. Nothing here reveals a key, and the only action that moves money is the escrow ruling, which can pick between the two exits a deposit already committed to and nothing else.

Who gets in#

An operator signs in to their own account and opens /blargdash; there is no second password once operators exist. Three clearances:

OPERATOR_ADMIN_EMAIL seeds the first admin at boot; that admin grants the rest under Operators. Every write appends a row to the operator actions log with who did it. The BLARGDASH_PASSWORD door still works as admin for a deployment with no operators yet.

Settings#

Platform settings live in the database and override the environment, with a short cache. Secrets are stored encrypted and the page shows only that one is set. The catalog names what may be set: the price list (opening fee, free wallets, free payments, payment fee, funding and transfer cents), relayer minimums and the mail provider key among them.

Relayers#

A relayer pays gas for settlements, burns and fee collection on one chain. The page shows every relayer per chain with its state, float, burn rate and runway, and moves them through a lifecycle: candidate, checked, active, retiring, retired. Add one by pasting a key (stored as ciphertext, never echoed) or by generating it; check it (the key derives the address, the RPC answers, the float meets the minimum, a signed no-op succeeds); promote it (only a fresh check, never two active); retire it when its in-flight work is done. The environment seeds the first active relayer on an empty table.

Health#

Revenue by kind against gas: opening fees, payment fees and funding cents over the last thirty days, what the sweep has collected on-chain, relayer spend per chain in native units with the runway the float buys, the directory's verified count, mail deliveries and the size of the review queue.

Review#

Signals the spending rail raises for a person to look at: ten or more refused payments by one account in an hour, eight or more wallets opened in a day, a wallet holding far over the line, fees owed for over a week. Each condition is one row per window. Clear says nothing is wrong; Freeze stops the account's payments and transfers with a reason the agent is told on its next attempt, until an admin Unfreezes. The scan runs on the float watch's timer and from the button.

Support#

Threads accounts opened from their dashboard or through their agents. A reply is written into the thread and emailed to the person (for an organization, to the member who opened it). Closing is recorded. The account's next message brings the thread back to waiting.

Connections#

Every agent connected over OAuth, one row per grant (the access token and its refresh token together): who it acts as, the account it was switched to when a member of an organization switched, the client, when it connected and was last used. A guest grant, made without signing in, is named as such until the agent opens a wallet and binds it. Revoke ends a grant; the client reconnects through consent and the account keeps everything. Tokens are hashes at rest and never shown, not even the hash.

Catalogue#

What the directory shows the world: how many endpoints stand verified, how many are flagged (their 402 stopped answering, or the host is unreachable) with what came back, the reviewed picks, the provider count and the time of the last check on this instance. Verify now re-quotes every third-party row in the background; the timer does the same every six hours. Flagged rows stay listed with their state shown; they are the ones to fix or drop from the seed.

Jobs#

The background loops on this instance and what each last did: when it started and finished, whether it succeeded, the error when it did not, and when it is next due. Rows appear after a loop's first tick, so an empty table right after a deploy is normal; a row whose next due time is in the past is a loop that stopped.

Mail and actions#

Mail is every email the service tried to send (sign-in links, invitations, support replies) with the recipient masked and the provider's error on a failed row: enough to answer "did the link go out", never a mailing list. Actions is the console's own trail: every write made here, who made it and what it touched, newest first.

Accounts and escrows#

Accounts lists every account with its kind (person, organization, unclaimed), wallets open, wallets that have held money, payments made and dollars spent, plus a dossier per account: wallets, receipts, notes and a timeline. Seller columns appear when selling is on. Escrows is the queue of disputed escrow payments awaiting a ruling.