> For the complete documentation index, see [llms.txt](https://selyo.gitbook.io/selyo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://selyo.gitbook.io/selyo-docs/archive/quest-experience.md). # Quest Experience There are some events where the organizers would require you to visit all the booth/sponsors and ask for a "stamp". When you finish all the booths/sponsors, you will now qualify for a raffle or a special prize. We bring this experience digitally through the use of QuestCards and PANATAK. Now, your participants will just "tap" their QuestCards to these devices provided in the booths and in effect, they will receive an NFT for "visiting" the booth or completing a quest. Their QuestCards also provides a link to a personal profile where one can see their Quest achievements . It also serves a digital calling card as they can also share the info provided on their profile page to other participants as well. This functionality refers to as "Booth Stamp". The PANATAK scanner device can also support different other roles as assigned to them. ### Timestamp Role When a scanner has a "Timestamp" role, they can be used to record the instance a participant goes IN or OUT of a venue or a hall. This will help record the number of participants a certain activity has. ### Boothstamp Role Mentioned above in the Quest experience, a boothstamp role is provide to scanners which is located in the sponsor booths. Participants who tap their QuestCards in scanner with this role will, in effect, receive an NFT provided by the sponsor booth. ### Merchant claim Role This can be used for giving away limited amoun of merchandise to monitor claims by the participants ### Voting role This can be used for doing a poll/election which will count each unique tap by participants. Alternatively, this can also be accessed with the web application for polls with several options. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://selyo.gitbook.io/selyo-docs/archive/quest-experience.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.