.

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

Days 1 to 7

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

Days 8 to 30

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

Day 31 onward

The creator chooses between Lock and Flexible. The default is Lock.

Available paths after day 30

Lock

The recipient becomes immutable.

This path is intended to signal commitment and maximize community trust.

Flexible

The 7-day cooldown continues.

This path is intended for legitimate recipient migrations.

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.

WARNING

This anti-vamping design is proposed. It has not been deployed, audited, or validated in production.