> ## Documentation Index
> Fetch the complete documentation index at: https://blank.build/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Auto Buyback and Burn

> How Auto Buyback and Burn routes part of creator-side trading fees into automatic buys and permanent token burns.

# Auto Buyback and Burn

Auto Buyback and Burn lets a creator route part of their creator-side trading fees into a dedicated buyback bucket. When enough SOL accrues, Blank buys the token on its own market and burns the bought tokens.

<Info>
  Buybacks are funded by the token's configured creator-side fee allocation.
  They do not add extra cost to trader swaps.
</Info>

<Card title="Project buyback budget" icon="calculator" href="/docs/start-here/fee-calculator">
  Use the Fee Calculator to estimate how much SOL routes to buybacks from a
  target market cap, volume assumption, and buyback allocation.
</Card>

## How it works

<Steps>
  <Step title="Creator sets an allocation">
    At launch, or later from the creator dashboard, the token controller chooses
    what share of creator-side fees goes to Auto Buyback and Burn.
  </Step>

  <Step title="Fees accrue in a buyback bucket">
    The fee-splitter books that share into `buyback_claimable`. This bucket is
    separate from creator payouts and staking rewards.
  </Step>

  <Step title="Blank schedules execution">
    When the bucket crosses the execution threshold, the worker schedules a
    delayed batch with retry and recovery handling.
  </Step>

  <Step title="The batch buys and burns">
    Blank buys the token through the active market, burns the bought Token-2022
    amount, and records the completed burn publicly.
  </Step>
</Steps>

## Public signals

Completed batches are visible on public token surfaces:

* a combined `BB` chart marker
* a public Auto Buyback and Burn supply action
* fee status totals for SOL routed to buyback and tokens burned
* lower current supply after the burn confirms

## Rules

* Allocation can be set at launch.
* Allocation can be increased later by the current token controller.
* Allocation cannot be reduced or turned off after launch.
* Staking, Auto Buyback and Burn, Liquidity Compounding, and Price Prediction allocations share the same creator-side fee budget and cannot exceed 100% combined.
* Failed or delayed batches do not stop trading; fees remain in the buyback bucket for retry.

## Developer fields

Use `buybackBurn.shareBps` in the launch payload to enable the feature at launch.

Use `GET /api/v1/token/{mint}/fees` to read:

* `buyback_burn_share_bps`
* `total_buyback_burn_earned`
* `vault_buyback_burn`
* `pending_buyback_burn`
* `distributed_buyback_burn`
* `buyback_burned_tokens_raw`

See [Launch Tokens](/docs/for-developers/launch) and [Fee Status](/docs/for-developers/fee-status) for API details.