Skip to main content
This is a suggested baseline for monitoring multisig wallets, a sensible starting point you can adopt as-is or tune. Thresholds, voter sets, and destinations are configured per workspace during setup, so treat the numbers here as recommended defaults rather than fixed values. The rules below build on the Multisig and Governance catalogue and apply to each Safe (EVM) or Squads (Solana) wallet in scope. Wallets on different chains or addresses are monitored as separate units.

What’s covered

Multisig wallet

Each Safe or Squads address gets the standard wallet rule pack: proposals, configuration changes, value thresholds, and balance monitoring.

Derived voters

Range reads the signer addresses from the multisig configuration and applies voter rules to those wallets. A compromised signer key can enable a malicious approval or execution even without direct treasury access.

Suggested wallet rules

Applied to each multisig wallet in scope.

Suggested voter rules

Derived from the multisig, applied to the signer addresses Range reads from the wallet configuration.

Suggested thresholds

How an alert flows

Each alert is routed to any destination your workspace has connected, see Supported destinations. You choose where each alert goes; the rule just decides when one fires.

Setting it up

Configured with you during onboarding:
1

Share your wallets

Provide the multisig addresses (Safe and/or Squads), chains, and signer list.
2

We configure the pack

Range sets up the standard rule pack and destination routing in your workspace.
3

Validate delivery

Confirm alerts arrive as expected in a staging or dry-run period.
4

Go live

Production monitoring is enabled.
What you can tune at setup or later: the wallet inventory, the voter set, value thresholds, balance floors, timezone windows, and destinations. See How alerting works for the general model.
Last modified on June 17, 2026