> For the complete documentation index, see [llms.txt](https://docs.fortunaway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortunaway.com/fortuna-id/what-is-fortuna-id/onchain-credentials.md). # Onchain Credentials Onchain Credentials are verifiable records that represent a user’s participation, achievements, roles, or cultural engagement within FortunaWay. A credential may be issued when a user completes a quest, joins a campaign, attends an event, contributes content, supports localization, or reaches a specific membership milestone. These credentials can be designed as non-transferable or limited-transfer records, depending on the use case. The purpose of Fortuna Credentials is not to create collectible assets for speculation. Their main function is to provide proof of participation, proof of contribution, and proof of membership within the FortunaWay identity network. Technically, credentials can be implemented through different models: * Onchain attestations * Soulbound or non-transferable credentials * NFT-based membership badges * Offchain verifiable credentials with onchain references * Partner-issued campaign credentials * Role-based access credentials This gives FortunaWay a flexible credential system that can support identity, reputation, access control, and ecosystem collaboration. --- # 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://docs.fortunaway.com/fortuna-id/what-is-fortuna-id/onchain-credentials.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.