USYC’s “tokenomics” are fund economics, wrapped in a token
USYC is not trying to be a protocol token with emissions, burns, or governance theater. It is a tokenized share of a real-world short-duration yield fund, designed to behave like institutional cash collateral that can move onchain. Circle and Hashnote describe USYC as the onchain representation of Hashnote International Short Duration Yield Fund Ltd. (SDYF).
The underlying fund invests in short-term US Treasury Bills and repo and reverse-repo activity. Circle’s developer docs frame the yield driver more narrowly as reverse repurchase agreements backed by US government securities, with returns tied to the overnight Fed funds regime. For a close analogue, compare it with our BUIDL tokenomics review.
That structure matters for how you should model it. USYC has no “security budget” of its own. It consumes the security budget of the chains it sits on, then adds one more trust layer above the chain: a permissioned issuer and a regulated fund complex. Circle notes USYC is issued by Circle International Bermuda Limited (CIBL), regulated by the Bermuda Monetary Authority (BMA), and represents an interest in a Cayman Islands mutual fund licensed by the Cayman Islands Monetary Authority (CIMA).
Access is explicitly restricted. Hashnote’s onboarding docs state USYC is only accessible to institutions outside the United States, subject to eligibility restrictions and a US$100,000 minimum investment. The USYC key facts section also lists the $100,000 minimum and repeats that shares and USYC are offered only to non-US persons.
From a token design perspective, that permissioning is the point. USYC is built to be a yield-bearing collateral leg that can settle into and out of USDC with smart contract rails, including use as margin collateral on integrated venues. If you are integrating USYC into lending, margin, or liquidation systems, you are integrating a collateral asset whose core constraints are offchain and administrative, even if the settlement path is onchain. For a contrast with a fiat-backed stablecoin that targets price stability rather than price-up yield, see our Ripple USD review.
Supply: elastic shares minted against USDC, burned on redemption
USYC’s supply is not pre-mined, allocated, or emitted. It expands and contracts with subscriptions and redemptions, like shares in a fund. Circle’s docs describe “onchain settlement” as entering or exiting USYC by exchanging USDC, with subscriptions and redemptions available 24/7/365 and settling atomically in real time (T+0).
Hashnote’s subscription and redemption docs are explicit about the action onchain. Subscribing mints USYC. Redeeming burns USYC and returns USDC. Their product structuring docs add the accounting bridge: tokens represent fund shares, token holders must be onboarded and KYC’d, and the fund administrator updates the SDYF share registry to reflect token movements.
Mechanically, the mint amount is price-referenced. Hashnote states the USYC received equals the deposit amount divided by the current USYC price. That is the cleanest mental model: USYC is “shares,” USDC is the subscription currency, and the conversion rate floats with NAV.
There is no emission schedule to analyze, and no burn policy meant to create reflexive value. That is good for sustainability. It also means USYC cannot subsidize its own security or liquidity the way a native protocol token might. Any onchain liquidity you see is either (1) natural demand from eligible holders, (2) venue-driven market making, or (3) issuer-provisioned facilities. For the broader framework behind these assessments, see our token design principles.
Hashnote also describes “Private Liquidity Teller” (PLT) arrangements that can provide up to 100% instant liquidity into USDC at all times, with additional fees. This is important. It is not “liquidity mining.” It is an operational promise backed by balance sheet and treasury management choices.
Yield and pricing: daily NAV marks, onchain oracle, price-up token
USYC accrues yield by pushing value into the token price. Circle’s USYC materials describe “simplified yield” that accrues automatically through a rising token price, with no staking or claiming. Circle’s BNB Chain announcement repeats the same mechanism, calling out yield through token price appreciation.
Hashnote’s USYC price formula is: USYC price = NAV of the prime brokerage account ÷ total USYC supply. Price is reported to an onchain USYC Oracle once per business day after the prime broker reports prior-day activity and after subscriptions, redemptions, and accrued interest are reconciled. Trade activity is described as Monday to Friday, excluding US federal holidays, with results reflected the next morning.
That daily mark is a feature and a constraint. For holders, it is operationally simple. For DeFi-style risk engines, it is a discontinuous oracle that steps once per business day. Liquidation design has to respect that. Intraday market prices can move against an oracle that stays flat until the next report.
Hashnote also documents an “effective subscription price” concept. Redemptions occur at the current USYC price, while subscriptions may occur at either the current price or a forecast next price depending on whether funds arrive before or after a daily cut-off. Their product structuring docs similarly state that after-hours subscriptions are minted at the next business day’s price, calculated in advance based on the current interest rate generated by the fund.
Circle’s USYC page ties a fee lever to this same boundary. It lists an “after hours subscription fee” that varies based on a projected next price. Even without using the exact timestamps, the design intent is clear: avoid cross-subsidizing late-arriving capital that did not participate in that business day’s yield.
From a security-budget-maximalist lens, the “oracle once per business day” detail is the one I would not wave away. It is a coordination point. It is also a composability bottleneck. If USYC is used as systemically important collateral, the oracle update process becomes a soft piece of infrastructure that the onchain world will route around, price around, and sometimes attack around.
Fees and fiscal flows: bps on rails, performance take on yield
USYC’s economic flows are simple and mostly offchain. The yield starts as cash-and-carry yield in repo and T-bills. It becomes fund NAV. NAV becomes token price. Then the manager and administrator take fees.
Hashnote’s standard fees are: 10% of yield as a performance fee, 4 bps subscription fee, and 3 bps redemption fee.
Hashnote clarifies the subscription fee applies when using USDC to subscribe to USYC, and that redemptions are processed into USDC. It also notes tiered fees for private liquidity, routed through commercial arrangements.
USYC is explicitly “fee-based,” not “inflation-based.” That is the opposite of most proof-of-stake security models, where issuance is a core budget line for validators. Here, there is no native validator set. The chain validator set gets paid only through gas fees. That means USYC adoption can support chain security only indirectly, through increased transaction demand and fee burn or fee revenue, depending on the chain’s design.
Two practical implications follow.
First, if USYC stays permissioned and primarily institutional, onchain transaction counts may remain modest. That limits its contribution to fee-driven security budgets. It can still be meaningful on specific venues, especially margin systems, but the demand profile looks spiky and event-driven.
Second, the “real yield” comes from outside crypto. That is the sustainable part. If the onchain environment goes risk-off, the yield engine is still a repo and T-bills book. The weak point is not yield sustainability. It is redemption and control.
Control plane: entitlements, allowlists, sanctions oracle, halts
USYC’s governance is administrative, not tokenized. There is no public onchain governance process described in Circle’s or Hashnote’s technical documentation. What you do have is a very explicit control plane built into the contracts and onboarding path.
Onboarding is a gated pipeline. Hashnote’s high-level process includes: create an account, complete questionnaires, the fund administrator performs KYC and AML, and a wallet screening provider whitelists the wallet address. Their product structuring documentation is direct that tokens represent fund shares and that token holders must be onboarded and KYC’d to own SDYF shares.
The enforcement mechanism onchain is the entitlements and permissions system. Hashnote’s product structuring docs describe entitlements as the gatekeepers to most of the functionality of USYC, with KYC’d wallets receiving roles that entitle them to hold and transfer, and with smart contracts querying the entitlements contract to verify permissions on transfers and receipts.
Sanctions enforcement is built in too. Hashnote documents that the entitlements contract performs OFAC sanctions checks by querying an onchain oracle for sanctioned address matches, and that the oracle is maintained by Chainalysis.
And there is an emergency brake. Hashnote states the entitlements contract can freeze all transactions involving USYC, positioning the allowlist to revert all transactions if suspicious activity occurs, and later restore transfers after resolution.
This is where USYC departs from the “neutral collateral” intuition many DeFi builders have. USYC is programmable collateral, but it is also stoppable collateral. In a pure crypto system, you assume liveness failures come from chain halts, MEV, or congestion. Here, liveness failures can also be policy decisions.
Finally, the rails themselves are standardized around a “Teller” contract interface. Circle’s quickstart shows a Teller contract with deposit and redeem functions for subscriptions and redemptions. Hashnote’s integration guide similarly describes subscriptions and redemptions handled through an audited Teller smart contract.
If you are building liquidation systems, this is the hard edge. The system is “smart contracts all the way down” only until entitlements or redemption liquidity say otherwise.
Risks: where this breaks in production
Dominant risk: redemption and transfer liveness is ultimately governed by an administrative and operational stack, not just chain consensus. For related collateral case studies, see our research notes.
USYC is explicitly designed as a fund share with an onchain twin. The fund share registry is updated by the fund administrator to reflect token movements. Eligibility is KYC and AML gated, with wallets whitelisted as part of onboarding. Transfers depend on entitlements, including OFAC screening supported by a Chainalysis-maintained oracle. And Hashnote documents a system-halt capability that can freeze all USYC transactions.
In other words, USYC’s primary safety property is compliance control. That is what makes it institutionally usable. It is also what makes it brittle as generalized collateral.
The moment you place USYC into a leverage loop, you are depending on two types of liveness. Chain liveness and issuer liveness. Chain liveness is probabilistic and economically defended. Issuer liveness is policy defended. Those are different animals. A proof-of-stake chain can have a declining issuance curve and still defend liveness if fee revenue replaces issuance. A permissioned collateral token can have strong chain security and still fail liveness if entitlements freeze flows, if onboarding status changes, or if redemptions are constrained above an instant-redemption capacity. Circle’s USYC page itself signals this by describing “near-instant” redemptions that can settle in one block time below capacity, while redemptions above that capacity settle T+0 or T+1.
If you are a lending protocol, the risk bearer is not “USYC holders in general.” It is whoever is long USYC as collateral when an unwind is required. That includes borrowers, liquidators, and any backstop liquidity providers. In the worst case, an administrative halt forces liquidations to route through secondary markets only, with a daily stepping oracle and a shrinking set of eligible counterparties. That is exactly how you get gap risk.
Service provider concentration amplifies this. Hashnote publicly lists critical providers, including prime broker Marex, bank Customers Bank, auditor Cohen and Company, fund administrator NAV Consulting, KYC and AML support via NAV Consulting and LMO Consulting, and MPC wallet provider Fireblocks. None of this is inherently bad. It is just not the same as “smart contracts and validators secure everything.” It is a traditional stack with onchain settlement on top.
From a security-budget-maximalist standpoint, the uncomfortable conclusion is that USYC can sit on highly secure chains and still fail as “always-on collateral” during the exact windows when security matters most. Those windows are market stress events, sanctions events, and operational incidents.
Top 3 risks
Administrative freeze and permissioning shock. Trigger: sanctions events, suspicious activity flags, or compliance updates that prompt entitlements changes. Mechanism: entitlements role checks gate transfers and receipts, and the entitlements system can freeze all USYC transactions. Who bears it: leveraged holders using USYC as collateral, liquidators relying on atomic sells, and venues guaranteeing settlement. Measurable indicators: rising revert rates on USYC transfers, allowlist churn, or an observable halt in onchain USYC transfer activity while base chains remain live.
Oracle step risk and liquidation mismatch. Trigger: rapid risk repricing intraday while USYC oracle updates remain on a business-day cadence, or delays in price reporting. Mechanism: USYC price is reported once per business day after reconciliation, and price equals NAV divided by supply. Who bears it: protocols that use the oracle value for collateral factors, liquidators, and market makers warehousing basis risk between “oracle price” and “market-clearing price.” Measurable indicators: widening secondary-market discount or premium to oracle, increased liquidation slippage, or clustering of liquidations immediately after oracle updates.
Liquidity capacity and settlement regime shift. Trigger: redemptions that exceed instant liquidity capacity, or a run where many venues simultaneously demand USDC liquidity. Mechanism: below an instant-redemption capacity, redemptions can settle in one block time, while above capacity they shift to T+0 or T+1. Who bears it: traders using USYC as margin collateral, and any system that assumes redemption is always atomic. Measurable indicators: redemptions settling slower than normal, growing queues or operational messaging about capacity, and persistent secondary-market discounts during periods of heavy redemption demand.
If you are designing integrations, treat USYC like what it is: permissioned, administrator-controlled collateral with real yield and a clear legal wrapper. That combination can be excellent for institutional workflows. It is less forgiving inside permissionless leverage systems.
If you need outside review for a USYC-based collateral system, this is one of the rare cases where tokenomics consulting is mostly risk-engineering: oracle cadence, liquidation design, and administrative-liveness assumptions, not emissions math.
One last historical note that affects operational expectations. Circle announced its acquisition of Hashnote on January 21, 2025, positioning USYC as a core yield-bearing collateral product integrated with USDC. Circle later announced USYC availability on BNB Chain on November 19, 2025. Multi-chain expansion increases address surface area and operational complexity. It does not change the core token economics. It does change the security envelope you are implicitly accepting when you deploy USYC as collateral across venues.
This article is part of our Tokenomics Deep Dive series.
