Docs / Fee schedule
Using Oarkel
Fee schedule
Every fee source, its rate, and where it goes.
Fee sources
| Fee | Charged on | Goes to | Rate |
|---|---|---|---|
| Creator fee | Every $OARKEL buy and sell on Pons | Harvested, mostly to buy back for the vault | Set by Pons; harvesting planned |
| Shroud fee | Each deposit into the pool | Fee vault | 0.25% |
| Unshroud fee | Each withdrawal, flat amount | Fee vault | 0.0005 ETH or 20 $OARKEL |
| Private transfer fee | Value sent to another key inside the pool | Fee vault | 0.10% |
| Relayer fee | Transactions sent through a relayer | The relayer that paid the gas | Set by each relayer, ETH only for now |
These are the values the pool will be deployed with. Every rate is a constructor argument, fixed forever at deploy, and the contract refuses any fee above 5%. Fees paid in $OARKEL raise the vault directly. Fees paid in ETH build up in the pool, anyone can sweep them to the fee address fixed at deploy, and the operator of that address is expected to swap them into $OARKEL and donate them. That last step is operated off-chain, not enforced by code. The practice app uses the same rates.
Why the unshroud fee is flat
A percentage exit fee would leak the size of the note being spent, and a fee tied to how old a note is would leak when it was created. A flat fee says nothing about either. The cost is that very small withdrawals are not worth making.
What public holders get
No fee share. Public $OARKEL can still benefit indirectly, since buybacks support the price and every shrouded token leaves the public float smaller, but yield itself is reserved for the vault.