# Treasury Change Runbook

## Alert: TreasuryUpdated

### Severity: HIGH

### Description
The treasury address has been changed. All platform fees will now be directed to the new address.

### Immediate Actions (< 1 hour)

1. **Verify the Change was Authorized**
   - Check if change was via TimelockController
   - Verify the initiating address
   - Confirm new treasury is a known Safe or authorized address

2. **If UNAUTHORIZED:**
   - Immediately pause affected contracts
   - Alert security team
   - Begin incident response

3. **If AUTHORIZED:**
   - Document the new treasury address
   - Update operational documentation
   - Verify test transaction to new treasury

### Investigation Checklist

- [ ] Change initiator verified
- [ ] New treasury address is a known Safe
- [ ] Change matches approved governance proposal
- [ ] No suspicious preceding transactions
- [ ] Treasury documentation updated

### Verification Steps

1. Check new treasury address on block explorer
2. Verify it's a multi-sig or known address
3. Send test transaction to verify receipt
4. Update monitoring to track new address

### Security Considerations

- Treasury changes should always go through timelock
- New treasury should always be a multi-sig wallet
- Never change to an EOA in production
- Monitor old treasury for any remaining funds

### Related Runbooks

- [Ownership Change](./ownership-change.md)
- [Fee Change](./fee-change.md)
- [Incident Response Plan](./incident-response.md)
