# What is Creator Vault?

<figure><img src="/files/AuLBcGFsj1PjfMl07iz7" alt=""><figcaption></figcaption></figure>

### Who it’s for

* Creators who want on-chain authorship + licensing.
* Creators who want funding without losing rights.
* Communities that want verifiable support and rewards.
* Teams that want collaboration and incentive rails without payout ops.

### Platform vision

Creator Vault is built for creators who want to own, fund, and distribute IP end-to-end.

It replaces opaque platforms with smart-contract rules and on-chain provenance.

### What “on-chain” changes

* Funds move through contracts, not platform-held balances.
* Anyone can verify totals and payouts on-chain.

### What you get

* **Provenance**. On-chain authorship and verifiable history.
* **Programmable licensing**. Clear usage terms and access control.
* **Funding**. Campaigns that don’t require giving up rights.
* **Growth**. Bounties for distribution and marketing.
* **Community**. NFTs, drops, and co-ownership mechanics.
* **Real-world monetization**. Digital perks plus optional physical fulfillment.

### What Creator Vault is not

* It is not a chargeback-based payment system.
* It cannot “undo” confirmed transactions.
* It does not guarantee campaign delivery or submission quality.

{% hint style="warning" %}
Always treat links, bounties, and campaigns as untrusted until you verify them. Use official channels to confirm addresses and URLs.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://creator-vault.gitbook.io/documentation/creator-vault/welcome/what-is-creator-vault.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.