This report, by Eric Meng collaborating with the BSSC Audit Adoption WG, describes an assessment of the token USDY deployed on the Ethereum network against the BSSC Token Integration Standard version 2. It is published as an example assessment of a well-known token against the specification.
| BSSC Token Integration Standard version 2 | ||
|---|---|---|
| Specification URL: https://specs.blockchainssc.org/tis/v2.html | ||
| Token being evaluated | Name: | Ondo US Dollar Yield |
| Symbol: | USDY | |
| Network: | Ethereum | |
| Deployment Address(es): | ||
| Evaluator | Name: | Eric Meng and BSSC Audit Adoption WG |
| Contact Details: | ||
| Evaluation | Date completed: | 2026-11-08 |
| Outcome / comments: | This report was compiled as an illustative example to provide guidance on developing an evaluation report, and may contain material errors. This evaluation was performed independently based on publicly available documentation, and input from the Token Project was not sought. There are a small number of requirements that cound not be completely verified in this way, related to governance and security measures applied for managing privileged roles. There were no requirements assessed that the token fails. | |
| title | Status | Comments / evidence |
|---|---|---|
| Token Allocation | Passes - Correctly Implemented |
USDY is minted on subscription against collateral, not pre-allocated to insiders. Underlying assets are roughly $2.19B at about 105.8% collateralization; allocation and reserves are published daily |
| Is it native, bridged, wrapped? | Passes - Correctly Implemented |
Native issuance on Ethereum. Ondo separately bridges USDY to other networks via the Ondo Token Bridge; the Ethereum contract in scope is the native mint |
| Token Rebasing | Passes - Correctly Implemented |
USDY is non-rebasing. Yield accumulates into an appreciating price; supply does not rebase |
| Trading History | Passes - Correctly Implemented |
Live since 2023 with multi-year price and transfer history and secondary integrations across DeFi. On-chain and market history are public |
| Price Discovery Mechanism | Passes - Correctly Implemented |
Price accrues from the yield on short-term US Treasuries and bank deposits. On-chain price is served by USDYOracleWrapper, and Ondo publishes prices and shares-multiplier history via its public API |
| Stablecoin Backing | Not Applicable (passes) |
USDY is not a stablecoin. |
| Protect Backing Assets from Issuer Insolvency | Passes - Correctly Implemented |
Issued by Ondo Global Markets (BVI) Limited, designed to be bankruptcy-remote. Ankura Trust Company acts as Verification Agent and Collateral Agent; holders have a security interest in the backing assets. Reserves are held off the issuer's operating balance sheet with daily third-party attestations, so redemption claims survive as secured interests rather than unsecured liabilities. |
| Identify Parties Controlling Critical Actions | Passes - Correctly Implemented |
Critical actions (mint, redeem, allowlist/blocklist administration, contract upgrade) are controlled by Ondo as issuer and manager. Ankura Trust Company controls collateral verification and enforcement. Custody sits with named custodians. Parties are named publicly. |
| Document Governance | Passes - Correctly Implemented |
USDY is centrally administered by the issuer with no on-chain token governance. The control model (issuer operations plus Collateral Agent oversight) is documented in Ondo docs and legal terms |
| Identify Governance participants | Passes - Correctly Implemented |
Participants are identified: Ondo Global Markets (BVI) Limited (issuer/manager), Ankura Trust Company (Verification and Collateral Agent), and named custodians. No anonymous controlling parties. |
| Pass Code Audit | Passes - Correctly Implemented |
Ondo token contracts have multiple public smart-contract audits: Spearbit (Mar 2025), Halborn (Feb 2025), Cyfrin (Apr 2024), Zokyo (Aug 2023), Nethermind (Apr 2023), and several Code4rena contests. Ondo audits page |
| Audit Code to a Standard | Passes - Correctly Implemented |
In te opinion of the assessor, the multiple audits performed are equivalent to meeting the requirements of SCS |
| Publish Code Audit Report or Attestation | Passes - Correctly Implemented |
Full audit reports are published on the Ondo docs audits page and via Cantina/Code4rena, not merely summarized |
| Limit Privileged Roles | Passes - Correctly Implemented |
Access is role-separated in the verified implementation via distinct minter, pauser, blocklist, allowlist, and sanctions-list clients rather than a single omnipotent owner. |
| Decentralize Privileged Roles | Incomplete Test (unknown) |
Whether a single Ondo operator can unilaterally exercise the admin roles is not publicly confirmed; the Halborn audit recommends multisig for administrative functions, which suggests it may not yet be in place. |
| Document Privileged Roles | Passes - Correctly Implemented |
Privileged roles are enumerated in the verified source and described across the published audit reports (mint/burn, pause, blocklist, allowlist, sanctions, upgrade). |
| Secure Privileged Roles | Incomplete Test (unknown) |
The trust-and-security page names asset partners and Ankura Trust for collateral oversight, which is asset custody rather than privileged-key security. No public SOC 2, ISO, multisig, or key-custody attestation for admin role holders is available |
| Vulnerability Disclosure Procedure | Passes - Correctly Implemented |
A responsible-disclosure path is published via the Ondo Immunefi program with a defined submission process and severity handling |
| Bug Bounty program | Passes - Correctly Implemented |
Public Immunefi program live since Mar 2023, rewards up to $1,000,000 for critical smart-contract findings, with USDY in scope. bug bounty |
| No Transfer or Method Hooks | Justified Exception (passes) |
USDY enforces transfer hooks by design. Each transfer runs allowlist, blocklist, and Chainalysis sanctions-list checks before executing. |
| Document Transaction Limits | Passes - Correctly Implemented |
Subscription and redemption limits and minimums are documented, and per-user trading and session limits are exposed via the Ondo API. New purchasers are subject to KYC/allowlisting and a settlement period before USDY is delivered and transferable |
| Define Transaction Size Limits | Passes - Correctly Implemented |
Minimums are defined ($5,000 mint/redeem on alternative networks; $100,000+ for bank-wire subscription) and per-asset trading and session limits are enforced and queryable via API |
| Avoid Transfer Fees | Passes - Correctly Implemented |
USDY charges no on-chain transfer fee. Balances do not shrink on transfer |
| Fix Transfer Fees | Not Applicable (passes) |
No transfer fees exist; so this requirement does not apply |
| Restrict Transfers from Blocked or Frozen Accounts | Passes - Correctly Implemented |
Blocking exists via BlocklistClient and Chainalysis SanctionsListClient. Transfers from blocklisted or sanctioned accounts are rejected on-chain. |
| Document Whether Blocked Accounts Can Receive Transfers | Passes - Correctly Implemented |
The access model is documented: only KYC-onboarded, allowlisted non-US persons can send or receive USDY, and blocklisted or sanctioned addresses can do neither. Non-allowlisted recipients cannot receive transfers |
| Make Confidential Transfers Auditable | Not Applicable (passes) |
USDY is a transparent ERC-20 with no confidential-transfer mechanism |
| ERC: Implement ERC Token Standards | Passes - Correctly Implemented |
USDY is a compliant ERC-20. Transfer restriction is layered on top via allowlist/blocklist/sanctions checks (ERC-1404-style restricted-transfer behavior), while standard ERC-20 balance, allowance, and event semantics are preserved |
| ERC: Document ERC Implementation Upgradability | Incomplete Test (unknown) |
No public Ondo documentation identifies the proxy admin, upgrade process, upgrade governance, or a timelock for the USDY proxy; the docs describe token mechanics only. |
| ERC: Balance Changes Create Transfer Events | Passes - Correctly Implemented |
Balance changes emit standard ERC-20 Transfer events, including mint (from the zero address) and burn (to the zero address), enabling accurate off-chain indexing. |
| ERC: Mint and Burn as per ERC-5679 | Passes - Correctly Implemented |
Mint and burn emit Transfer events to and from the zero address, consistent with ERC-5679 intent for observable supply changes |
| ERC: No Fallback Function | Passes - Correctly Implemented |
The EIP-1967 proxy exposes a fallback that delegatecalls the implementation. This is inherent to the upgradeable-proxy pattern but there isn’t any implemented fallback |
| ERC: Revert Blocked Transfers | Passes - Correctly Implemented |
Transfers involving non-allowlisted, blocklisted, or sanctioned addresses revert rather than silently failing, preserving correct integrator accounting. |
| Solana: SPL or 2022 Program Tokens | Not Applicable (passes) |
This is not a Solana Token |
The BSSC Token Integration Standard version 2 ("the Standard") establishes technical, governance, and operational requirements intended to help identify and reduce known security risks associated with digital asset integration. BSSC makes the Standard and related assessment framework (the "Assessment Framework") available for use by third parties, including independent evaluators and those conducting self-assessments. Reports prepared using these materials may provide useful information about conformity with the requirements evaluated, but the findings and conclusions are those of the report's preparer, not BSSC.
Conformance to the Standard's requirements can provide meaningful information about a Token's integration-related security practices, but does not guarantee that the Token is secure, free from vulnerabilities, or suitable for any particular purpose. An assessment against the Standard is not necessarily a comprehensive security audit. Conversely, failure to satisfy a requirement does not necessarily establish an exploitable vulnerability. Findings should be considered together with their accompanying explanations, and requirements that have not been evaluated or verified should not be treated as satisfied.
Use of the Standard or Assessment Framework does not, by itself, establish any employment, agency, accreditation, certification, or other relationship between BSSC and the person preparing a report. Unless BSSC expressly states otherwise in writing, BSSC has not selected, supervised, or evaluated the qualifications of that person, nor has it reviewed or verified the report's methods, evidence, findings, or conclusions. BSSC does not adopt, warrant, or stand behind the evaluator, the report, or the Token evaluated. Publication of an illustrative report by BSSC does not itself constitute approval or endorsement. BSSC does not currently operate a certification program for this Standard, and use of these materials confers no BSSC certification or certification mark. Nor does a report constitute a listing or integration decision by any exchange or other organization merely because it uses the Standard.
Neither the Standard nor the Assessment Framework provides financial, investment, or legal advice. No report prepared using these materials should be treated as providing such advice, establishing regulatory compliance, or recommending the purchase, sale, holding, listing, or integration of a Token merely because it was prepared using these materials. BSSC makes no representation concerning any Token's current or future value, investment merits, regulatory status, or performance
Reports prepared using the Assessment Framework may rely on information supplied by Token issuers or other third parties that BSSC has not independently verified, including statements about reserves, asset backing, issuer solvency, or legal rights. Findings are limited to the information reviewed and procedures performed and may become outdated as the Token, its underlying contracts, governance, or operating environment changes. Readers should consider the report preparer's methodology, qualifications, and stated limitations.
Readers should also review BSSC's Disclaimer of Warranty and Liability accompanying the Standard.