> For the complete documentation index, see [llms.txt](https://docs.phynite.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phynite.io/technology/phynite-protocol/8.-conclusion.md). # 8. Conclusion We have proposed a system for the digital trade of ownership rights of physical items without relying on trust. We used the innovative technology of NFTs provided by Ethereum, and built on top of the transparency and decentralization of blockchain to connect the blockchain network to the real world. By combining the power of the established US legal system and blockchain, we have created the concept of Contractually Bound Non-Fungible Tokens, or NFTs which can legally obligate parties to carry out certain actions depending on its state. We have provided solutions to publicly store digital signatures of legally binding contracts on the blockchain to be used as digital receipts, while maintaining the privacy of users’ contact information. Although having a guardian company hold the physical items creates a lack of decentralization in certain aspects, decentralization is a feature that is used to replace trust, and we believe that the incentives created by the legally obligating power of the Phynite Protocol can serve that purpose as well. --- # 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://docs.phynite.io/technology/phynite-protocol/8.-conclusion.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.