Putting Blockchain Standards Into Practice: What’s New for Token Integration and Node Operations
Blockchain technologies continue to evolve, and the standards that support them need to evolve as well. New networks, token types, operational practices, and emerging technologies can introduce new considerations and change how existing requirements are applied.
Our latest updates to the Token Integration Standard (TIS) and Node Operation Standard (NOS) reflect that evolution.
Token Integration Standard Version 2 expands the specification to cover additional Ethereum Virtual Machine (EVM)-based token types as well as Solana tokens. Node Operation Standard Version 3 updates requirements for organizations operating blockchain nodes. Both specifications are being released with new Audit Frameworks that provide additional guidance for evaluating conformance.
We are also sharing example evaluations of real tokens using TIS v2, along with new report-generation tools that make evaluation results easier to document and share.
Together, the updated specifications and supporting resources show how BSSC standards can evolve through implementation and industry input, while giving organizations additional tools for applying them in practice.
Expanding the Token Integration Standard
Organizations integrating tokens into exchanges, wallets, custody platforms, and other products need to understand the characteristics and potential risks of those assets. That can be difficult when tokens differ not only in their implementation but also in the networks and standards they use.
Token Integration Standard Version 2 broadens the types of tokens that can be evaluated against a common set of requirements. The original specification covered ERC-20 tokens. Version 2 expands the specification to additional EVM-based token types and adds support for Solana tokens. We have also released an audit framework and checklist.
The objective is not to determine whether a token is simply “safe” or “unsafe.” Token integrations involve different use cases, architectures, and risk tolerances. The standard provides a structured way to examine characteristics that an organization should understand as part of its own evaluation.
The updated specification provides clearer expectations around areas including sensitive token controls, such as the ability to mint, freeze, or upgrade tokens. For asset-backed tokens, it also addresses information related to custody of the backing assets and what happens to those assets if the custodian becomes insolvent.
These are not theoretical considerations. They can materially affect the risks an organization assumes when it decides to support an asset.
TIS v2 gives issuers a clearer understanding of the information integrators may need, while giving exchanges, wallets, custodians, and other organizations a more consistent way to evaluate it.
Applying TIS v2 to Real Tokens
One of the most important parts of this release is not another specification. It is a set of examples showing what happens when the specification is actually used.
BSSC is publishing sample evaluations of real tokens using TIS v2. These examples demonstrate how an evaluator can work through the requirements, determine their status, and identify areas that may deserve additional attention.
That distinction matters. A standards-based evaluation is not a substitute for an organization’s own risk assessment. It provides a structured way to surface relevant information.
The evaluations also provide practical guidance for people applying the standard themselves. A written requirement can seem straightforward until an evaluator has to decide what evidence demonstrates conformance in a real implementation. Seeing examples can help show how those judgments are made.
The evaluation work also helped refine the standard. Applying the TIS v2 draft to real tokens helped the BSSC team identify areas where requirements could be clearer, including how to evaluate older token contracts that do not implement newer interfaces. One resulting clarification allows those contracts to be evaluated based on observable behavior rather than whether they implement a newer interface.
That is exactly the kind of feedback standards need. Applying a requirement in practice can expose ambiguity that is difficult to see while drafting it.
Updating the Node Operation Standard
Node Operation Standard Version 3 takes the same practical approach to a different part of blockchain infrastructure. Blockchain nodes perform essential functions within decentralized networks, but operating them securely involves both familiar infrastructure practices and considerations specific to blockchain.
NOS v3 updates the standard to reflect changes in how that infrastructure is being operated and managed. Among the updates are stronger controls around automated and AI-generated changes, along with updated expectations around access, network exposure, and preparedness for future changes in cryptography.
These changes reflect how node operations continue to evolve. As new technologies and risks emerge, the standard needs to account for them without prescribing a single implementation approach.
As with TIS v2, the updated Node Operation Standard is accompanied by a new Audit Framework and checklist.
Making Requirements Easier to Evaluate
The Audit Frameworks are a significant part of these releases because a specification alone cannot answer every implementation question. Each framework provides guidance at the individual-requirement level, including the intent of the requirement, relevant evidence an evaluator may examine, and what constitutes meeting or failing to meet it.
That makes the frameworks useful for more than formal audits:
- An auditor can use the guidance to support a more consistent evaluation.
- A developer or operator can use the same material earlier in the process to understand what evidence may eventually be needed.
- Organizations evaluating third-party systems can better understand what a requirement is intended to demonstrate.
In each case, the goal is greater consistency between what the specification says and how people apply it. BSSC is also adding report-generation capabilities to the new Audit Frameworks, making it easier to turn evaluation results into a consistent format for documenting and sharing findings.
Together, the Audit Frameworks, example evaluations, and reporting tools are intended to make the standards more practical to use. They help bridge the gap between defining a requirement and understanding how that requirement can be applied and evaluated in practice.
Implementation Lessons Guide Standards
There is a broader principle behind these releases. Standards should be stable enough for organizations to rely on, but they cannot be static.
Token models change. Infrastructure practices change. Tools such as AI become part of development and operational workflows. Evaluators encounter edge cases that were not obvious when a requirement was written.
A useful standards-development process needs a way to absorb that experience without forcing organizations to continually adapt to wholesale changes. The TIS evaluations offer one example of that feedback loop. Applying the specification to real tokens exposed implementation questions that could then be clarified in the standard and supporting guidance.
Audit Frameworks create another source of feedback. When evaluators repeatedly encounter uncertainty about the same requirement or evidence, that can help identify where additional guidance may be useful. The specification establishes the common expectation. Implementation and assessment help test whether that expectation works in the real world.
From Publishing Standards to Putting Them Into Practice
These releases build on BSSC’s recent work to make blockchain standards more practical to apply and assess. The Blockchain Transaction Lifecycle Security Standard extended requirements across the transaction process, while Version 2 of the Smart Contract Security Standard introduced extensive auditing guidance through its Audit Framework.
TIS v2 and NOS v3 continue that progress with broader coverage, new assessment guidance, real-world examples, and tools for documenting results.
The goal is not simply to publish more standards. It is to turn expertise from across the industry into requirements organizations can understand, apply, and evaluate, then use what we learn from implementation to make those standards better.
No standard or audit can eliminate risk. But clearer requirements, practical guidance, and real-world examples can give organizations a better basis for understanding where risk exists and how they are addressing it.
That is how standards become more than documents. They become tools people can actually use.
BSSC encourages token issuers, exchanges, wallets, custodians, node operators, auditors, and other organizations working with blockchain and digital assets to review the updated specifications and supporting resources and provide feedback based on their experience applying them.
Review the latest BSSC standards and supporting resources at the BSSC standards page.