This checklist is offered as a tool to help assess conformance to the BSSC Node Operation Standard specification.
This version corresponds to the BSSC Node Operation Standard, version 3, published 17 November 2026. In case of any discrepancies between this checklist and the Specification document, the Specification is the authoritative document.
| BSSC Node Operation Standard version 3 | ||
|---|---|---|
| Specification URL: https://specs.blockchainssc.org/nos/v3.html | ||
| The Node Operator evaluated | Name(s): | |
| Short name / ID: | ||
| Scope of evaluation: | ||
| Evaluator | Name: | |
| Contact Details: | ||
| Evaluation | Date completed: | |
| Outcome / comments: | ||
| Requirement Name | Statement of Requirement | Status | Comments |
|---|---|---|---|
| Manage Key Security | A Node Operator MUST securely manage Keys and Key material in accordance with the requirements in the BSSC Key Management Standard or equivalent standards. [KMS] |
||
| Implement Standard Security Practices | A Node Operator MUST follow the guidance in the BSSC General Security and Privacy Guidelines [GSP] or an equivalent standard. |
||
| Document Protocol Analysis | Node Operators MUST document their process for protocol selection and risk analysis of a new protocol |
||
| Monitor Protocol Changes | Node Operators MUST implement a process that continuously monitors changes to the network and adjusts risk accordingly |
||
| Document Supply Chains | Node Operators MUST maintain documentation of their Software Bill Of Materials, including risk analysis and management for all node-related components. |
||
| Document Protocol Responsibilities | Node Operators MUST document the protocol's operation, the responsibilities they have with respect to the protocol, and MUST maintain documentation identifying the responsible parties for managing those responsibilities |
||
| Test in Controlled Environments | Node Operator MUST conduct pilot testing in a controlled test network environment to validate a protocol's performance, interoperability, and security posture, prior to mainnet deployment |
||
| Comply with Applicable Regulation | The node operator MUST adhere to applicable anti-money laundering and national security address blacklists, or locally established equivalent standards or guidelines, whenever such measures are available |
||
| Document Protocol Cryptography Algorithms | Node Operators MUST document the cryptographic algorithms employed by the protocol, including signature schemes, hash functions, and key exchange mechanisms. |
||
| Evaluate Protocol Crypto-agility and Post-quantum plans | Node Operators SHOULD evaluate the protocol's roadmap or capability for transitioning to quantum-resistant cryptography. |
||
| Follow Protocol Conventions | Nodes MUST perform all standard activities — including attesting, executing, proposing, and any other responsibilities — in strict accordance with the documented best practices of their respective network. |
||
| Follow Protocol Consensus | Nodes MUST remain on the most recent accepted chain |
||
| Document Anti-slashing Controls | Node Operators MUST maintain documentation of the controls they follow to prevent slashing or other penalties for non-participation in network duties |
||
| Maintain Boot Peers Lists | The node operator MUST maintain boot peers lists |
||
| Configure Discovery Appropriately | Nodes MUST only allow discovery by peers where necessary to support the network. |
||
| Verify Discovery Configuration | Node Operators MUST review and update the discoverability configuration of all nodes every month. |
||
| Limit Consensus Power | Limit
Consensus Power
|
||
| Practice Client Diversity | Node operators SHOULD deploy a diverse set of client software implementations where they are available. |
||
| Balance Client Share | Node Operators SHOULD NOT run any single client software representing more than 2/3 of their overall deployment. |
||
| Document Continuity Process | Node Operators MUST maintain documentation of their fault-tolerance strategies and continuity and failover procedures. |
||
| Document Uptime Monitoring | Node Operators MUST maintain documentation of processes for monitoring node uptime and remediating detected issues. |
||
| Distribute Nodes | Nodes SHOULD be distributed among multiple hosting providers, data centers, and geographic regions. |
||
| Document Recovery Procedures | Node Operators MUST maintain documentation of the procedures they follow for the deployment, recovery, and updating of nodes. |
||
| Document Procedural Deviations | Node Operators MUST maintain documentation of any deviations from documented procedures for node deployment, recovery, and update. |
||
| Document Cryptography Migration Procedures | Node Operators MUST document plans and any procedures for cryptographic migration scenarios, including protocol-level transitions to post-quantum algorithms. |
||
| Prepare for Cryptography Migration | Node Operators SHOULD maintain operational readiness to adopt updated cryptographic schemes in accordance with protocol governance timelines. |
||
| Provision Nodes Sufficiently | Node operators MUST provision nodes with sufficient hardware and network resources—including, but not limited to, disk space, disk speed, network speed, and bandwidth—to effectively perform their designated duties. |
||
| Configure Resilient Nodes | Node Operators MUST maintain documentation of resilience to spikes in activity, with relevant measures assessed and if necessary updated at least annually. |
||
| Use Remote Signers | Remote signers SHOULD be employed |
||
| Secure Remote Signer Alternatives | Where remote signer support is unavailable, operators MUST implement alternative security controls to safeguard key material. |
||
| Communicate Securely | Node Operators MUST use appropriately secured communication methods that adhere to industry-standard encryption protocols |
||
| Document Unsecured Channels | Node Operators MUST maintain documentation of any instance where encryption is not used for information in transit, including a risk assessment. |
||
| Restrict Privileged Access | Access to node control planes, logs, and signed Stored Transactions MUST be restricted to authorized parties, by implementing the Principle of Least Privilege. |
||
| Minimize Network Exposure | The network exposure of node clients MUST be minimized to include only the services essential for effective network operation |
||
| Restrict Agentic Write Access | Node Operators MUST NOT allow autonomous agents such as generative AI tools unmoderated write access to production code |
||
| Log Access Events | Node Operators MUST record all access events for the control plane. |
||
| Review Logs | Node Operators MUST review event logs for anomalies at least every 24 hours. |
||
| Retain Logs | Node logs MUST be retained for a minimum of 90 days, or a longer period where required by applicable regulation or documented retention policies. Security-relevant logs (access events, authentication events, configuration changes) SHOULD be retained for at least 180 days. |
||
| Aggregate Logs | Node logs SHOULD be aggregated where feasible. |
||
| Do Not Log Sensitive Information | Logs containing sensitive information, such as cryptographic keys or personally identifiable information (PII), MUST be suppressed, sanitized, or otherwise secured to prevent unauthorized access. |
||
| Use Automated Monitoring | Node Operators SHOULD use automated monitoring systems to detect operational anomalies |
||
| Document Incident Response Plans | Node Operators MUST maintain documentation of the Security incident response procedures they follow. |
||
| Follow Incident Response Plans | In the event of a security incident, Node Operators MUST execute documented Incident Response Procedure to ensure node availability and to facilitate a secure and safe return to operations. |
||
| Provide Rapid Human Response | Node Operators SHOULD ensure that automated incident responses are limited in scope, and that timely human oversight is engaged |
||
| Follow Reward Conventions | Nodes that are eligible for rewards MUST receive any form of incentive in accordance with the specific chain’s established protocols. |
||
| Log Protocol Payments | Node Operators MUST document all rewards or incentives received in a verifiable log. |
||
| Document Insurance | Document
Insurance
|
||
| Document Exit Procedures | Document
Exit Procedures
|
||
| Document Governance Positions | Document
Governance Positions
|