Fees
Get Fee Split
Read how the market divides repaid interest between its fee legs and liquidity providers
GET
Returns how the market divides every unit of repaid interest, read from the contracts on each call rather than from stored configuration. Four named legs come off in a fixed order, and liquidity providers keep what is left.
The order never changes. Trusset’s infrastructure fee takes 15 percent of repaid interest first. Of the remainder, the operator takes a fixed 8 percent and the distributors a fixed 5 percent. The market’s insurance-fund rate then takes its share of what is left, and the liquidity providers receive the rest. Each leg rounds down, so the liquidity providers absorb the rounding. Interest recovered through a liquidation is split the same way.
Only one of these figures can move. The infrastructure rate is hardcoded, and the operator and distributor shares are constants on the factory that no party can set, raise, lower or redirect. The insurance-fund rate is the market’s
protocolFeeRate, zero by default, which the issuer sets through Update Market Config.
Nothing is paid out inline. Each leg is booked as a liability on the market and leaves through its own permissionless sweep. Get Cashflows shows what each leg has accrued, what has been swept and what is still pending.
Path Parameters
string
required
Market ID.
Response Fields
object
Read the split
rateBps and effectiveBps answer different questions. rateBps is the leg’s rate against its own base, which is what the contracts store. effectiveBps is what the leg takes out of repaid interest once the legs before it have come off.
On a FIXED_SHARES market at the default insurance-fund rate of zero, 100 units of repaid interest split as follows.
The fixed transaction fee is not part of this split. It is a flat charge on disbursement and repayment, shared 8 percent to the operator, 5 percent to the distributor leg and 87 percent to Trusset’s infrastructure liability.
transactionFees.shares states those rates.
The split is cached for up to 60 seconds, so a change made on chain can take that long to appear here.
