Offboarding

Authored by:

Isaac Patka

SEAL | Shield3

Geoffrey Arone

Shield3

Louis Marquenet

Opsek

Pablo Sabbatella

SEAL | Opsek

Dickson Wu

SEAL

Reviewed by:

Piña

Coinspect

engn33r

matta

The Red Guild | SEAL

When leaving a multisig, follow these steps:

Signer removal

1. Coordinate with team - Notify other signers and schedule the removal transaction
2. Execute removal - Follow the Signer Rotation Runbook
3. Verify removal - Confirm your address has been removed from the multisig
4. Update documentation - Ensure documentation reflects the change

Timing requirements

Teams should define offboarding timelines in advance based on the multisig's role, risk, and governance process.

For higher-risk or emergency-sensitive multisigs, signer removal may need to happen on a much shorter timeline. For lower-risk setups, the appropriate timeline may be longer. Document the expected response window in your internal policy and make sure it is understood by all signers. For example:

• Emergency-class multisigs: Complete signer removal within 48-72 hours
• Critical-class multisigs: Complete signer removal within 7 days
• Other multisigs: Complete signer removal within 14 days

Clean up access

• Leave all multisig communication channels (Signal, Telegram, etc.)
• Remove access to any sensitive shared documents or resources
• Delete any locally stored sensitive multisig information

Handover

• Share any relevant context or pending items with remaining signers
• Provide contact information if needed for transition questions