> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/public-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/public-docs/products/digital-product-passport.md). # Digital Product Passport The Legitimate Digital Product Passport utilizes blockchain to permanently store to back products on-chain. ## Legitimate Protocol The Legitimate Protocol is an blockchain based framework designed to keep physical assets in-sync with their digital counterparts in terms of ownership and provenance. When a product is integrated into the Legitimate Protocol, it becomes a connected product. [Legitimate Tags](/public-docs/legitimate-tags/tag-catalog.md) and the [Legitimate](/public-docs/products/verify-experience.md) platform enable customers to verify authenticity and ownership of physical goods through our services. Our product data including product information, individual creation dates, and anonymized owner identifiers. These data are stored on blockchains so it can be independently accessed and verified for authenticity and circularity tracking. ### How it works Connected products powered by Legitimate's Protocol have a few key features: * Locking Mechanism on the Digital Product NFT * The Digital Product NFT is cannot be transferred or used until the current owner reads the tag with their phone to verify. * Secure * When an owner of a phygital product transfers the Digital Product NFT to another person, the NFT is immediately locked again. The only way to unlock the NFT is by using the Legitimate Tag attached to the product. * Extensible * Third party exchanges, marketplaces, and applications can build on top of this transfer restricted NFT state to provide token gated content, access, and more.

--- # 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.legitimate.tech/public-docs/products/digital-product-passport.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.