> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/protocol/anti-vamping.md).

# Anti-Vamping

Explains proposed recipient-change safeguards, including early changes, seven-day cooldowns, and post-day-30 Lock or Flexible modes.

Anti-vamping is a proposed protection for creator fee recipients. It aims to preserve correction flexibility while limiting repeated recipient changes.

### Recipient-change lifecycle

{% stepper %}
{% step %}

#### Days 1 to 7

The creator may make one recipient change. Any later change is subject to a seven-day cooldown.
{% endstep %}

{% step %}

#### Days 8 to 30

The creator may make one additional recipient change, subject to the same seven-day cooldown.
{% endstep %}

{% step %}

#### Day 31 onward

The creator chooses between **Lock** and **Flexible**. The default is **Lock**.
{% endstep %}
{% endstepper %}

### Available paths after day 30

{% columns %}
{% column %}

#### Lock

The recipient becomes immutable.

This path is intended to signal commitment and maximize community trust.
{% endcolumn %}

{% column %}

#### Flexible

The 7-day cooldown continues.

This path is intended for legitimate recipient migrations.
{% endcolumn %}
{% endcolumns %}

### Design intent

* Early configuration mistakes can be corrected.
* Repeated recipient changes become constrained over time.
* Long-term creators can choose a stronger commitment signal.
* Legitimate migrations remain possible through the flexible path.

{% hint style="warning" %}
This anti-vamping design is proposed. It has not been deployed, audited, or validated in production.
{% endhint %}


---

# 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://whitepaper.getpaid.family/protocol/anti-vamping.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.