> For the complete documentation index, see [llms.txt](https://blocks-1.gitbook.io/blocks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blocks-1.gitbook.io/blocks/verified-by-blocks/overview.md). # Overview Verified by BLOCKS is a method of proving the authenticity of digital and real-world assets. It leverages the native data utility of the BLOCKS token, and the [Blocks Data Standard](https://github.com/blocks-dao/blocks-data-standard), to immutably store verification data on-chain. The verification process combines public and private information which is used to generate unique hash values. These hash values can be recreated by select partners via API to prove authenticity. The verification data is embedded within a BLOCKS transaction when tokens are sent to the smart contract address being verified. BLOCKS verification provides benefits to projects and end users:\ • Increased customer confidence\ • Improved project transparency\ • Independent on-chain verification\ • Reduced fraud Please see [Partner Onboarding](/blocks/verified-by-blocks/partner-onboarding.md) to learn more about obtaining credits. --- # 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://blocks-1.gitbook.io/blocks/verified-by-blocks/overview.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.