Follow Protocol Consensus

BSSC Node Operation - Audit Framework

Domain: 2. Network Participation | Level: MUST | Type: Detective/Corrective

Statement of Requirement:

Nodes MUST remain on the most recent accepted chain.

See it in the specification

Purpose

Minimize chain forking, and the risk of slashing or operational failures due to following a fork rather than the accepted chain

Audit Procedures

Review procedures for ensuring nodes remain on the canonical chain, including fork-choice monitoring, chain head tracking, hard fork execution, and rollback/resync procedures.

Inspect monitoring infrastructure for chain head tracking and alerts generated for sync status falling behind, chain head divergence, and missed slots/epochs.

If hard forks occurred during the audit period, verify that the operator detected the fork, prepared in advance, executed the upgrade, and verified post-fork chain adherence - see also Monitor Protocol Changes

Verify that recent on-chain activity aligns with the canonical chain with no gaps indicating divergence. For non-validator nodes, verify chain-head comparison logs against independent references.

Key Evidence

Success Criteria

Failure Criteria

Any of these circumstances is likely to mean the Requirement is not met.

Common Failure Patterns

Other Relevant Standards

ISO 27001

A.8.9, A.8.32

SOC 2

CC7.2, CC8.1

PCI DSS

10.4.1, 11.5

NIST CSF

DE.CM-01, DE.CM-09, RS.AN-03