Requesting an Emergency Blockchain Network Update
Urgent issues in blockchain networks may require updates outside the regular change management process. This guide details how to handle emergency network updates to minimize risks and restore services efficiently.
When to Request an Emergency Update
Submit an emergency update request for high-priority incidents when:
- Multiple nodes or the entire network are down
- Critical security vulnerabilities pose significant risks
- A temporary fix is needed to maintain network integrity while a permanent solution is developed
Emergency updates should be rare; always try to follow the standard blockchain change management process for non-emergency updates.
How to Request an Emergency Update
Follow these steps:
- Log a high-priority issue with the Blockchain Support Desk detailing:
- The issue or vulnerability
- Why it qualifies as an emergency
- Proposed update plan (rollback strategy, testing, etc.)
- The Blockchain Change Manager will prioritize the review
- If approved, follow protocols to implement the update
- The emergency change advisory board will review and determine further actions
Final approval is required from network administrators and relevant stakeholders based on risk assessments.
Guidelines for Emergency Updates
During implementation, adhere to these guidelines:
- Form a qualified team for swift execution
- Prepare and validate rollback strategies
- Communicate impacts and downtime clearly
- Follow standard procedures like testing and peer reviews
- Keep detailed documentation for auditing purposes
Emergency updates are subject to audits; ensure thorough records. Request an emergency update when necessary, and our team will work to resolve the issue promptly.