protocol identification
two sourcesCircle USYC is Circle’s tokenized money market fund product. The official website is circle.com/usyc, and Circle’s developer docs host the smart-contract reference page for USYC. The protocol is not verifiable on-chain in this run, so contract verification status is limited to explorer/issuer documentation rather than independent chain inspection.
Circle states USYC is issued by Circle International Bermuda Limited and represents an interest in a Cayman Islands mutual fund. Public sources place inception/launch around 2023-05-01. The protocol is deployed on Ethereum and BSC per Circle’s contract page; other public sources also mention additional chains, but for this request only Ethereum and BSC are relevant.
USYC has no native governance token disclosed in the sources reviewed; the product itself is the tokenized fund share. Main contract addresses reported by Circle are: Ethereum USYC 0x136471a34f6ef19fE571EFFC1CA711fdb8E49f2b and BSC USYC 0x8D0fA28f221eB5735BC71d3a0Da67EE5bC821311, with associated teller/entitlements contracts on each chain. These addresses are cross-checked by Circle’s developer documentation and secondary aggregator pages that repeat the same addresses, but explorer verification status is Not verifiable as of 2026-09-04 in this run.
On lineage, USYC is not a clean standalone fork in the usual DeFi sense; it is a tokenized-money-market product originally associated with Hashnote and later operated under Circle after Circle’s acquisition of Hashnote. Available sources do not establish a specific open-source upstream protocol fork, so the safest identification is no independently verifiable fork lineage. Changes vs. upstream are therefore Not verifiable as of 2026-09-04.
Audit status is also Not verifiable as of 2026-09-04 from the sources gathered here. For malicious-modification history in similar forks, the only defensible statement is that forked tokenized-fund deployments are common targets for address confusion and clone/phishing risk, but a USYC-specific malicious-modification history is Not verifiable as of 2026-09-04.