> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/truvera-workspace/truvera-workspace-release-notes/2024-release-notes/release-notes-december-2024.md). # Release notes December 2024 ## v1.50.0 December 17 Rebrand from Dock to Truvera and support for did:cheqd. ### Updates and new features DCKA-3000 Added support for arrays data type in credential schemas. DCKA-2954 API Accumulator support for cheqd DCKA-3026 Adding an alias to API key improves the usability ### Bug fixes DCKA-3029 Fixed an error when some attributes were not visible on the webview and the wallet giving the error "input.descriptor\[0]" ## v1.49.0 December 12 ### Updates and new features DCKA-2992 Updated the API to fix "Unknown type for key in schema: date" error. ### Bug fixes DCKA-2969 Fixed an issue with exporting DIDs that are on cheqd blockchain. ## v1.48.0 December 9 ### Updates and new features Cheqd blockchain support (alpha testers only) DCKA-2914 Add cheqd as a DID method in Certs DCKA-2955 API StatusListCredential support for cheqd DCKA-2956 API TrustRegistry support for cheqd ### Bug fixes DCKA-2986 Fixed an error that occured, when trying to verify only a date range attribute in a ZKP credential. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.truvera.io/truvera-workspace/truvera-workspace-release-notes/2024-release-notes/release-notes-december-2024.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.