> For the complete documentation index, see [llms.txt](https://arcanahq.gitbook.io/project-arcana/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arcanahq.gitbook.io/project-arcana/the-build/dignitas-emblems.md). # --- Dignitas Emblems --- The Arcana Credentialling Engine strongly integrated with another key build of Arcana - Dignitas Emblems. Using Soul-Bound-Token technologies, Arcana allows users to store their gaming legacies verifiably, immutably, and perpetually on the block chain. By offering a practical use case with no avenue for monetary churn, we hope to use this as a proof of concept to the practical benefits of blockchain for gaming. The intrinsic goal of Dignitas Emblems is to celebrate gaming achievements for everyday gamers and to allow like-minded individuals to discover and connect with one another. Beyond high fidelity storage though, Dignitas Emblem SBTs will also unlock extrinsic benefits for gamers over time. Connecting gamers with the relevant backgrounds to work with studios they love, playtest new games, attain privileged access, these are just some of the practical benefits we seek build and expand on. --- # 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://arcanahq.gitbook.io/project-arcana/the-build/dignitas-emblems.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.