Roadmap

Check whether your contract can be paused and until when, who can pause it, who can upgrade it, how many signatures each takes, and whether any of that power sits with a single key. Read-only, at no cost.

A message on Telegram or Discord when an owner changes, a role is granted or removed, the contract is upgraded, a Safe changes its signers or threshold, the contract is paused or unpaused, or a timelock queues an action. When a timelock's delay is longer than a few minutes, a queued action reaches you before it can run. You also hear when a pause window is about to run out, and an upgrade alert says whether the new code is verified and which functions changed.

An alert when a wallet you name as an admin, deployer or signer sends any transaction.

Every alert kept with what triggered it, searchable, and ready to export as a file.

Slack, PagerDuty and your own signed webhooks, beside Telegram and Discord. Send each rule where it belongs by how urgent it is, send a test alert, and see who changed a rule. If our checks fall behind a network, we tell you.

Before a Safe signer approves a transaction, see what it really does, worked out independently of the wallet screen, and whether the destination only looks like an address you have paid before. We never hold a key.

An alert when a transaction is proposed to a Safe you watch and as each signature arrives, with what it really does, worked out independently of the wallet screen, and a warning when the destination only looks like an address you have paid before.

An alert when more than a share you choose leaves the contract in one block or one hour, when one payout passes a multiple of its stake, or when a token's supply grows faster than a limit you set.

Alerts on the hot, warm and cold wallets you name: the first payment to an address never seen before, every further payment to it, any payment out of a cold wallet, an outflow that stays just under your limits for days, and a wallet of yours that your hot wallet paid and you never listed.

If stablecoins are taken, a live list of each transfer, where it went and who issued the token, ready for your team to send to the issuer.

An alert when a proposal is created, queued or executed in your on-chain governor, and when one is posted to your Snapshot space.

An alert when a wallet you name lets a new spender move its tokens or allows an unlimited amount, and when a bot or treasury wallet falls below a balance you set.

An alert when a wallet or contract you watch pays, or is paid by, an address on the US Treasury's sanctions list (OFAC).

An alert when a price feed your contract reads stops updating, drifts from a second source or is scheduled to shut down, when a layer 2 network reports its sequencer down, when a stablecoin leaves its peg, when a bridge you rely on changes its verifiers or rests on a single one, and when a new market lists a token with almost no price history or liquidity.

Signs that often come before an attack: a new unverified contract that contains your address, a wallet funded through a mixer, bursts of failed calls, a new token that copies your name or symbol. Always labelled as a warning, never as confirmed.

An alert ahead of the date, and again as it nears, when a network, bridge, price feed or service your contracts depend on shuts down or changes its terms, from a list we keep and update.

Alerts on any event or function of any contract, with conditions you set, and your alerts through an API.

Bring the monitors you already have. Anything we cannot import is listed back to you.

A queued Safe transaction or timelock action run against the chain as it is now, to show what would change before it executes, and for an upgrade, whether the new code is verified and which functions change. Nothing you could sign comes from us.

An alert when your DNS records, domain registration or certificates change, when the script your site serves changes, when a new version of your npm package or a new GitHub release appears, when a dependency added to your repository was published only days ago, and when an admin, webhook, role or profile changes in your Telegram group, Discord server or X account.

Alerts by email, and a weekly summary of everything we saw.

For larger teams: an alert when a password, two-step verification or recovery setting changes on a Google Workspace, GitHub, 1Password or Cloudflare account you connect, read from logs you authorise us to read, and a higher severity when a signer acts on chain soon after.

An alert when a bot or keeper of yours stops checking in.

When an alert fires, a prepared pause, revoke or nonce-burn transaction your team can sign in its own Safe. We prepare it. We never hold a key and never send anything.

On an address you check: withdrawals an address started from a layer 2 network back to Ethereum and never finished, with the next step to finish them from your own wallet.

The same alerts for the Solana programs and wallets you run.

Alerts on Bitcoin and XRP Ledger addresses you name.

Every token approval each of your watched wallets has open, the risky ones flagged, with a link to revoke each in your own wallet.

An alert when a bridge's minted supply passes what is locked behind it, and when a Hyperlane route's security module changes or is weak.

For a token that can be minted, a suggested limit on how fast its supply may grow, which you can change or clear.

An alert when a new version of your npm package adds an install script, has very few downloads, or was published by someone new.

For signers who choose it: an alert when the phone number behind a signer's account was swapped or forwarded, and a higher severity when that signer then acts on chain.

An alert when a work email of a team member who opts in appears in a new breach or an infostealer log.

An alert when a wallet you watch looks drained by a stolen key, and when a watched contract sends out native coin.

An alert when a new certificate is issued for a domain that looks like yours.

A wallet that should never move, set up as a cold-wallet rule. Any movement is an alert. Only its public address is used.

A message on Telegram asking a signer to confirm "I proposed this" or "Not me" for a transaction proposed to your Safe. "Not me" only raises the alert.

Name the addresses your team uses, so alerts say who they are.