Open the wallet on this site and click its π‘οΈ Admin (or π‘οΈ Moderate) button.
β Back to the site
Online now
Visitor counts across every world this domain declares (GET /presence/status, one call per world). Counts only: the presence server holds no identity for visitors, so nobody is listed by name. Refreshes automatically every 5 seconds while this page is open.
Visits
How many times visitors entered each world (POST /atlas/admin/visits). Anonymous counts only β no visitor identity is stored, and a visitor who re-enters a world is counted again, so these are visits, not unique people. Days are UTC; counts older than 90 days are dropped.
| World | Today | Last 7 days | Last 30 days |
|---|
Per day (last 14 days, all worlds)
World moderation
Mute, unmute or remove anonymous visitors from a world for a limited time. Visitors appear only under a temporary reference and the name they chose; wallet keys and network addresses are never shown. Your wallet asks you to approve each moderation session, and this page never sees your keys.
| Visitor | In | Joined | State | Reference | Actions |
|---|
Audit log for this world
A private record kept by the presence service of every moderation action in this world, including refused ones. It never contains chat text, wallet keys or network addresses.
| # | Time | Moderator | Action | Visitor ref | Length | Reason | Outcome |
|---|
Revoke a credential
Immediately invalidates a credential by id (POST /atlas/revoke). Cannot be undone.
Suspend / unsuspend a credential
A reversible freeze (POST /atlas/suspend, /atlas/unsuspend) for when a report just came in and revoking outright would be too heavy-handed β a suspended credential still exists and still verifies, it's just refused wherever a presentation is checked, until this is lifted or it expires on its own.
Trusted trade peers
The other domains this domain will accept a cross-domain Trading Station settlement with (POST /atlas/admin/trusted-trade-peers/add, /remove β SPEC.md Β§7), in either role a trade can put it in: accepting a foreign-issued balance here, and honoring a relay request against a credential this domain itself issued. Mutual by convention, not by enforcement β add a domain here only once you'd also want it listing this domain back.
Consortium mint co-signing
This domain's own half of a domain-quorum reserve mint (reserve-bank-demo.html's Act 8, POST /atlas/demo/reserve/consortium/co-sign) β the admin-gated step a sibling domain's own operator has to take, since a domain's approval can only ever come from that domain's own server signing with its own key. Enter the requesting domain and the pending request's id (both shown on the requesting domain's own reserve-bank-demo.html page), then co-sign: this fetches the real pending action from that domain first and signs exactly that, never a value typed in below.
Claw back a credential
Once a suspended report is actually confirmed: revokes the credential wherever it currently sits and mints a fresh one straight to whoever it actually belongs to, in the same act (POST /atlas/clawback). Works on a stolen balance or a unique item alike, and reaches a 'bound' relationship credential (a Post Office or Trading Station membership) the same total way revoke already does β re-pointing that membership's own roster entry automatically if so. Paste the exact credential as it currently stands, wherever it's ended up.
Mint an asset
Mints a brand-new credential with its own starting facts (POST /atlas/asset/mint) β the authenticated sibling of a visitor's own self-serve mint, for when a specific instance needs a fact only this domain should be able to set (a factory's real serial number, say) rather than every unit of a class coming out identical. Properties merge onto the class's own catalog defaults, same merge rules as Reissue below.
Reissue an asset
Rewrites an already-issued non-fungible credential's properties and/or tradeScope, superseding it with a new one (POST /atlas/asset/reissue). Paste the exact credential currently held. Properties merge onto what's already there β a key left out is untouched, and a key set to null is removed entirely rather than kept as a literal null.
Fulfill a purchase
Confirms a held credential is genuine and unspent, then consumes it in the same act (POST /atlas/asset/fulfill) β the hand-over step for anything acquired via POST /atlas/asset/purchase, or any other credential meant to be presented once and only once. Paste the exact credential the visitor is presenting.
Class-wide patch
Sets a fact for an entire non-fungible asset CLASS at once (POST /atlas/admin/class-patch), instead of reissuing every current holder's credential by hand β useful for fixing a mistake or correcting an over/underpowered roll across everyone who has one. Nothing already-issued changes right away: each holder's own wallet picks the patch up automatically the next time it checks in with this domain (the same check-in that already delivers mail and revocations), so there's no roster of who currently holds one kept here.
This class rolls random per-item stats at mint time β the properties below are only the shared fallback template, not any specific holder's actual roll. A patch still applies the same way to whatever each holder's own credential currently has.
Picking a class above pre-fills its current properties and tradeScope (its own active patch, if it has one, otherwise its plain catalog defaults) so you're editing what's actually there rather than guessing. Only what you change matters β a property left out of the box below is left untouched, not cleared, since this always merges in what you type. To remove a property entirely, set it to null rather than deleting its line.
Send mail
Signs and delivers a message to whoever holds the named credential (POST /atlas/mail/send), optionally attaching a freshly minted gift asset. This is addressed by credential id, NOT by public key or handle β paste the exact id of a credential the recipient's wallet already holds (find it in their wallet's own item list, or from an id an Issue/Reissue call returned). This domain doesn't check that the id is real, so a wrong or made-up id will still say "Sent." but nobody will actually receive anything.
Send a ticket by email
Mints a ticket of the chosen class and emails it to an address as an attachment (POST /atlas/admin/send-ticket-to-email, SPEC.md Β§13.1). The recipient needs no wallet: whoever holds the attachment holds the ticket, and forwarding the email with the new holder CC'd passes it on. Meant for testing here, and as the same call a company's own backend makes when it issues tickets. Only a unique (non-fungible) class that is not bound to its owner can be sent. The domain must have outbound email configured, or this says so. Properties merge onto the class's catalog defaults, as in Mint above. If the mail server does not accept the message the ticket is cancelled, so nothing is left outstanding.
Calendar
Publishes to this domain's (or one world's) calendar (POST /atlas/calendar).