Token
$COMPOUND is the token for this project. Here is what it is, where its fees go, and what it deliberately does not do.
What it has to do with the vaults
Short answer: nothing mechanical. The token and the vaults are separate, and it is worth being exact about that before anything else on this page.
- Depositing does not earn you $COMPOUND. Your fees compound back into your own position, which is the whole design. There is no reward token layered on top.
- Holding $COMPOUND does not change your vault position. Not your fees, not your share of the pool, and not your ability to withdraw.
- You never need it to use the app. Nothing in the deposit or withdrawal path asks for it, checks for it, or benefits from it.
Where the fees go
$COMPOUND launches on Pons v2, and trading it generates fees. Those fees, the ones the token's own market produces, are allocated three ways:
How this is carried out
The allocation above is the intended policy for revenue the token generates. It is not enforced by the vault contracts, which have no knowledge of the token and no mechanism for splitting anything: the vault's own fee goes to a single address fixed when the vault was built, and nothing about that changes here.
If the split later moves into a contract of its own, this is the section that will change, and it will name and link that contract so the claim can be checked rather than taken on trust.
What it does not do
- It is not a governance token and confers no vote. This is not a policy choice that could be reversed later: the vaults are immutable, so there is no parameter for a vote to change and no function through which to change one.
- It cannot alter the vault fee. That is fixed at construction at 1% of collected fees and cannot be raised by anyone, ourselves included.
- It carries no claim on vault deposits. Holders have no entitlement to the assets in any vault, or to the fees those vaults collect.
- It does not make the app depend on us. Compounding stays permissionless whether the token exists, thrives or fails.
