The Token Integration Standard (TIS) is a set of security requirements for a Token, intended to help decide whether specific Tokens pose known and unacceptable security risks.
The goal of this specification is to provide a set of security requirements for description and use of Tokens such that Tokens which meet these requirements provide a high level of safety assurance for common integration cases.
To reach these requirements we have considered the combination of technical robustness, operational resilience, and economic integrity ensuring the token’s safe functionality, reliable governance, and protection against malicious or unintended exploits, to capture the inherent trade-offs between trust, security, and decentralization, while being flexible enough for diverse Token implementations.
Important: Note Well: It is not possible to provide a formal security guarantee for a Token. Meeting the requirements in this specification does not constitute such a guarantee, it simply identifies that the Token or Token holders are unlikely to be maliciously exploited through a specific set of common and well-known vulnerabilities.
It is important to understand that while careful review is important to minimise the likelihood that a Token is unsafe, safety cannot be guaranteed by compliance with this specification. Carefully and correctly meeting the requirements outlined in this document will minimize the chance that a Token is exposed to a number of known vulnerabilities, and is thus likely to be more secure than a Token that contains a known exploitable vulnerability. However, it is not a guarantee that there are no vulnerabilities.
Please see also the Disclaimer of Warranty and Liability.
The document is structured as a set of requirements, that are intended for several different audiences who are each likely to use them is slightly different ways:
This version of the specification covers Tokens that implement ERC standards, and Solana Tokens.
While the content of this specification might be useful for assessing other types of Tokens, the BSSC has not explicitly considered them in developing this specification.
Future revisions of this specification MAY cover more types of Token.
This specification is primarily directed at upgradable Tokens, and has many requirements on the Token Project to ensure that governance and upgrades are not a source of significant risk.
Tokens that do not have a generally active Token Project can still conform to the specifications requirements if they are immutable (meaning there are no Privileged Roles that can change the Token's functionality in any way), important information about them is generally available, and they meet security requirements, so long as they can meet the minimal requirement of Vulnerability Disclosure Procedure, which does require some entity able to take action in certain circumstances.
The key terms "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document MUST be interpreted as described in [RFC2119] as modified by [RFC8174] when they appear in all capitals, as shown here.
Where a requirement refers to document, the relevant documentation MUST be available to all parties who are intended to be able call the Token Contract and SHOULD be available publicly without restriction.
Where a requirement refers to maintain documentation, auditors MUST review the relevant documentation. Attesting conformance to this specification is an endorsement of the accuracy of such documentation.
Where a requirement refers to equivalent standards or guidelines, attesting conformance is an explicit endorsement that the relevant specification is an appropriate alternative in the circumstances.
An attestation of conformance to this specification MUST include the Token Name and Token Symbol as defined by the Token Contract, and the address(es) of the Token Contract on the blockchain(s) where conformance is claimed.
The TIS requirements are spread over 4 general domains, plus requirements that are specific to different types of token:
This division is intended to help drive careful consideration of the diverse aspects of security that all contribute to ensuring a Token is sufficiently well-secured to enable a high level of confidence to third parties integrating it.
Token
Allocation
The Token
Project MUST document Token
allocations and vesting schedules
Purpose: Provide transparency for future events that will impact supply
Is
it native, bridged, wrapped?
The Token
Project SHOULD document whether
the Token is native, bridged, wrapped, and other blockchains where the
Token
Project has deployed the Token
Purpose: Identify some important external factors that can impact the value of the Token
Token
Rebasing
The Token
Project MUST document Any
circumstances in which the Token will rebase, and how such rebasing is
applied
Purpose: Provide transparency into mechanisms that vary the value of a Token.
Trading
History
The Token
Project MUST document The Trading
and TVL history of the Token since deployment
Purpose: Enable transparency of the market history of a Token.
It is sufficient to provide a reference to one or more up-to-date third party services that openly publish this information, and on well-known blockchains and especially for well-known Tokens that is a common approach.
Price
Discovery Mechanism
The Token
Project MUST document If the Token
Contract supports Minting or Burning, what automated price discovery
mechanisms are available.
Purpose: Provide transparency into mechanisms that vary the price of a Token
Stablecoin
Backing
If the Token claims to be a Stablecoin,
The Token
Project MUST document an
explanation of the stabilization mechanisms for the Token's value.
Purpose: Provide some transparency into the mechanism that underpins the value of a Stablecoin.
Protect
Backing Assets from Issuer Insolvency
If a Token is backed
by an off-chain or real-world asset, the Token
Project MUST document how the
backing asset is protected if the entity holding it loses legal
control.
Purpose: Provide transparency into whether a Token's backing survives the insolvency of the entity holding it.
This includes how the backing is segregated or held bankruptcy-remote so it does not fall into that entity's estate, and whether redemption rights survive.
Identify
Parties Controlling Critical Actions
The Token
Project MUST maintain
documentation identifying the parties and contracts that participate
in authorizing key modifications including:
It is sufficient, and in many cases a good practice because it avoids exposing individuals to further risk, to identify an organization that manages a specific role rather than identifying a specific individual concerned.
Purpose: Provide transparency into the controllers of functions that can impact the value of a Token.
Document
Governance
The Token
Project MUST document the
processes for making and implementing decisions in relation to the Token
Contract.
Purpose: Ensure transparency for ways the Token. can be changed
Identify
Governance participants
The Token
Project SHOULD maintain
documentation identifying all individuals holding Privileged
Roles or participating in governance of the Token
Contract.
Purpose: Help users and security auditors to understand the role of the Token Project in managing the Token Contract, and to assess related risks and risk management.
It is important to understand what work has been done to ensure the Token's security.
Pass Code Audit
The Token
Project MUST maintain
documentation that the Token
Contract has passed a code security audit.
Purpose: Provide reassurance that the Token Contract does not include known vulnerabilities which malicious parties could exploit, leading to a sudden loss of value.
A Token Contract is by definition a Smart Contract. While this specification provides requirements relevant to its function as a Token, it is important to meet security requirements that apply to all Smart Contracts, to minimise the likelihood that the Token Contract contains a well-known vulnerability and can be exploited by a malicious party, or malfunction due to a bug, resulting in undesirable and unexpected behaviour.
Audit Code to a Standard
The audit passed for Pass Code Audit SHOULD attest that the
Token Contract
conforms to the BSSC Smart Contract Security Standard [SCSS]
or equivalent.
Purpose: Demonstrate the known vulnerabilities for which the Token Contract has been tested.
Note that the BSSC expects to change the level of this requirement to "MUST" in a future revision, probably effective by the beginning of 2028.
Publish
Code Audit Report or Attestation
The Token
Project SHOULD document all code
security audits of the Token
Contract in order to demonstrate the security posture of the Token
Contract. The Token
Project MAY publish an attestation confirming the completion of
a code security audit in lieu of publishing the full code security audit
report.
Purpose: Provide reassurance that the Token Contract does not include known vulnerabilities which malicious parties could exploit readily, leading to a sudden loss of value.
Limit
Privileged Roles
Privileged
Roles MUST be strictly limited to those necessary for proper
performance of the Token
Contract.
Purpose: Any unnecessary Privileged Role is a potential attack vector, and potential cause of undesired and unexpected behaviour.
Decentralize
Privileged Roles
Privileged
Roles SHOULD be decentralized.
Purpose: If a Privileged Role is held by a single actor, it can become a single point of failure, making it impossible to manage a Token in case that actor is unavailable, or vulnerable to manipulation in case of a malicious or compromised actor.
For reliability, it is important to minimize the cases where single individuals can carry out Critical Actions alone. At the same time, to mitigate the risk that aspecific individual expected to perform Critical Actions is unavailable, it is important to maintain redundant Privileged Roles.
This can be achieved through a variety of approaches, including organizational controls such as a requirement for separate approvals. Best practice is to implement these through Multisig techniques including Multi-Party Computing, or governance provisions implemented within the Smart Contract System, where the number of signatures is high enough to reflect the importance of the action, and does not assume all signatories are available.
Note that in cases such as Incident Response it is especially important to balance the need for rapid protective action with the risk that centralizing the necessary capacities increases vulnerability in the case of a malicious actor, or of an honest actor being compromised.
Best practice includes ensuring that automated agents cannot exercise privileged roles, except in emergency incident response situations where their capabilities reflect their capacity to respond faster than a human actor, for example pausing transactions, but are also constrained to reflect their lack of trustworthiness
Document
Privileged Roles
The Token
Project MUST document all Privileged
Roles for the Token
Contract.
Purpose: Because Privileged Roles are a common attack vector, if they are unidentified they are unmonitored and thus especially vulnerable to manipulation by the Token Project or another malicious actor.
Secure
Privileged Roles
The Token
Project MUST maintain
documentation that entities with Privileged Roles (including as
participants of a Multisig
or as developer of code) implement comprehensive security and compliance
standards based on the identified risks related to their role.
Purpose: Protect Privileged Roles from manipulation by a malicious actor
For example, showing that the Token Project conforms to [SOC 2], [ISO 27001], or relevant blockchain-specific security practices such as the Blockchain Security Standards Council's "Key Management Standard" [KMS] and "General Security and Privacy Guidelines" [GSP].
Vulnerability
Disclosure Procedure
The Token
Project MUST document a secure
procedure for responsible disclosure of vulnerabilities found by third
parties.
Purpose: Provide an opportunity for a party who discovers a vulnerability in a Token to alert the Token Project, enabling them to fix it before it is publicly disclosed.
As a minimum requirement, this enables a replacement Token Contract to be deployed, and Token holdings to be migrated into the new Token Contract.
Best Practice is that the Token Project has "24/7" coverage with the capability to respond to a wide range of risks and reports in a timely manner.
Bug Bounty
program
The Token
Projects SHOULD offer sufficient incentives to motivate
responsible disclosure of vulnerabilities found by third parties.
Purpose: Providing an incentive to report vulnerabilities can induce someone who discovers a vulnerability to report it rather than to exploit it.
As well as providing information on secure channels that enable responsible disclosure of vulnerabilities, and that provide an effective response, best practice is to offer a "Bug Bounty Program" that provides incentives to third parties who responsibly submit vulnerabilities that are confirmed as legitimate risks. Determining the amounts that bug bounties pay is typically informed by the value of disclosure or impact of exploitation, and the Smart Contract Project’s risk tolerance and overall financial state.
No
Transfer or Method Hooks
The Token
Contract SHOULD NOT implement any Transfer
Hooks
Purpose: Ensure that transfers do not have extra consequences making them harder to understand
Note that any Transfer Hook needs to meet the requirements for documentation, governance, and security review in order to ensure that the system is reliable.
ERC tokens can add Transfer
Hooks in many ways, while Solana Program 2022 tokens do so
through the transfer_hook extension.
Document
Transaction Limits
The Token
Project MUST document any
limitations on the number or total value of transactions a user can
initiate within a given timeframe.
Purpose: This is important information to help users fairly assess the Token.
Define
Transaction Size Limits
The Token
Project MUST document any
thresholds for the amount of tokens a user can send in a single
transaction.
Purpose: Help users assess the Token's tradeability, which impacts liquidity
Avoid
Transfer Fees
The Token
Contract SHOULD NOT charge fees on transfers.
Purpose: Promote liquidity by minimizing transaction fees to gas cost
Fix
Transfer Fees
Transfer fees MUST NOT be variable or
upgradeable unless the Token
Project maintains
documentation identifying the parties or contracts that control any
modifications to them.
Purpose: This helps understand the risk that Transfer fees change, which can affect Token holders or the value of the Token.
Restrict
Transfers from Blocked or Frozen Accounts
If the Token
Contract implements a method to block or freeze accounts,
transfers initiated from a blocked or frozen address MUST revert.
Purpose: This ensures predictable known behavior for Tokens that enable account blocking.
Document
Whether Blocked Accounts Can Receive Transfers
The Token
Project MUST document whether
deposits to blacklisted or frozen addresses are allowed or blocked.
Purpose: Ensure predictable known behavior.
Make
Confidential Transfers Auditable
If a Token enables
confidential transfers (transfers whose amounts and/or parties are
hidden or encrypted on-chain), the Token
Contract MUST enable designated custodians and compliance
parties to reconstruct and prove transfer amounts.
Purpose: Ensure that Token transfers can be verified for compliance purposes, even where transfer details are otherwise confidential.
For example, Solana's Token-2022 confidential transfer
extension exposes an auditor key, and Zcash uses viewing keys, both of
which let an authorized party see otherwise-hidden transfer details.
Similar mechanisms on other chains are also in scope.
ERC: Implement ERC Token Standards
The Token
Project MUST document how the Token
Contract completely and correctly implements at least one of
the following ERC Token Standards:
Purpose: This ensures predictable known behavior.
ERC:
Document ERC Implementation Upgradability
If the Token is
upgradeable, the Token
Project MUST document all code
relevant to the Token
Contract's implementation of ERC Token standards that can be
upgraded.
Purpose: Clarify the scope of upgrade risks
ERC: Balance Changes Create Transfer Events
Any methods in the Token
Contract that change Token balances, such as
transfer(), or methods to mint and burn tokens MUST emit a
Transfer event as described in [ERC-20].
Purpose: Ensure that changes to overall supply or distribution are easily tracked through standard methods, for transparency.
Note that ERC-20 requires that even a transfer of a zero amount emits
a Transfer event.
ERC: Mint and Burn as per ERC-5679
Methods in the Token
Contract that change the Total Supply of the token MUST emit a
Transfer event as specified in [ERC-5679]
Purpose: This ensures that changes to overall supply are easily tracked, for transparency.
[ERC-5679] requires that minting or
burning ERC tokens will emit Transfer events referring to
the zero account, which otherwise would not make transfers.
Because the to and from parameters of those
events are indexed they enable efficient tracking of
minting or burning events by filtering for Transfer events
involving the 0x0 account.
This means minting tokens emits a Transfer event from
the Zero address, and burning tokens emits a Transfer to
the zero address.
For example
function _mint(address account, uint256 value) internal {
//Actual logic, check, effects, interactions, ...
emit Transfer(address(0), account, value);
}
ERC: No Fallback Function
The Token
Contract SHOULD NOT have a fallback function. If the Token
Contract has a fallback function, the _Token
Project MUST document the circumstances
that will cause the function to be executed, and what it does.
Purpose: Avoid, or clearly document, the uncommon pattern of using a fallback function rather than a transaction reverting directly
ERC:
Revert Blocked Transfers
Where a Token
Contract blocks a transaction from interacting with a specific
account, it MUST cause the transaction to revert with a clear error
message, for example "Transfer to blocked address is not allowed".
Purpose: Ensure that transactions that revert because an account is blocked from receiving are clearly identifiable,
Solana:
SPL or 2022 Program Tokens
The Token MUST be owned by
either the Solana SPL Token Program, or the Token 2022 Program.
Purpose: Ensure the Token's behavior and security properties are well-understood and correspond to well-known patterns.
In practice this means the token implements one of the sets of attribute values in the following table:
| Token Program | Attribute | Value |
|---|---|---|
| SPL Token | Token Type | SPL Token |
| Program ID | TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA | |
| Token 2022 Program | Token Type | SPL Token 2022 |
| Program ID | TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb |
Solana SPL Tokens created under the original Token Program (TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA) do not include custom or per-token logic. Instead, the logic is centralized within the program itself, and all Token instances are state representations governed by that shared logic. This means that it has no unknown behavior
Verifying that a Token is owned by the official Token Program ensures that:
The "Token 2022 Program" (TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb) is a superset of the original Token Program. It maintains compatibility with the base instruction set while introducing new functionality through modular extensions.
Ensuring that a Token is owned by the official "Token 2022 Program" guarantees:
Because the Token behaviour is customizable based on extensions, there are further requirements that apply to Tokens owned by the "Token 2022 Program".
"ERC-20: Token Standard", F. Vogelsteller and V. Buterin, Ethereum Improvement Proposals 2015. https://eips.ethereum.org/EIPS/eip-20
"ERC-1155: Multi-Token Standard", Witek Radomski, Andrew Cooke, Philippe Castonguay, James Therien, Eric Binet, and Ronan Sandford, Ethereum Improvement Proposals 2017. https://eips.ethereum.org/EIPS/eip-1155
"ERC-1363: Payable Token", Vittorio Minacori, Ethereum Improvement Proposals 2018. https://eips.ethereum.org/EIPS/eip-1363
"ERC-3643: Token for Regulated Exchanges", Joachim Lebrun, Tony Malghem, Kevin Thizy, Luc Falempin, Adam Boudjemaa, Ethereum Improvement Proposals 2021. https://eips.ethereum.org/EIPS/eip-3643
"ERC-5679: Token Minting and Burning", Zainan Victor Zhu, Ethereum Improvement Proposals 2022. https://eips.ethereum.org/EIPS/eip-5679
"ERC-7943: Universal Real World Asset Interface", Dario Lo Buglio, Tino Martinez Molina, Mihai Colceriu, Ethereum Improvement Proposals 2025. https://eips.ethereum.org/EIPS/eip-7943
"BSSC General Security and Privacy Guidelines v2", Ed. Joe D'annolfo, BSSC 2026. https://specs.blockchainssc.org/gsp/v2.html
ISO/IEC 27001 - Information security management systems, ISO. https://www.iso.org/standard/27001
"Key Management Standard", Ed. Mark Nesbitt, Akshar Rawal, and John Kemp, BSSC 2025. https://specs.blockchainssc.org/kms/
"Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, IETF 1997. https://www.rfc-editor.org/rfc/rfc2119.html
"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", B. Leiba, 2017. https://www.rfc-editor.org/rfc/rfc8174.html
"BSSC Smart Contract Security Standard", Ed. J Neufeld and Chaals Nevile, BSSC 2026. https://specs.blockchainssc.org/scs/
"SOC 2® - SOC for Service Organizations: Trust Services Criteria", AICPA. https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2
The specification's scope has been broadened to cover Solana tokens as well as ERC-20 tokens.
In an editorial reorganisation, the Requirements Domain Network Security (which had no requirements) was removed, while the requirements in Requirements Domain Upgradability were merged into other Requirements Domains as appropriate. A new section was added to gather requirements that are specific to ERC-20 tokens, and an analogous section was added for Solana tokens.
The following changes since version 1 affect conformance, or are otherwise substantial:
tx.origin, as redundant with
Pass Code Audit, and
Audit Code to a StandardRequirements related to the EthTrust specification were generalized to cover a wider range of tokens and languages, and the specific dependency on that specification was removed.
Mint or Burn Events
in favour of ERC20: Mint and Burn as per ERC-5679Requirements specific to ERC-20 tokens were separated into a new ERC Tokens: specific requirements section, and the name prefixed with "ERC:" accordingly, but their URLs have not changed.
Many requirements involving documentation now refer to the explicitly defined terms document and maintain documentation, which clarify for whom the documentation needs to be available. As well as new requirements, this change has been made in the following existing requirements:
The requirements are the core of this document. Each requirement has a standard structure:
As an example:
ERC20: Mint and Burn as per ERC-5679
Methods in the Token Contract that change the Total Supply of the token MUST emit aTransferevent as specified in [ERC-5679]Purpose: This ensures that changes to overall supply are easily tracked, for transparency.
[ERC-5679] requires that minting or burning ERC-20 tokens will emit
Transferevents referring to the zero account, which otherwise would not make transfers.Because the
toandfromparameters of those events areindexedthey enable efficient tracking of minting or burning events by filtering forTransferevents involving the0x0account.
has the name "ERC20: Mint and Burn as per ERC-5679".
Its stable URL is https://specs.blockchainssc.org/TIS/#req-mint-burn-erc-5679 which points to the requirement in the latest published version of the specification.
The statement of requirement is
Methods in the Token Contract that change the Total Supply of the token MUST implement those functions as specified in [ERC-5679]
The rest of the text is explanatory. While it is helpful to some audiences, it is not a formal part of the requirement that needs to be met.
Requirements are grouped into a set of Requirement Domains, and generally into smaller groups within each Requirement Domain, as a convenience. Requirements are not prioritized, as specific priorities will depend substantially on specific implementations and use cases.
Some kinds of link used in this document are identified by specific formatting:
This specification has an accompanying Audit Framework, that provides informative guidance on how to assess each requirement, and a checklist that can be used to record an evaluation of a Token against the Standard, and generate a report.
In case of any discrepancy, this document is authoritative.
This document is the BSSC Token Integration Standard, version 2, developed by the Blockchain Security Standard Council (BSSC Inc.) as a replacement for the Version 1 Specification published in May 2025.
The BSSC requests feedback on this document. Feedback can be provided through the BSSC Contact Page.
NO WARRANTIES: THIS SPECIFICATION IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, COMPLETENESS AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL BSSC, ITS MEMBERS OR ITS CONTRIBUTORS BE LIABLE FOR ANY CLAIM, OR ANY DIRECT, SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE SPECIFICATION.
THIRD PARTY RIGHTS: Without limiting the generality of the foregoing, BSSC ASSUMES NO RESPONSIBILITY TO COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENT OR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BE INFRINGED BY AN IMPLEMENTATION OF THE SPECIFICATION IN ITS CURRENT, OR IN ANY FUTURE FORM. IF ANY SUCH RIGHTS ARE DESCRIBED ON THE SPECIFICATION, LICENSOR TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, OR THAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED.