> For the complete documentation index, see [llms.txt](https://docs.verio.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verio.network/verio/staking-on-ip-assets.md).

# Staking on IP Assets

## Problem <a href="#problem" id="problem"></a>

A problem with registered IP Assets is that they may unintentionally or deliberately violate existing IPs on the network, posing risks for existing IP holders and future creators. For example, if you came across a comic with a compelling superhero character and decided to create a new comic using that character's persona and background, you would register a derivative IP based on the original IP and mint a license tailored to your needs. However, if it turns out that the original IP infringes on another existing IP, that original IP and your derivative IP will both be frozen, rendering your time and money wasted. To prevent the above situations and especially with the ease of registering IPs onto Story leading to potentially malicious actors intentionally registering illegitimate IPs, there needs to be a metric indicating the degree of an IP's validity.

## Solution <a href="#problem" id="problem"></a>

Just as liquid staking enables users to participate in network security, IP asset re-staking allows them to signal the value and legitimacy of their favorite assets. Creators can register their IP assets with Verio, and offer incentives to reward users for staking on them.

In Verio’s IP asset re-staking system, stake weight serves as a powerful filter for determining the legitimacy and credibility of an IP. Since fraudulent or infringing IPs pose significant risks—both for original creators and derivative works—using stake as a decentralized legitimacy signal helps mitigate these issues without relying on centralized enforcement.


---

# 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.verio.network/verio/staking-on-ip-assets.md?ask=<question>&goal=<endgoal>
```

`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.