Domain: 1. Protocol Onboarding |
Level: MUST | Type: Preventive
Statement of Requirement:
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.
Purpose:
Demonstrate the Node Operator understands a Protocol.
Audit Procedures
Verify the Node Operator identifies parties responsible for meeting
their technical and non-technical responsibilities with respect to the
protocol, including operational, security, governance, compliance,
legal, reporting, and participation, as well as any other
protocol-specific obligations.
Interview responsible personnel to confirm that
documentation provided is complete, and accurately describes how the
Node Operator manages protocol operation
they understand and are able to meet their responsibilities.
Verify that documentation
is updated as required.
accurately covers upgrade mechanisms, governance processes, voting
procedures, emergency mechanisms such as killswitches, pauses and
circuit breakers, and protocol-specific operational nuances.
Verify that documentation is updated as required.
Key Evidence
Protocol responsibility documentation per protocol
Service level agreements or service descriptions
Documentation of assigned responsibilities and operational
runbooks
Auditor-verified customer-accessible publication
Service catalogs or CMDBs reflecting responsibilities
Success Criteria
Documented responsibilities exist for all operated protocols
covering both technical and non-technical
Documentation is customer-accessible (auditor-verified)
No significant protocol-mandated responsibilities are missing
Personnel can articulate responsibilities without reliance on the
document
Failure Criteria
Any of these circumstances is likely to mean the Requirement is not
met.
No documented responsibilities exist for any operated protocol
Documentation covers only technical or only non-technical
responsibilities
Significant protocol-mandated responsibilities are missing
Documentation is not accessible to customers
Common Failure Patterns
Documentation covers consensus duties but omits governance
responsibilities
Responsibilities are documented in internal wikis but not shared
with customers
Documentation is generic across all protocols rather than
protocol-specific
Non-technical responsibilities (regulatory, customer communication)
are absent
No distinction between operator and customer/delegator
responsibilities