> For the complete documentation index, see [llms.txt](https://docs.tuum.tech/identify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tuum.tech/identify/basics/roadmap.md). # Roadmap ## Identify Snap * [x] Develop did:pkh plugin for Veramo * [x] Support did:key * [x] Support did:hedera * [x] Development of Core DID Functionalities - Generate, Issue and Verify Methods for DIDs and Verifiable Credentials * [x] Support configuring Hedera account using private key and accountId via an API * [x] Support snap features for Hedera * [x] Support snap features for other EVM chains such as Ethereum, Binance, Goerli, Polygon, etc * [x] Sync Verifiable Credentials between devices and browsers using Google Drive storage * [x] Support connecting to Hedera account using private key from within Metamask and/or snap dialog box * [x] Support connecting to Hedera account using mnemonics from within Metamask and activating the account by user sending some HBAR to the wallet ## Example website * [x] Showcase all the APIs of Identify Snap by letting the user interact with each API on the website such as resolving the DID, creating Verifiable Credentials, Verifiable Presentations, etc * [x] Showcase a very simple DID authentication mechanism whereby the website uses Verifiable Credentials and Verifiable Presentations for signing up and logging into the website * [x] Add a way to let users connect to their personal Google Drive which will be used to store their Verifiable Credentials remotely thereby enabling the sync feature when the user tries using the website from multiple browsers or devices --- # 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.tuum.tech/identify/basics/roadmap.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.