# Pons CTO and CTO token fees

At T+24 h of each operation, the team submits the official Pons CTO application for the CTO token. If Pons accepts, 100% of that token's future creator fees (0.7% base share plus its creator tax) buy back and burn $VIVRA. This is the project's flywheel.

## The CTO application

The form at `cto.ponsfamily.com` asks for:

| Field | Prepared by |
| --- | --- |
| Applicant email and X account | team (the CTO token's new X account) |
| Contract address | project analysis |
| New fee recipient wallet | Vivra's CTO Fees wallet |
| Takeover plan description | Scanner and CM, from the token dossier |
| At least one community link | Telegram opened by TG Bot |
| Verification tweet tagging @ponsdotfamily and naming the token | CM, published after approval |

A team member submits the application, never an agent. Its status is tracked in the back-office: submitted, accepted, rejected.

## On-chain behavior

- **Pons v2**: after approval, Pons proposes the new recipient. Tracking reads `pendingCreatorFeeRecipient(token)` (3-day wait, then a 3-day execution window) and the `CreatorFeeRecipientUpdated` event.
- **Pons v1**: Pons sets redirection through the locker (`feeRedirects(token)`).
- Only future fees change recipient. Fees already credited to the developer remain theirs.

## Fee recipient

One CTO Fees wallet receives creator fees from all CTO tokens. Daily, the treasury job calls `claim()` or `claimToken(token)` on Pons escrow; the Buyback Bot then uses 100% of the amount to buy back and burn $VIVRA (section 7). Per-token attribution for the ledger comes from escrow `Credited` events.

Confirm with Pons that one wallet can receive fees from multiple CTO tokens.

## Day 30 handover

| Item | What is transferred |
| --- | --- |
| Telegram | group ownership to the 3 chosen moderators |
| CTO token X account | credentials to moderators; CM reduces activity to 1 post per month |
| Website | remains on the Vivra subdomain; moderators receive a website export |
| Creator fees | remain with Vivra: 100% buys back and burns $VIVRA |

## If Pons rejects the application

The operation continues: agents, buyback, and verdict do not depend on Pons CTO approval. Only the fee flywheel fails to start for that token. The dapp displays the application status on the dossier.

## Acceptance criteria

- [ ] On testnet, a test token redirects its recipient to the CTO Fees wallet: a claim followed by $VIVRA buyback and burn is visible in the ledger.
- [ ] A test CTO application is generated and reviewed in under 30 minutes.