This report, by Eric Meng collaborating with the BSSC Audit Adoption WG, describes an assessment of the token WBTC 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: | Wrapped BitCoin |
| Symbol: | WBTC | |
| Network: | Ethereum | |
| Deployment Address(es): | ||
| Evaluator | Name: | Eric Meng with the BSSC AuditAdoption 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 is an incomplete evaluation, as some requirements could not be tested without the participation of the Token Project. The Token fails requirements for a Responsible disclosure procedure and an incentive for making those disclosures (such as a Bug Bounty). The assessment was performed independently, and input from BitGo/BIT (prinicipal Token Project participants) was not sought. There are therefore two requirements that could not be completely assessed: The protection for backing assets against loss of legal control, and the security posture protecting Privileged Roles. | |
| title | Status | Comments |
|---|---|---|
| Token Allocation | Passes - Correctly Implemented |
No premine or team allocation. Supply is minted only against 1:1 BTC deposits and burned on redemption, so circulating supply equals custodied reserves |
| Is it native, bridged, wrapped? | Passes - Correctly Implemented |
WBTC is a custodial wrapped asset, not a native asset or trustless bridge output. BTC is held by a centralized custodian and WBTC is minted on Ethereum by approved merchants. Provenance and trust model are documented. |
| Token Rebasing | Passes - Correctly Implemented |
No rebasing. Balances are static ERC-20 balances at 8 decimals; supply changes only via explicit mint and burn. |
| Trading History | Passes - Correctly Implemented |
Continuous public trading and on-chain history since the 2019 launch across major CEX and DEX venues. |
| Price Discovery Mechanism | Passes - Correctly Implemented |
Deep secondary liquidity on CEX and DEX. Price tracks BTC through arbitrage against the merchant mint and burn redemption path. |
| Stablecoin Backing | Not Applicable (passes) |
WBTC tracks BTC, not a fiat peg, so stablecoin backing requirements do not apply. |
| Protect Backing Assets from Issuer Insolvency | Incomplete Test (unknown) |
BTC reserves are held in multi-sig cold storage under a regulated custodian with on-chain proof of reserves, and merchant redemption is 1:1. Bankruptcy-remoteness and legal segregation of reserves from the custodian's estate are not publicly attested, which is the central custodian-trust gap. Needs issuer confirmation. |
| Identify Parties Controlling Critical Actions | Passes - Correctly Implemented |
Critical actions are publicly attributable: the custodian (BitGo, now under a BiT Global joint venture) holds BTC and controls the owner key path, approved merchants execute mint and burn, and the WBTC DAO multisig governs role changes. |
| Document Governance | Passes - Correctly Implemented |
The WBTC DAO governs addition and removal of merchants and custodians via multisig. The governance model is publicly documented |
| Identify Governance participants | Passes - Correctly Implemented |
DAO members and merchants are named publicly, including the custodian and institutional merchant set. |
| Pass Code Audit | Passes - Correctly Implemented |
A public ChainSecurity audit covers the WBTC Ethereum contracts, including merchant and custodian management and the token mint, transfer, and burn paths. Two issues were raised (a mint and burn pause gap and an abi.encodePacked hash-collision risk) and both were addressed; ChainSecurity records no remaining security issues in the audited version. ChainSecurity audit ยท audit docs |
| Audit Code to a Standard | Justified Exception (passes) |
In the opinion of the assessor(s), the audit represented standard practice in 2018 when performed. |
| Publish Code Audit Report or Attestation | Passes - Correctly Implemented |
The ChainSecurity audit report is published as a downloadable PDF on the auditor's site and is linked from the WBTC documentation |
| Limit Privileged Roles | Passes - Correctly Implemented |
Privileged actions are scoped: mint and burn are gated to custodian-controlled member roles via the controller, and pause is limited to the owner. No arbitrary admin transfer of user balances exists. |
| Decentralize Privileged Roles | Passes - Correctly Implemented |
The owner key is a multisig under WBTC DAO governance rather than a single EOA. Custody itself remains centralized in the custodian joint venture |
| Document Privileged Roles | Passes - Correctly Implemented |
Owner, controller, members (merchants), and custodian roles and their powers are publicly documented and reflected in the verified contract. |
| Secure Privileged Roles | Incomplete Test (unknown) |
The owner key is an on-chain multisig under WBTC DAO governance, but no public SOC 2 or attestation covers the current BitGo and BiT Global custody arrangement, so key-custody controls are not verifiable from public information. Needs issuer confirmation. |
| Vulnerability Disclosure Procedure | Fails |
No public vulnerability disclosure policy or security contact specific to the WBTC token was located. |
| Bug Bounty program | Fails |
No public bug bounty program for the WBTC contracts was located |
| No Transfer or Method Hooks | Passes - Correctly Implemented |
Classic ERC-20 with no ERC-777 style transfer callbacks or method hooks. Transfers carry only a global pause guard, not per-transfer external calls. |
| Document Transaction Limits | Passes - Correctly Implemented |
The immutable contract enforces no on-chain per-transfer limits, and the absence is publicly verifiable from the source. Merchant mint and burn KYC thresholds are off-chain and do not constrain token transfers |
| Define Transaction Size Limits | Not Applicable (passes) |
No transaction size limit mechanism exists in the immutable contract, so there is nothing to define |
| Avoid Transfer Fees | Passes - Correctly Implemented |
No transfer fee is applied. The transferred amount equals the received amount. |
| Fix Transfer Fees | Not Applicable (passes) |
No transfer fee is applied. The transferred amount equals the received amount. |
| Restrict Transfers from Blocked or Frozen Accounts | Not Applicable (passes) |
The contract has no per-account blacklist or freeze. It exposes only a global owner-controlled pause that halts all transfers rather than targeting specific accounts. |
| Document Whether Blocked Accounts Can Receive Transfers | Not Applicable (passes) |
The contract has no per-account blacklist or freeze. It exposes only a global owner-controlled pause that halts all transfers rather than targeting specific accounts. |
| Make Confidential Transfers Auditable | Not Applicable (passes) |
WBTC has no confidential or shielded transfer feature; all transfers are transparent ERC-20 events. |
| ERC: Implement ERC Token Standards | Passes - Correctly Implemented |
Implements the full ERC-20 interface (transfer, transferFrom, approve, allowance, balanceOf, totalSupply) at 8 decimals. |
| ERC: Document ERC Implementation Upgradability | Not Applicable (passes) |
Immutable Contract |
| ERC: Balance Changes Create Transfer Events | Passes - Correctly Implemented |
Mint emits Transfer from the zero address and burn emits Transfer to the zero address, alongside Mint and Burn events, so every balance change produces a Transfer event. |
| ERC: Mint and Burn as per ERC-5679 | Passes - Correctly Implemented |
The 2018 contract predates ERC-5679 and does not implement its IERC5679Ext20 interface. It uses bespoke mint and burn functions. Standard Transfer events are emitted |
| ERC: No Fallback Function | Passes - Correctly Implemented |
No fallback or receive function |
| ERC: Revert Blocked Transfers | Not Applicable (passes) |
No per-account blocking exists. The global pause reverts all transfers when active, but there is no account-level block to revert. |
| 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.