Communication Setup

Authored by:

Isaac Patka

SEAL | Shield3

Geoffrey Arone

Shield3

Louis Marquenet

Opsek

Pablo Sabbatella

SEAL | Opsek

Dickson Wu

SEAL

Reviewed by:

Piña

engn33r

🔑 Key Takeaway: Give every multisig a dedicated E2EE primary channel, a backup on a different platform, and paging for critical response windows.

Establish secure primary and backup channels before the first real signing ceremony so emergencies are not the first time the team coordinates.

Primary channel

Set up a dedicated communication channel for multisig operations:

• Platform: Signal recommended (end-to-end encryption)
• Membership: Multisig signers + authorized management only
• Configuration: Notifications enabled, disappearing messages for sensitive discussions
• Naming: Clear channel naming convention (e.g., "X-Treasury-Multisig")

Backup channels

Configure backup communication on a different platform:

• Platform: Different from primary (if Signal primary, use Telegram/Discord/Slack)
• Same membership restrictions as primary
• Document access procedures for all signers

Paging system (Critical/Emergency Multisigs)

For multisigs requiring rapid response:

• Configure alerts that can reach signers 24/7
• Include essential info in page: multisig name, urgency level, primary action needed
• Link to emergency runbooks in notification message
• Test quarterly to ensure reliability

Further Reading

• Multisig for Protocols overview: how the pages of this framework fit together
• Emergency Procedures: when these backup channels get used
• Incident Reporting: where reports are sent once contact is made
• Encrypted Communication Tools: choosing platforms for signer coordination