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

# Community Takeover

> How Blank handles manual community takeover requests for abandoned tokens, including requester requirements, review boundaries, and approval effects.

# Community Takeover

<Info>
  Community takeover is a manual review path for abandoned tokens. It is not a
  public eligibility state, not an automatic holder vote, and not a tokenomics
  migration.
</Info>

## When to request

Use CTO review only when the original creator appears to have abandoned the token and the community has enough evidence for Blank to review.

A request should include:

* Token CA.
* Connected verified requester wallet. This becomes the CTO controller if approved.
* Telegram username for the requester.
* Evidence that the original creator abandoned the token.
* Proof that the community supports the takeover.
* Evidence links and future creator-fee recipients.

The request is tied to the connected verified wallet. Blank keeps review state internal and only shows a public CTO badge after an approved execution is complete.

<Card title="Submit a CTO request" href="https://blank.build/cto-request" cta="Open CTO Request Form" arrow="true">
  Use the app form after you have the token CA, requester wallet, Telegram
  username, abandonment evidence, community proof, evidence links, and proposed
  creator-fee recipients.
</Card>

## Review boundary

Submitting a request does not change public token state.

<Warning>
  No in-review CTO state appears on token pages, and no public CTO badge appears
  before approval execution.
</Warning>

Admins can mark requests in review, rejected, or cancelled internally.

## What CTO can change

A completed CTO can change future control and creator-fee routing only:

* Creator dashboard ownership moves to the approved requester account.
* Future creator-fee controller wallet changes to the approved requester wallet.
* Future creator-fee recipient wallets and shares can change.
* The token page shows a public CTO badge after completion.

## What CTO does not change

* Tokenomics are not rewritten.
* Historical creator attribution remains stored internally.
* Past creator-fee distribution history is not rewritten.
* Vesting and allocation rights stay tied to the original tokenomics setup.

## Approval flow

After manual approval, Blank:

<Steps>
  <Step title="Settle old creator fees">
    Blank settles accrued creator fees under the old active split.
  </Step>

  <Step title="Execute the admin transaction">
    Blank submits the admin CTO transaction from the worker.
  </Step>

  <Step title="Verify on-chain state">
    Blank verifies the on-chain fee split config before writing the approved
    state.
  </Step>

  <Step title="Record the CTO split">
    Blank records the new split source as CTO.
  </Step>

  <Step title="Transfer dashboard control">
    The requester can manage the token from the creator dashboard.
  </Step>

  <Step title="Show the public badge">
    The token page shows the public CTO badge after completion.
  </Step>
</Steps>