> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/technical-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/technical-docs/protocol/overview.md).

# Overview

This is a preview of our protocol. All documentation here is still work in progress.

## The Legitimate Protocol

The Legitimate Protocol is an secure decentralized framework designed to keep physical products in-sync with unique digital identities, specifically from an ownership and provenance perspective. When integrated into the Legitimate Protocol, a product is capable of becoming a phygital (physical + digital) product.

NFC Tags operating on the Legitimate protocol can be by used by customers to verify the authenticity and ownership of physical goods through Legitimate's infrastructure and decentralized smart contracts.

### How it works

NFC tags powered by the Legitimate protocol have a few key features:

* Unique Digital Identity
  * A decentralized digital ID that satisfies most provenance and traceability protocols, designed to track products through their entire lifecycle. Owners can scan the NFC tag to claim ownership of a product.
* Secure
  * A digital ID can be transferred from one owner to another to record any change in ownership. Our Locking Mechanism (defined below) is a secure escrow implementation that ensures the digital ID and the physical product belong to the same person.
* [Locking Mechanism](/technical-docs/protocol/smart-contracts/locking-mechanism.md)
  *  A digital ID is “locked” and cannot be unlocked or transferred until the NFC tag on the physical product is scanned by the new owner to unlock.
* Extensible
  * Third party developers can build on top of this “locked” digital ID state to provide exclusive gated content, access, and more.

<figure><img src="https://content.gitbook.com/content/uF8GxCCVKiHZhuxM0XLD/blobs/8n9pm9bflXgFBfQNpIfk/image.png" alt=""><figcaption><p>LGT Protocol Diagram</p></figcaption></figure>


---

# 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/technical-docs/protocol/overview.md?ask=<question>&goal=<user_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.