> For the complete documentation index, see [llms.txt](https://verify-doc.taplink.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://verify-doc.taplink.network/introduction.md). # Introduction The project aims to build a system to authenticate genuine products and track their origins using NFC chips and blockchain technology. Each product will contain an NFC tag with a unique ID stored. Mobile apps can scan these tags and verify against a blockchain record to determine authenticity. **Key Technologies:** * **NFC chips:** To store and retrieve unique product identifiers * **Mobile app:** To read NFC tags and connect to blockchain * **Blockchain network:** To store product IDs and validation records transparently * **Smart contracts:** Business logic to authenticate NFC IDs via blockchain * **Cloud hosting:** To host backend API and off-chain components **Key Features:** * Scan NFC tags on products using a mobile app to extract unique ID * Check ID against blockchain record to authenticate products * Transparently track validation history of each product on blockchain * Trace product origins back using supply chain data on blockchain * Tamper-proof system to build customer trust. --- # 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://verify-doc.taplink.network/introduction.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.