> For the complete documentation index, see [llms.txt](https://vself-project.gitbook.io/vself-project-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vself-project.gitbook.io/vself-project-documentation/user-profile-toolkit/multi-chain-support.md). # Multi-chain support #### Chains Our next goal is to add multi-chain support to the user profile toolkit. We plan to support a large number of different chains, including but not limited to [Ethereum](https://ethereum.org/en/), [Polygon](https://polygon.technology/), and [Aurora](https://aurora.dev/). This improvement allows users to add NFTs from these chains to their profiles. #### Authorization & indexing Like in the NEAR-supported profile case, the user should authorize to add her NFTs from any of the supported chains. Authorization for the EVM-compatible chains is provided through [MetaMask](https://metamask.io/) using [Login.xyz](https://login.xyz/) JS SDK. Additional [TheGraph](https://thegraph.com/en/) sub-graphs for each chain monitors chain updates and provides the list of NFTs owned by the user. The user also can choose NFTs from this list to share on her public page. #### Storage Key pairs for different chains are stored in [GunDB](https://gun.eco/docs/Introduction), offline-first & distributed graph database with DID provided by the [Ceramic Key DID library](https://developers.ceramic.network/reference/accounts/key-did/). [Social DB](https://github.com/NearSocial/social-db/) is used as an on-chain data storage for public profiles for the multi-chain case. Social DB usage requires the NEAR ID to create a new user profile. For user profiles without NEAR ID, we provide a [smooth on-boarding](/vself-project-documentation/near-onboarding/smooth-onboarding.md) process. --- # 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://vself-project.gitbook.io/vself-project-documentation/user-profile-toolkit/multi-chain-support.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.