Fees & protocol revenue
Where fees can be earned, who has a claim on them, and why asset balances are not all spendable revenue.
In this chapter
Three implemented fee mechanisms
The contracts implement fees on isolated borrowing, acceptance of funded credit and routed swaps. They earn nothing merely by existing. Fees depend on deployment, actual usage, compatible integrations and successful settlement.
The read-only quote comparison does not run those contracts or collect revenue. No Serevin service fee or affiliate arrangement is configured for Route quotes or the external Route link. A provider’s reported platform fee is separate from pool fees, upstream charges and transaction gas.
| Activity | Fee mechanism | Form of protocol claim |
|---|---|---|
| Isolated borrowing | Configured share of accrued interest. | New supplier shares minted to the treasury. |
| Term-loan acceptance | Origination fee deducted from principal. | Loan assets accounted for separately as earned fees. |
| Routed swap | Fee deducted from the input amount. | An earned balance in that input token. |
Principal belongs to its claimant
Funds committed to an offer, collateral held for a borrower and assets backing supplier shares cannot be labeled ordinary protocol income. A reserve contribution is also different from an earned trading or lending fee.
A treasury can hold a claim before holding withdrawable cash. In isolated lending, fee shares depend on market liquidity for redemption. Swap fees may be held in several input assets and would need conversion before a policy denominated in another asset could be executed.
A useful revenue report therefore separates earned fees, currently claimable amounts, realized asset proceeds and completed spending. Gross volume and unrealized token appreciation do not belong in the same total.
What this means for SVRN holders
The current contracts do not automatically distribute protocol revenue to SVRN holders. There is no implemented fee-discount tier, voting entitlement, emissions rate or revenue-sharing schedule.
A redemption claim would depend on integrating a compatible token into the reserve, funding that reserve and finalizing the actual rights. Holding a market-traded token by itself does not establish those rights.
Buybacks and reinvestment remain separate work
The local treasury-buyback module accepts explicit funding from its configured treasury authority. Both administrators approve each purchase, including the adapter, amount, minimum tokens received, unique order reference and deadline. It verifies the actual decrease in token supply after burning. The canonical SVRN token is recorded; production funding, execution adapter admission and activation remain pending.
A direct transfer or a treasury budget named Buybacks does not create this module’s spendable budget. Allocation remains discretionary. There is no unattended spending schedule, automatic launchpad fee collection or holder payout.
A buyback exchanges existing assets for tokens. A burn reduces actual supply only if the token supports the required behavior. Neither guarantees a rising market price. Purchased tokens sent to vesting remain existing supply unless later burned.