asking the server who you are

Events

Every event on this deployment, drafts included. The number in the left column is the event id — which is also the NFTokenTaxon every badge for that event is minted under.

New event

1 Registry —

event id / taxon	name	status	date	venue	registered

— Registration counts come from GET /admin/api/events/{id}/registrations, one call per row.

New event

An event is a row in the database and a number on the ledger. Pick the number carefully: everything else here can be edited later.

1 Create POST /admin/api/events

Event id = NFTokenTaxon

Event id

This integer is the NFTokenTaxon stamped into every badge minted for this event. It is written by NFTokenMint into the token itself and cannot be changed afterwards — not by editing this row, not by anything.

Do not reuse a number. Two events sharing a taxon become one on-chain collection: nfts_by_issuer?taxon=N returns both events’ badges mixed together, and verification cannot tell them apart. The server refuses a duplicate with a 409 for exactly this reason.

Any whole number from 0 to 2147483647. Pick one you can read out loud — it appears in the public URL and in every roster query.

Name *

Description

Event date

The date of the event itself. The ledger never sees it.

Venue

Metadata URI

Event-wide fallback badge artwork, used when per-attendee art is unavailable. Editable only until the first badge is minted — NFTokenMint.URI is written into the token and is immutable, so changing it later would leave minted badges pointing at the old artwork.

Status

Cancel

—

— taxon

Edit event

The database who said they are coming

—

registered

—

checked in

—

attendance rows

Registered is a row somebody created on the public page. Attendance rows are signed claims this server verified against the chain and indexed.

The chain what actually exists on XRPL

—

minted

—

claimed

—

burned

—

owner unknown

Do not add these to the registration count. A registration is not a badge: somebody can register and never claim, and a badge can exist for somebody who never registered.

2 Registrations GET /admin/api/events/…/registrations

name	address	proof	email · personal data	registered	checked in

Email is the only personal data on this page. It is shown here because the organiser needs it, and it is never put in a URL. The plain Export CSV omits it; Export CSV with emails writes a file containing every attendee’s address book entry, which then lives outside this console with no access control at all.

Sign in

This deployment has no admin credentials

Events

New event

—