Skip to main content
GET
Returns what the instance behind the API key earns as a distributor in one vault. That is what it has been paid, what the vault holds for it now, and an estimate of its part still waiting on the markets. Every figure covers your instance’s own verified wallets only. The vault’s operator also gets an operator block with its own share and every other distributor’s standing. Any vault visible to your instance can be read, including an unpublished one in which your instance is a distributor of record.

How a distributor earns

The instance whose API key builds a depositor’s first attributed deposit becomes that depositor’s distributor. That holds for Deposit and for a market’s Deposit to Vault route alike. The vault binds the holder to that instance’s distributor wallet once and attributes every share the holder has or later receives to it. As borrowers repay, each market the vault funds sets aside a distributor share for its liquidity providers. That share is 5 percent of the interest left after Trusset’s 15 percent infrastructure fee, plus 5 percent of each fixed transaction fee. The vault’s part is its slice, and it waits on the market until someone collects it.
  1. Collect Distributor Fees pulls one market’s slice into the vault. The vault credits the part earned by attributed shares to their distributors and the rest, earned by shares no distributor brought, to the vault operator.
  2. Pay Distributor sends a distributor’s credit to its payout wallet. Pay Operator Fees sends the operator’s credit to the vault owner.
All three are open to any signer on-chain and pay only fixed recipients, so a keeper can run them. The API builds Pay Operator Fees for the operating instance only. Trusset holds none of these funds.

When the figures are read

The payout history comes from the vault’s events, recorded up to the last settled block. That is the finalized block, or five blocks behind the head on a chain that reports no finality. When history.complete is true, the balances, claims and payout history are all read at history.asOfBlock. The page then trails the chain head by the finality delay, and a payout you just confirmed appears once its block is final. When history.complete is false, the vault and market figures are read live and paid and earned cover only the blocks read so far. A vault created in a block that is not final yet carries history.pendingFinality: true until it is.

Path Parameters

string
required
Vault ID.

Response Fields

Every amount is an object { raw, value }: raw in base units of the vault’s asset, value formatted at its decimals.
object

Error Codes