Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Verify Access Control | Contents | next: Verify Deployment Authorization

Implement Upgrade Safety Controls

Statement of Requirement

For high-impact Application Transactions (e.g., upgrades to core protocol contracts), Signature Managers SHOULD require time-locks or multi-party approval before signing.

See it in the specification

Applicability

Purpose

Enable safeguards to protect against "blind" signing high-impact Application Transactions.

Audit Procedure

Verify that Apply Transaction Policies to Signing enables requirements for time-locks on Application Transactions

Success Criteria

The Signature Manager provides a mechanism to configure requirements for signing Application Transactions that include the ability to impose a timelock.

Failure Criteria

There is no mechanism to require timelocks in order to sign Application Transactions

Justifiable Exceptions

This is a useful feature. However, its absence is justifiable on the grounds of keeping code or interfaces simple. Justification for not meeting this requirement does not need to be explicit.

Key Evidence

previous: Verify Access Control | Contents | next: Verify Deployment Authorization