> 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/wallet-connection.md). # Wallet Connection Wallet connection is the primary entry point for Fortuna ID. It allows users to create or access their FortunaWay identity without relying on traditional username-password accounts. When a user connects a wallet, FortunaWay can associate that address with a profile, quest history, credentials, membership roles, and contribution records. Wallet signatures can be used for authentication, helping verify that the user controls the connected address without exposing private keys. Fortuna ID can support common wallet connection standards across EVM-compatible networks and future multi-chain environments. The wallet acts as the user’s identity key, while FortunaWay provides the cultural identity layer built on top of it. Key technical functions include: * Wallet-based login * Signature-based authentication * Address-linked identity profile * Quest and credential association * Multi-chain compatibility planning * Basic anti-sybil and anti-abuse checks --- # 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/wallet-connection.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.