checking your sign-in
Volunteer desk
This desk issues real badges and spends the event’s funds, so it stays behind the organiser account.
Use the organiser account for this event. If you do not have it, ask whoever set the event up — there is no self-service reset.
Which event are you working?
Every badge you hand out is stamped with the event you pick here, and that cannot be changed afterwards. So the desk asks rather than guesses — every time, including after a reload.
Nothing here has been chosen for you. If the event you want is not listed, it has not been opened yet — whoever set it up can do that from the organiser page.
This deployment has no operator account configured
There is nothing to sign in to. The desk is switched off rather than left open, so no badges can be issued from this browser.
Whoever runs this deployment needs to configure an operator account and restart it. A sign-in form is deliberately not shown here: it could not work.
Scan the attendee
camera onCamera is off
Start it to read the attendee’s wallet code — or skip it entirely and type their address below. Both routes end in the same place.
Paste whatever their code contained — the address is pulled out of a longer payload for you. / jumps here, N starts the next attendee.
Attendee
—Badges
everything issued, here and elsewhere| # | badge | attendee | nftoken id | status | confirmation |
|---|
Nobody yet. The first badge you issue appears here, and turns confirmed the moment the attendee accepts it.
Every badge ever issued for this event (taxon …), counted from the ledger itself rather than from this desk’s own list. Use it to check the desk against the full picture.