previous: Evaluate
Protocol Crypto-agility and Post-quantum Plans | Contents page | next: Follow Protocol
Consensus
Follow Protocol Conventions
BSSC Node Operation - Audit Framework
Domain: 2. Network Participation |
Level: MUST | Type: Preventive
Statement of Requirement:
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.
See it in the specification
Purpose:
Help maintain the network in optimal state, mitigate risks of
slashing or other operational failures
Audit Procedures
Verify that responsibilities and operational practices identified for
Document Protocol
Responsibilities are carried out in practice
Key Evidence
Evidence provided for Document Protocol
Responsibilities
Node configuration runbooks and protocol best practice compliance
documentation
On-chain performance data (attestation effectiveness, proposal
success rates, sync committee participation)
Validator performance reports from tools such as beaconcha.in, Rated
Network, or equivalents
Live monitoring dashboards showing real-time node performance
metrics
Alerting configurations for missed duties
Success Criteria
Documentation exists mapping protocol best practices to operator
configuration
On-chain data demonstrates consistent, above-threshold participation
throughout the audit period
Isolated missed duties are documented with root cause analysis and
remediation
Monitoring and alerting in place to detect participation
failures
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No documentation linking operator configuration to protocol
conventions
On-chain data reveals sustained or recurring missed duties below
network-acceptable thresholds
Patterns of missed duties without documented root cause or
remediation
No monitoring to detect protocol participation failures
Common Failure Patterns
Nodes configured with defaults without verifying alignment with
current best practices
Configuration correct at deployment but not updated after protocol
upgrades
Attestation effectiveness degrades from infrastructure issues (clock
drift, resources, latency) not monitored
Best practices for one protocol incorrectly applied to a different
protocol
Missed proposals due to MEV-boost relay misconfiguration or builder
API failures
Other Relevant Standards
A.5.37, A.8.9
CC8.1, CC7.2
2.2
PR.PS-01, DE.CM-01
previous: Evaluate
Protocol Crypto-agility and Post-quantum Plans | Contents page | next: Follow Protocol
Consensus