Treasury Distribution
How DALP fixed treasury yield uses a configured treasury address to fund holder-initiated claims for completed yield periods.
Fixed treasury yield pays token holders from a configured treasury address. The treasury is external to the token contract. DALP records claims on-chain and indexes the distribution state for operators and auditors.
System context
The asset token does not hold a separate treasury balance for fixed treasury yield. Payment capacity depends on the configured treasury address and denomination asset.
Configuration model
A fixed treasury yield feature binds one token to a yield schedule and payout source.
| Configuration item | What it controls |
|---|---|
| Token | The asset whose holders can accrue yield. |
| Denomination asset | The payment asset used for yield claims. |
| Treasury | The address that funds payouts. |
| Yield basis | The basis amount used to convert holder balances into claimable yield. |
| Rate | The yield rate applied by the feature. |
| Start date, end date, and interval | The period schedule used to calculate completed yield periods. |
The fixed treasury yield feature stores the treasury address that funds payments. Externally owned treasuries use ERC20 allowance. Vault-style treasuries use the supported payout interface. The asset contract does not hold a separate treasury balance for fixed treasury yield.
Claim flow
Holders claim yield after eligible periods have completed. DALP does not automatically push each yield payment to every holder.
DALP calculates period end timestamps from the start date, end date, and interval. Holder entitlement depends on balances at completed period boundaries. The feature resolves a historical-balance provider when the feature is attached to the token.
A claim records the holder, the net claimed amount, the first and last claimed period, per-period holder amounts, per-period total yields, and the estimated total yield per period. The feature also tracks total claimed amount, consumed interest, and accrual closure state so later claims use the remaining net entitlement.
Treasury ownership and allowance
The treasury address is an operational funding source for payouts.
- An externally owned treasury must approve enough denomination asset allowance for the feature to pay claims.
- A vault-style treasury must support the payout interface expected by the feature.
- Governance can update the treasury address.
- A zero-address treasury update is rejected.
- Treasury updates emit an on-chain event for auditability.
A holder may have no claimable yield when no period has completed, when the holder had no eligible balance at completed period boundaries, when the holder already claimed those periods, or when consumed interest offsets the available amount.
Indexed distribution view
DALP exposes the fixed treasury yield state through indexed data rather than requiring operators to reconstruct every claim from live chain reads.
The indexed view includes:
- the yield schedule and configured treasury address;
- the denomination asset;
- whether the treasury is classified as a contract when that information is available;
- claimed and unclaimed yield values;
- period-level distribution data.
Use the indexed view for monitoring distribution progress, reconciling holder claims, and checking whether the treasury configuration matches the intended payout source.
Audit evidence
The fixed treasury yield model gives auditors three useful evidence layers:
- Configuration evidence: token, denomination asset, treasury, rate, basis, and schedule.
- Claim evidence: holder, claimed amount, claimed periods, and period-level yield data.
- Treasury evidence: current treasury address and treasury update events.
These evidence layers show how DALP calculated and recorded holder claims. They do not prove the economic source of funds before funds reach the configured treasury.
Boundaries
Coupon payments, maturity redemption, reserve verification, and external treasury-operator duties are outside fixed treasury yield.
For the broader compliance model, see asset policy. For architecture flow navigation, see architecture flows.
Airdrop distribution flow
How DALP moves tokens from a funded airdrop contract to eligible addresses, including Merkle proof checks, claim tracking, strategy variants, and failure modes.
XvP settlement flow
How the DALP XvP settlement flow executes atomic multi-party token exchanges, from settlement creation through approval collection and optional hashlock coordination for external-chain legs to all-or-nothing execution.