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
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.
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.
Submit a CTO request
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.
Review boundary
Submitting a request does not change public token state. 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:Verify on-chain state
Blank verifies the on-chain fee split config before writing the approved
state.