Overview
Liquid Treasury enables institutions to earn competitive yields on stablecoin holdings through blue-chip Tokenized Money Market Funds (TMMFs) — with instant redemptions available 24/7, subject to availability. Built on the Multiliquid Protocol, Liquid Treasury delivers institutional-grade access to Treasury yields with full compliance, on-chain transparency, and seamless integration. Available to U.S. and non-U.S. Accredited Investors. KYC/KYB required for all depositors.T-Bill Yield
Interest rates based on a discount to short-term U.S. Treasury Bill Rates. Real-world asset backing, not synthetic or DeFi-native.
Instant Liquidity
Redeem to stablecoins or blue-chip TMMFs instantly, 24/7/365, subject to availability.
Issuer Diversification
Multi-issuer TMMF reserve structure reduces counterparty risk. No single point of failure.
The Problem
Institutions must choose between earning yield or having liquidity. Traditional money market products force this tradeoff with settlement delays and redemption caps. No existing product offers all three: true instant liquidity, T-Bill yield, and issuer diversification.Why Liquid Treasury
The $TSY Token
Deposit stablecoins to mint $TSY tokens 1:1. Your token balance remains constant while interest accrues. Upon redemption, burn $TSY to receive principal plus accrued interest atomically.
$TSY is freely-transferrable on secondary. As DeFi integrations expand, holders can use $TSY as collateral in lending protocols, provide liquidity on DEXs, and integrate into yield strategies.
How It Works
1
Deposit
Send USDC to Liquid Treasury and receive $TSY tokens. Primary minters complete KYC/KYB onboarding. Deposits flow into the multi-issuer TMMF reserve, with a dedicated stablecoin buffer for instant redemptions.
2
Earn
Start accruing yield immediately. Returns are contractually tied to prevailing U.S. Treasury Bill yields, providing transparent, market-linked returns. Interest is calculated daily based on the 3-Month U.S. T-Bill Oracle rate.
3
Redeem
Withdraw to stablecoins, subject to availability, or TMMFs instantly, 24/7. The dedicated liquidity buffer enables stablecoin redemptions without waiting for underlying TMMF redemptions.
Reserve Architecture
Liquid Treasury’s reserve is split between yield-generating TMMF holdings and a stablecoin buffer that decouples redemption speed from settlement:TMMF Holdings (~80-95%)
Allocated across leading blue-chip Tokenized Money Market Funds, the yield-generating core of the reserve. Always available for atomic, in-kind redemptions.
Stablecoin Buffer (~5-20%)
Stablecoin reserve enabling instant redemptions without redeeming underlying TMMFs. Buffer replenishes on T+1/T+2 cycles from new deposits and TMMF redemptions. If the stablecoin buffer hits 0%, all transactions will be reverted.
Legal Structure
Liquid Treasury operates through a bankruptcy-remote Delaware Special Purpose Vehicle (SPV), providing clear legal separation and investor protection.- Contractual Interest: Interest is contractually tied to prevailing U.S. Treasury Bill yields, providing transparent, market-linked returns.
- Bankruptcy Remote: SPV assets are segregated and bankruptcy-remote, providing structural protection.
- On-Chain Verifiable: Real-time on-chain reserve verification for full transparency.
- Note Structure: Depositors become lenders to the SPV and sign a note purchase agreement.
DeFi Composability
$TSY is designed for seamless integration across DeFi:- Permissionless Transfers: Move $TSY freely between wallets and protocols.
- DeFi-Ready: Use as collateral, liquidity, or in yield strategies.
- Secondary Market Liquidity: Trade or swap $TSY on secondary markets.
- Soulbound Yield: $TSY is non-interest-bearing and freely transferrable. Only original minters can burn $TSY and claim their yield.
Compliance
KYC/KYB Verification
Required for all primary participants. Whitelist-enforced on-chain minting ensures only verified addresses receive newly issued tokens.
BSA/AML Compliance
Bank Secrecy Act and Anti-Money Laundering compliance. Blacklist enforcement for sanctioned or restricted addresses.
Segregated Reserve Custody
Segregated reserve custody via audited smart contracts using OpenZeppelin standards.
On-Chain Transparency
Real-time on-chain reserve verification. All state changes emit comprehensive events for auditability.
Integration Options
Liquid Treasury is designed for programmatic access — ideal for B2B2C platforms, trading desks, liquid funds, vault curators, exchanges, payment processors, and any business managing treasury operations at scale.- Smart Contracts: Direct on-chain interaction via ethers.js or web3.py for DeFi integrations
- REST API: Read-only deployment metadata, canonical EVM transaction history, and LP volume analytics
- SDK: TypeScript library for seamless integration into existing stacks
- CLI Tool: Command-line interface for automated treasury operations and scripting workflows
See the API Reference for REST endpoints. For
on-chain integration details, contract ABIs, and technical specifications,
see the Integration Guide.
Technical Reference
The sections below provide detailed smart contract documentation for developers integrating directly with Liquid Treasury’s on-chain infrastructure.Contract Architecture
Treasury Token
- ERC20Upgradeable: Standard token functionality
- ERC20BurnableUpgradeable: Burn capability
- ERC20PermitUpgradeable: EIP-2612 gasless approvals
- AccessControlEnumerableUpgradeable: Role-based permissions with enumeration
- PausableUpgradeable: Emergency pause capability
- ReentrancyGuardUpgradeable: Reentrancy attack protection
- UUPSUpgradeable: Secure upgrade mechanism
Deployment Model
The treasury token can be deployed independently on multiple chains, connected via bridge contracts: Each deployment is independent but connected via bridges:- Same token name and symbol across chains
- Separate role administration per chain
- Bridge contracts handle cross-chain transfers via burn-and-mint
Core Functions
Minting
mint (Primary Issuance) Mint tokens to whitelisted addresses only. Used for initial token issuance to institutional clients after KYC/KYB verification.- Caller must have
MINTER_ROLE - Recipient must be whitelisted (
whitelisted[to] == true) - Contract must not be paused
- Amount must be non-zero
AccountNotWhitelisted(to) if recipient is not whitelisted, InvalidAmount() if amount is zero
Whitelist enforcement on primary issuance ensures KYC/KYB compliance. Only addresses that have completed the onboarding process can receive newly minted tokens.
- Caller must have
BRIDGE_ROLE - Recipient must not be the zero address
- Contract must not be paused
- Amount must be non-zero
BridgeMint(bridge, to, amount) for off-chain monitoring before the standard Transfer event.
Burning
burnFrom requires prior approval from the token holder. If the caller has BRIDGE_ROLE, a BridgeBurn event is emitted for off-chain monitoring in addition to the standard Transfer event.
Requirements:
- Amount must be non-zero
- Contract must not be paused
burnFromrequires sufficient allowance
Transfers
Standard ERC-20transfer and transferFrom functions. Transfers are permissionless with two exceptions:
- Blacklist enforcement: Both sender and receiver are checked against the blacklist on every transfer (including mints and burns). Blacklisted addresses cannot send or receive tokens.
- Pause enforcement: All transfers are blocked when the contract is paused.
Whitelist enforcement applies only to
mint() (primary issuance). Transfers between addresses are unrestricted beyond blacklist and pause checks. This enables $TSY to trade freely on secondary markets and integrate with DeFi protocols.EIP-2612 Permit
- User signs an approval message off-chain
- A relayer submits the
permit()transaction (pays gas) - Approval is set without requiring a transaction from the user
- Subsequent
transferFrom()orburnFrom()can execute immediately
Bridge Integration
Bridge Management
Bridges are managed through role-based access control. TheOPERATOR_ROLE can add and remove bridges:
BRIDGE_ROLE; removing a bridge revokes it. Each operation emits BridgeAdded or BridgeRemoved events.
Multiple bridges can operate simultaneously, providing redundancy, distributed risk, and competitive routing options.
TreasuryOFTAdapter (LayerZero)
A reference bridge implementation using LayerZero’s OFT (Omnichain Fungible Token) protocol:- Source chain: Burns tokens via
Treasury.burnFrom()(requires user approval of the adapter) - Destination chain: Mints tokens via
Treasury.bridgeMint()(requiresBRIDGE_ROLE) - Routes zero-address recipients to
0xdeadto prevent token loss
- Deploy
TreasuryOFTAdapteron each chain - Grant
BRIDGE_ROLEto the adapter:treasury.addBridge(adapterAddress) - Configure LayerZero peers:
adapter.setPeer(dstEid, peerAddress)
Compliance Controls
Whitelist
Whitelist enforcement applies only to primary issuance minting (mint()). Managed by WHITELISTER_ROLE:
mapping(address => bool) public whitelisted
Lifecycle:
- Institution completes KYC/KYB onboarding
- Compliance team adds the institution’s address to the whitelist
- Address can now receive primary issuance mints
- If needed, address is removed from the whitelist during offboarding
Blacklist
Blacklisted addresses cannot send or receive tokens in any context (transfers, mints, burns). Managed byBLACKLISTER_ROLE:
mapping(address => bool) public blacklisted
Batch operations enable efficient compliance actions across multiple addresses in a single transaction.
Administrative Functions
Force Burn
super._update() directly.
Use cases: Regulatory compliance (e.g., court orders), security incident response, recovery from compromised addresses.
Events: Emits ForcedBurn(operator, from, amount).
Force Transfer
ForcedTransfer(operator, from, to, amount).
Pause / Unpause
forceBurn, forceTransfer) remain operational when the contract is paused.
Yield-Bearing Integration (Treasury Delegate)
When integrated with MultiliquidSwap, the Liquid Treasury token becomes a yield-bearing asset through the Treasury Delegate contract. The delegate manages daily interest rate accrual, a credit-based redemption system, and swap operations.Overview
The Treasury Delegate extends the standard Multiliquid delegate model with yield mechanics:- Users deposit RWAs or stablecoins via MultiliquidSwap and receive $TSY tokens
- The delegate tracks credits (deposit entitlements) separately from token balances
- An off-chain worker posts daily interest rates sourced from the 3-Month US T-Bill Oracle
- Credits accrue yield over time via a compounding multiplier
- When users redeem, they receive their principal plus accumulated yield
Token/Credit Separation
$TSY tokens (ERC-20) and credits are independent:- Tokens can be freely transferred on the open market
- Credits track a user’s yield entitlement and are non-transferable
- Secondary market buyers receive tokens but no credits (no yield benefit until depositing via MultiliquidSwap)
- Redemption requires sufficient credits to prevent negative backing
Daily Rate System
Posting Rates An off-chain worker posts daily interest rates sourced from the 3-Month US T-Bill Oracle :dayNumber: The day number (block.timestamp / 1 days)grossRate: The APY before management fee (WAD-scaled, e.g., 4.5% =4.5e16)- The management fee is subtracted on-chain; the net APY is stored
- The net APY is converted to a per-day compounding rate
firstRateDay and lastRatePostingDay). The operator cannot advance the rate posting frontier.
Management Fee
5e15) subtracted from the gross rate at posting time. Only the LP admin can update it.
Withheld Credits
New deposits enter a withheld credits queue before becoming full credits. These withheld credits become full credits after 24 hours of yield-generation. Withheld credits are selected first when any withdrawals are being made. If they have not reached the 24 hour maturity period upon withdrawal, the credits have yield generated withheld (if any). This prevents timing exploits of the underlying RWA NAVs. Each withheld credit entry tracks:
Queue operations:
- Additions: New deposits are pushed to the back of the deque
- Reductions (withdrawals): Consumed from the back (LIFO — most recent deposits first, which have accrued the least yield)
- Merges: Released from the front (FIFO — oldest deposits mature first) when 24-hour hold period expires
Interest Accrual
Interest accrual is permissionless — anyone can trigger it for any user:type(uint256).max for uncapped daily accrual or to attempt to merge every currently eligible record. Main credits are accrued before eligible withheld-credit records are merged. dailyAccrualComplete reports whether all currently processable daily rates have been applied, while creditsFullyMerged reports whether no currently eligible withheld-credit record remains.
Interest accrual is called daily after rate posting by an off-chain worker to make sure all accounts are up to date.
Yield multiplier: Each user’s effective redeemable value is credits * yieldMultiplier / WAD. The multiplier starts at 1e18 (1.0) and compounds daily.
View Functions
Withheld credits are always valued at 1:1 in view functions (no yield applied). Only main credits receive the yield multiplier. For stablecoin withdrawals, a partial-day yield is applied using the last posted rate to account for intra-day accrual.
Access Control
Treasury Token Roles
Treasury Delegate Roles
Events
Treasury Token Events
Treasury Delegate Events
Custom Errors
Treasury Token Errors
Treasury Delegate Errors
Technical Specifications
Next: Integration Guide
Learn how to integrate with the Multiliquid Protocol