From ticket to door.

1. Create the event

The website and the app are the same thing — use whichever is in your hand. The app is the website installed on your phone: open the menu and tap “Install the app”.

1. Sign in from Account, with your email (a six-digit code, no password) or with a wallet you already have. On a phone, choose “MetaMask or another wallet app”.
2. Apply to organize from your account. While NFTicks runs on the test network, every organizer is approved by hand, usually within a day.
3. Open Create an event. Give it a name, a picture, where it happens — in person, online, on Discord or on Telegram — and a date.
4. Add the kinds of ticket, each with a price and how many there are, and choose what buyers may do with them afterwards: resell or not, when, and up to what price.
5. Press create and confirm twice: once to put the tickets on the blockchain, once to publish the name, picture and venue. The commission is shown before you confirm.

From that moment the event is on sale. Every sale is paid straight into your wallet in the same transaction; nobody approves a buyer and we never hold the money.

2. Kinds of ticket, and their numbers

Each kind of ticket is its own ticket on the blockchain, with its own number — Standing is #12, VIP is #13; for a community, Beginner is #14 and Advanced is #15. The number is shown on each ticket in Your events and is the end of its link: nfticks.io/p/14.

That number is how the bots know which ticket opens what. You give it to them once, with /setup, in the place the ticket opens.

3. Discord: one role per kind of ticket

On Discord a ticket gives its holder a role, and the role decides which channels they see. Beginner holders see #beginners; Advanced holders see #advanced; both can see #general.

1. Add the NFTicks bot to your server. Keep both permissions ticked: “Manage Roles” hands out the roles, and “Create Invite” lets it add buyers to your server when they connect their Discord account on the ticket page.
2. In Server Settings → Roles, create a role for each kind of ticket — for example “Beginner” and “Advanced” — and drag the NFTicks role above them. The bot can only hand out roles that sit below its own.
3. Decide what each role sees. Right-click the channel — or a whole category, which covers every channel in it — → Edit → Permissions → switch on Private Channel → Add members or roles → pick the role. Every channel can be private: the bot reaches a new member by private message. A welcome channel open to everyone still helps anybody who has closed their private messages. A role you already have works as well as a new one.
4. Prove you are the organizer: in any channel type /verify, open the private link the bot gives you, and sign with the wallet that created the tickets. It is a signature, not a payment.
5. For each kind of ticket, type /setup pass:14 role:@Beginner, then /setup pass:15 role:@Advanced. The bot confirms each one.
6. Share the ticket links wherever your audience is.

What your buyers do

They get their role in one of three ways. None of them needs you.

1. The button on the website. Right after paying — and later on the ticket page and in My tickets — they press “Get your Discord role”, allow NFTicks on Discord, and sign with the wallet that holds the ticket. They are added to your server and the role arrives within about twenty seconds. No command to type.
2. The bot’s private message. Somebody who joins the server gets a private message from the bot with a link of their own; they open it and sign, and the role arrives the same way, with a message saying why.
3. /verify. Anybody can send it to the bot in a private message — click the NFTicks bot in the member list, then Message — or type it in any channel they can see.

When a ticket expires or is sold on, the role is taken back, with a message.

For buyers to be added to the server automatically, the NFTicks role needs “Create Invite” (Server Settings → Roles → NFTicks). Servers that add the bot with the link above have it. Without it the button still links their account and the role still arrives, but they join through the invite link you put on the ticket page.

Two kinds can open the same role — set both up with the same role:. A buyer keeps the role while any ticket that opens it is valid.

4. Telegram: one group per kind of ticket

Telegram has no roles, so a kind of ticket opens a whole group. For a beginner and an advanced level, make two groups.

1. Add @nfticks_access_bot to the group and make it an administrator with two rights switched on: “Invite users via link” and “Ban users”.
2. Prove you are the organizer: open a private chat with the bot, send /verify, and sign with the wallet that created the tickets.
3. In the group, send /setup 14 with that ticket’s number. The bot replies with a join link for the group — share that, or the ticket link.
4. Repeat in the other group with the other number.

How the bot knows which ticket is for which group

/setup is sent inside the group, so the bot writes down “this group opens for ticket 14”. It never guesses. Several kinds can open the same group: send /setup once for each.

What your buyers do

Buy the ticket, then send /verify to the bot privately and sign. Within a minute the bot sends a private invite that works once, for them only. Somebody who taps the group’s join link is let in at once if they have verified, and told how to if not. When a ticket expires or is sold on, they are removed and told why — and let back in on their own if they buy again.

Online events: the link to join

For a call or a livestream, add the link people click to be there — Zoom, Google Meet, a stream. You do it on the page that appears right after you create the event, or later under the ticket in Your events.

Only somebody the blockchain says holds a valid ticket sees it, as a “Join the event” button on the ticket page and in My tickets. You can change the link any time, and a ticket sold on stops opening it.

5. Knowing who has access

In Your events, every kind of ticket shows where it opens — the server and role, or the group — and three numbers:

• Buyers — how many wallets hold it.
• Inside — how many are in the channel or group because of it, right now.
• Not linked yet — buyers who have not typed /verify. They hold the ticket, but the bot cannot know who they are until they do. These are the people who would otherwise write to you saying they paid and cannot get in.

Nobody on your side approves anybody. The bots check the blockchain every twenty to sixty seconds and correct whatever has changed, and every entry and removal is recorded with its reason.

6. The door: events people walk into

What the guest shows

In My tickets, the ticket has a “Show entry code” button. It shows a QR code that changes every twenty seconds, so a screenshot sent to a friend will not get them in. Somebody holding three tickets can come in three times, not four.

What your staff do

1. In Your events, press “Door staff link” and send it to whoever works the door. It needs no account and can do nothing except check tickets in for your events.
2. They open it on their phone and press “Start scanning”.
3. They point the camera at the guest’s code. The whole screen turns green — “Let them in” — or red with the reason: an old code, a ticket sold on, a ticket already used, or a ticket for somebody else’s event.

Keep resale closed before the doors open — the default closes it a day before — so a ticket that has been used cannot be sold on to somebody else waiting outside. The door phone needs mobile data.

7. When something is off

“I paid and I cannot get into the channel.”

On Discord, they press “Get your Discord role” on the ticket page or in My tickets; anywhere, they can type /verify. Either way they sign with the wallet that holds the ticket. If they bought with their email, they sign in with the same email.

/setup says only the organizer can set it up.

Type /verify first and sign with the wallet that created the tickets — the one your sales are paid into.

Discord: the bot cannot give the role.

Drag the NFTicks role above the ticket roles in Server Settings → Roles. The bot says so when you run /setup.

Telegram: the bot does not invite anybody.

It needs to be an administrator with “Invite users via link” and “Ban users”; it lists which one is missing when you run /setup.

The door says the code has expired.

The guest is showing a screenshot or a screen left open too long. They open the ticket again and the new code works.