This report, by Eric Meng, chaals nevile and the BSSC Audit Adoption WG describes an assessment of the token SFM deployed on the BNB Smart Chain 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: | SafeMoon V2 |
| Symbol: | SFM | |
| Network: | BNB Smart Chain | |
| Deployment Address(es): | ||
| Evaluator | Name: | Eric Meng, chaals nevile and the BSSC Audit Adoption WG |
| 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 Token does not meet the requirements, with extensive failures across all domains of the specification. In 2023 the Token Contract was subject to a critical security issue exploited for a market value of approximately $9million USD, and Token Project executives were charged with fraud in 2023. | |
| Title | Status | Comments / evidence |
|---|---|---|
| Token Allocation | Fails |
Complete documentation was not provided. The US SEC alleges that insiders held large undocumented allocations. |
| Is it native, bridged, wrapped? | Passes - Correctly Implemented |
|
| Token Rebasing | Fails |
SFM is a reflecting token, with fees from transfers directed in part to an account that transferred value to the Token porject in swapped BNB Tokens, effectively rebasing the Token. This was not documented by the Token Project (and is part of the basis for the SEC charges against principal Token Project executives) |
| Trading History | Passes - Correctly Implemented |
Scanners such as Dexscreener provides market data |
| Price Discovery Mechanism | Passes - Correctly Implemented |
Price is set by the SFM/WBNB constant-product AMM pool on SafeMoon Swap |
| Stablecoin Backing | Not Applicable (passes) |
not a stablecoin |
| Protect Backing Assets from Issuer Insolvency | Not Applicable (passes) |
not a stablecoin |
| Identify Parties Controlling Critical Actions | Fails |
Parties controlling critical actions are not identified by the Token Project |
| Document Governance | Fails |
Processes controlling governance decisions are not identified by the Token Project |
| Identify Governance participants | Fails |
Parties controlling critical actions are not identified by the Token Project. According to the SEC filings, this was deliberate in order to enable such parties to commit fraud against investors. |
| Pass Code Audit | Fails |
V1 of the contract was audited by CertiK, but did not pass the audit as they found major security issues. |
| Audit Code to a Standard | Justified Exception (passes) |
There was no clear equivalent available at the time and the V1 audit represented a reasonable practice. |
| Publish Code Audit Report or Attestation | Not Tested |
|
| Limit Privileged Roles | Fails |
The owner holds broad, uncapped powers including setting fees, excluding addresses from fee and reward, and setting the maximum transaction amount |
| Decentralize Privileged Roles | Fails |
Privileged control rests with a single owner key. No multisig or timelock is documented. |
| Document Privileged Roles | Fails |
Owner-only functions exist on-chain but the issuer publishes no documentation enumerating them. |
| Secure Privileged Roles | Incomplete Test (unknown) |
No evidence of multisig or timelock protection. The March 2023 upgrade pushed a critical bug through a privileged key, indicating inadequate change control. |
| Vulnerability Disclosure Procedure | Fails |
No vulnerability disclosure procedure or security contact is published. |
| Bug Bounty program | Fails |
No bug bounty or similar incentive program |
| No Transfer or Method Hooks | Fails |
The Token includes a reflection mechanism. However rather than justified exception, the SEC case demonstrated this was explicitly included to defraud investors. |
| Document Transaction Limits | Fails |
An owner-set maximum transaction amount exists but is not documented for holders |
| Define Transaction Size Limits | Fails |
The maximum transaction limit is owner-adjustable with no fixed floor, allowing the owner to constrict transfers |
| Avoid Transfer Fees | Fails |
Every transfer incurs an approximately 10% fee split between holder reflection and added liquidity. However rather than justified exception, the SEC case demonstrated this was explicitly included to defraud investors. |
| Fix Transfer Fees | Fails |
Fees are not fixed. Owner setters setTaxFeePercent and setLiquidityFeePercent adjust them. |
| Restrict Transfers from Blocked or Frozen Accounts | Passes - Correctly Implemented |
Transfers from blocked accounts revert |
| Document Whether Blocked Accounts Can Receive Transfers | Not Tested |
Project documentation is no longer available |
| Make Confidential Transfers Auditable | Not Applicable (passes) |
There is no confidential transfer mechanism |
| ERC: Implement ERC Token Standards | Fails |
Transfer function does not transfer the declared value, violating the statement "Transfers _value amount of tokens to address _to" in the ERC-20 specification. |
| ERC: Document ERC Implementation Upgradability | Fails |
The upgradability is not documented. |
| ERC: Balance Changes Create Transfer Events | Partial / Incomplete (fails) |
Transfers emit transfer events for the primary transfer, but not for the transfers created through reflection. |
| ERC: Mint and Burn as per ERC-5679 | Not Tested |
|
| ERC: No Fallback Function | Not Tested |
|
| ERC: Revert Blocked Transfers | Passes - Correctly Implemented |
verified in source |
| Solana: SPL or 2022 Program Tokens | Not Applicable (passes) |
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.