> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/help/comprehensive-overview-electronic-registries-and-verifiable-credentials/electronic-registries/what-issues-will-electronic-registries-address.md). # What issues will Electronic Registries address? With the technological advancements “Digital Registries” are becoming the need of the day in every sector. These registries do not just provide data about entities they are designed for, but enable verification and authentication of the entities, thus making the information stored “reliable “ & “trustworthy”. One of example of the digital registry is AADHAAR- National Identity Registry for India, which enables storing, authentication & online verification of Indian citizens and is widely used for all Government program enrollments, beneficiary verification, and citizen’s identity data validation. In addition, if these registries are augmented with the capability to issue digitally verifiable credentials (VC) enabling offline & online verification of the entity/holder in question can turn out to be the solution to “augment trust” & reduce frauds in any sector. By having verified data within various registries, stakeholders and partners can easily enroll and access these services and benefits, while eliminating the need for repeated data collection and validation. Additionally, the use of open APIs allows other systems to easily onboard users and share data, further streamlining the 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://rc.sunbird.org/help/comprehensive-overview-electronic-registries-and-verifiable-credentials/electronic-registries/what-issues-will-electronic-registries-address.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.