Fixed treasury yield
How operators configure the fixed-treasury-yield token feature for periodic holder-claimed yield from a configured treasury wallet.
The fixed-treasury-yield token feature accrues a periodic yield per holder, claimable against a configured treasury wallet. Use it for bond coupons, deposit interest, money-market-fund distributions, or any instrument that pays a fixed-rate periodic return drawn from a funded treasury.
For the architecture reference, see Fixed treasury yield.
When it attaches
Most bond templates, the deposit template, money-market-fund, and several structured templates include fixed-treasury-yield. See the system templates catalog.
What you configure
In the Asset Designer details step, the wizard surfaces:
| Parameter | Description |
|---|---|
denominationAsset | ERC-20 token that yield pays in. |
basisPerUnit | The unit-of-account the rate applies to. For most instruments, one token. |
treasury | Wallet the yield draws from. The operator funds this wallet on the published schedule. |
startDate | When accrual begins. |
endDate | When accrual stops. Defaults to the maturity date for bond templates. |
rate | Per-period rate in basis points. 500 means 5% per period. |
interval | Accrual interval (DAILY is the typical seed default). |
For convertible-note and money-market-fund templates, the wizard inherits the denomination asset from the redemption configuration when the two features compose.
What you operate
After deployment:
- Fund the treasury on the published schedule. The platform tracks the running yield-coverage shortfall and surfaces a coverage indicator in the asset detail workspace's yield tab.
- Monitor coverage through the yield-coverage statistics. A persistent shortfall blocks holder claims until the treasury is topped up.
- Holders claim their accrued yield through the platform's claim flow. Each claim transfers the holder's accrued amount from the treasury to the holder and resets the holder's accrual clock to the claim block.
- End accrual when the asset reaches
endDate. The feature stops accruing for blocks past that date.
Operating considerations
- Accrual is per holder per block-aware tick. A holder who transfers their position to another wallet stops accruing on the source wallet and starts accruing on the destination wallet starting at the transfer block.
- The treasury can be a wallet under operator control or a smart contract that allowances the yield feature to spend. Most operating models use a wallet for simplicity.
- The feature does not enforce that the treasury holds enough denomination asset to cover all accrued claims. Underfunding the treasury is an operating-discipline issue the platform reports through the coverage indicator.
- Rate changes are restricted-mutable. Plan rate updates around accrual-period boundaries to avoid mid-period rate ambiguity for holders.
Troubleshooting
| What you see | What to check |
|---|---|
| Holder cannot claim yield | Confirm the holder accrual is non-zero and the treasury holds at least the claim amount in the denomination asset. |
| Coverage indicator shows red | Top up the treasury with the denomination asset before the next claim window. |
Yield accrues past endDate | Confirm the endDate is set correctly. The feature stops new accrual after endDate but does not erase prior accrual. |
| Rate change does not take effect | Restricted-mutable updates run through the governance-update path and are asynchronous; wait for the on-chain transaction to confirm. |
Read next
- Fixed treasury yield architecture
- Maturity redemption — often paired for fixed-income instruments.
- Yield coverage statistics API
Maturity redemption
How operators configure the maturity-redemption token feature during asset creation and trigger holder redemption when a fixed-income asset reaches its maturity date.
AUM fee
How operators configure the aum-fee token feature for periodic management-fee accrual against assets under management.