> For the complete documentation index, see [llms.txt](https://maxi-science.gitbook.io/manual-maxi-registry/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://maxi-science.gitbook.io/manual-maxi-registry/introduction-to-intellectual-property-and-blockchain-registry.md).

# Introduction to Intellectual Property & Blockchain Registry

The digital era has brought unprecedented innovation, providing new ways to create, share and protect content. With the advancement of technologies, intellectual property (IP) and its management have become a fundamental issue. The importance of IP protection is on the rise, and blockchain registration is emerging as a promising tool to protect the rights of inventors, scientists, innovators, creators and artists.

In this manual, we will explore the fundamentals of intellectual property, the  legislation that protects it, and how blockchain technology can be applied to ensure the security and authenticity of IP records.


---

# 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://maxi-science.gitbook.io/manual-maxi-registry/introduction-to-intellectual-property-and-blockchain-registry.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.