This report, by Eric Meng collaborating with the BSSC AAWG, describes an assessment of the token GUSD deployed on the Ethereum main net 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: | Gemini Dollar |
| Symbol: | GUSD | |
| Network: | Ethereum main net | |
| Deployment Address(es): | ||
| Evaluator | Name: | Eric Meng, BSSC AAWG |
| Contact Details: | ||
| Evaluation | Date completed: | 2026-11-07 |
| Outcome / comments: |
This report was compiled as an illustative example to provide guidance on developing an evaluation report, and may contain material errors. The assessors believe the Token passes all requirements. Note this report was compiled independently without the participation of the Gemini Trust Company (the principal Token Project participants) being sought | |
| title | Status | Comments |
|---|---|---|
| Token Allocation | Passes - Correctly Implemented |
No fixed or pre-mined allocation. Mints and burns are managed by Gemini Trust Company against USD deposits as a 1:1 peg |
| Is it native, bridged, wrapped? | Passes - Correctly Implemented |
Native Solana 2022 Token, and the Token Project documents deployments on other chains. |
| Token Rebasing | Not Applicable (passes) |
The token does not rebase |
| Trading History | Passes - Correctly Implemented |
Available on standard scanners where the token is deployed. |
| Price Discovery Mechanism | Passes - Correctly Implemented |
USD-pegged stablecoin. Price is held near 1.00 by Gemini 1:1 mint and redemption; price discovery on centralized and decentralized markets |
| Stablecoin Backing | Passes - Correctly Implemented |
Fully backed by cash and cash equivalents held in US bank deposits, money market funds, and US Treasury bills; monthly BPM LLP attestation on a randomly selected business day. reserve attestations |
| Protect Backing Assets from Issuer Insolvency | Passes - Correctly Implemented |
Reserves held at US depository institutions and government money market funds under NYDFS reserve requirements. On-chain bankruptcy-remoteness for token holders is not contractually guaranteed. |
| Identify Parties Controlling Critical Actions | Passes - Correctly Implemented |
Gemini Trust Company controls the custodian (print/burn and print-limit), imp (implementation upgrade), and pauser roles. |
| Document Governance | Passes - Correctly Implemented |
Centralized issuer governance documented in the GUSD whitepaper and subject to NYDFS supervision. |
| Identify Governance participants | Passes - Correctly Implemented |
The sole governing entity is Gemini Trust Company. Individual key-holder identities and the multisig signer set are not public. |
| Pass Code Audit | Passes - Correctly Implemented |
GUSD smart contracts were audited by Trail of Bits; a summary of the security assessment is published by Trail of Bits, and asserts that all issues discovered were resolved. |
| Audit Code to a Standard | Justified Exception (passes) |
In the opinion of the assessors, the 2018 Trail of Bits audit represented the standard practice at the time. |
| Publish Code Audit Report or Attestation | Justified Exception (passes) |
The audit is published by the auditor, not directly linked from the Token project. In the opinion of the assessor, this meets the requirement in practice. |
| Limit Privileged Roles | Passes - Correctly Implemented |
Privileged actions are confined to custodian, imp, and pauser roles; custodian minting is rate-limited by an on-chain print limit. |
| Decentralize Privileged Roles | Passes - Correctly Implemented |
Custodian keys are held offline in a multi-signature scheme under Gemini's NYDFS-regulated, SOC 2 controls, so no single employee can unilaterally sign |
| Document Privileged Roles | Passes - Correctly Implemented |
Custodian, imp, pauser, and print-limit controls are documented in the whitepaper |
| Secure Privileged Roles | Passes - Correctly Implemented |
Custodian keys are held offline in a multi-signature scheme; the issuer maintains SOC 2 controls and operates under NYDFS supervision |
| Vulnerability Disclosure Procedure | Passes - Correctly Implemented |
Gemini operates a coordinated vulnerability disclosure channel via Bugcrowd and a security contact, following RFC9116 |
| Bug Bounty program | Passes - Correctly Implemented |
Gemini runs a Bug Bounty program on BugCrowd. |
| No Transfer or Method Hooks | Passes - Correctly Implemented |
Standard ERC-20 transfer path with no pre- or post-transfer callback hooks. |
| Document Transaction Limits | Passes - Correctly Implemented |
The on-chain print limit that caps custodian minting is documented; no per-user transfer caps exist |
| Define Transaction Size Limits | Passes - Correctly Implemented |
Minting is bounded by the print-limit ceiling; ordinary transfers are unconstrained by design. |
| Avoid Transfer Fees | Passes - Correctly Implemented |
No transfer fee is charged on GUSD transfers |
| Fix Transfer Fees | Not Applicable (passes) |
No transfer fees exist |
| Restrict Transfers from Blocked or Frozen Accounts | Not Applicable (passes) |
There is a global pause but no per-account blocking mechanism |
| Document Whether Blocked Accounts Can Receive Transfers | Not Applicable (passes) |
There is a global pause but no per-account blocking mechanism |
| Make Confidential Transfers Auditable | Not Applicable (passes) |
Transparent ERC-20 contract with no confidential transfer feature |
| ERC: Implement ERC Token Standards | Passes - Correctly Implemented |
Implements the ERC-20 standard |
| ERC: Document ERC Implementation Upgradability | Passes - Correctly Implemented |
Upgradeable via the ERC20Proxy design separating ERC20Impl and ERC20Store; the upgrade model is documented in the whitepaper |
| ERC: Balance Changes Create Transfer Events | Passes - Correctly Implemented |
Transfer events are emitted on transfer, mint (print), and burn. |
| ERC: Mint and Burn as per ERC-5679 | Passes - Correctly Implemented |
Print emits Transfer from the zero address and burn emits Transfer to the zero address, consistent with ERC-5679 supply-event semantics; the 2018 contract predates the formal interface. |
| ERC: No Fallback Function | Passes - Correctly Implemented |
Forwarding proxy design with no payable fallback or delegatecall catch-all. |
| ERC: Revert Blocked Transfers | Not Applicable (passes) |
There is a global pause but no per-account blocking mechanism |
| Solana: SPL or 2022 Program Tokens | Not Applicable (passes) |
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.