# 2SOLV Phase 9 Incident and Rollback Runbook

## Immediate Response

1. Stop new launch announcements.
2. Preserve logs and current state.
3. Disable public send/broadcast features if wallet safety is affected.
4. Keep endpoint routing stable unless routing itself is the incident.
5. Notify operator and document timestamps.

## Testnet/Ecosystem Rollback

1. Keep CT300 running if public pages are healthy.
2. Restart `2solv-ecosystem-mvp.service` only after checking logs.
3. Validate endpoint nginx with `nginx -t` before reload.
4. Use CT300 failover dashboard only after confirming the snapshot endpoint is responsive.
5. Restore from GFS backup only after confirming backup age and manifest integrity.

## Mainnet Rollback Preconditions

Mainnet rollback is sensitive because public chains are append-only. Before genesis/mainnet launch, define:

- whether launch can be aborted before public mining;
- whether relaunch is acceptable if genesis parameters are wrong;
- who controls seed nodes and DNS;
- how users will be notified;
- which artifacts must be archived for audit.

## Evidence to Capture

- daemon `get_info` output;
- mining status;
- wallet balance/status;
- endpoint nginx config and cert status;
- DNS resolver outputs;
- backup manifest paths;
- app/API HTTP status codes;
- timestamps in UTC and local timezone.