# SnitchWallet

SnitchWallet is a bitcoin canary for your servers.

You plant a private key holding a small amount of real bitcoin on your server. If anyone steals the key and moves the coins, SnitchWallet alerts you, usually within seconds of the theft being broadcast, so you know the server has been breached. Bitcoin transactions are public, so the theft can't be hidden.

SnitchWallet is pre-launch. [Join the waitlist](https://snitchwallet.com/#waitlist) for early access. Early-access users are free.

Canonical page: https://snitchwallet.com/

## Install

```sh
curl -fsSL https://get.snitchwallet.com | sh
```

It prints a link. Approve the server in your browser and the canary is armed. Nothing keeps running on the server afterwards. Early-access users get it first.

## How it works

One line on the server, one click in your browser. After that, the blockchain does the watching.

1. **Run one line.** Run the installer on a Linux server. It prints a link. Linux servers come first.
2. **Approve it in your browser.** Open the link, approve the server and fund the bait, by card through a licensed on-ramp partner or from your own wallet. About $10–25 is typical. The canary is armed and the installer deletes itself.
3. **Hear about it when the bait is taken.** Whoever steals the key wants the coins. Moving them takes a public bitcoin transaction, and SnitchWallet alerts you, usually within seconds of it being broadcast.

What installing looks like (illustration):

```text
$ curl -fsSL https://get.snitchwallet.com | sh

To arm a canary on web-3, open this link and approve the server:

    https://snitchwallet.com/approve/…

Waiting for approval…
Canary armed. The installer has removed itself.
Nothing is left running on web-3.
```

What an alert looks like (example):

> **Canary fired on web-3**
>
> - **What happened:** Someone used the key planted on web-3 to move its bitcoin.
> - **Seen:** In the mempool, before the first confirmation.
> - **What it means:** Someone got into web-3 and read files they had no business reading. Treat the server as breached.

### Installing on a fleet

For cloud-init, Terraform, Ansible, Docker or Kubernetes, pass an auth key instead of clicking a link:

```sh
curl -fsSL https://get.snitchwallet.com | sh -s -- --authkey-file /run/secrets/authkey
```

Run it when each server first boots, not when you build the image, so every server gets its own canary.

## Nothing runs on your server

After install, the only thing left on the server is the bait. All the watching happens on our side, on the public blockchain.

- **No agent.** No daemon to update, crash or spot in the process list.
- **No open ports.** Nothing new listens on the network.
- **No outbound traffic.** The server never phones home after install.
- **No installer left behind.** It deletes itself once the canary is armed.
- **No off switch on the server.** Nothing on the server can silence an alert. Retiring a canary takes your admin login, from your own machine.

## Your keys, your coins

SnitchWallet is non-custodial. The bait is your bitcoin, and we can't move it.

- **We never hold your bitcoin.** Keys are created on your own machines. We only ever see addresses, or encrypted data we can't read.
- **Take it back any time.** Retire a canary from your own machine and the bait comes back to you. That works even if SnitchWallet shuts down: keys use standard formats that mainstream wallets such as Sparrow, Electrum and Bitcoin Core can import.
- **Fund it your way.** Pay by card through a licensed on-ramp partner, or send from your own wallet. Typical bait is about $10–25.
- **The one catch.** If an attacker takes the bait, it's gone. That's the price of the alert.

If we disappear, your money doesn't.

## Built for AI agents

Your agent can plant canaries. It can't dig them up.

### Let your agent install them

SnitchWallet works over MCP, so an AI agent can put canaries in place for you. You, to your agent:

> Put a SnitchWallet canary on every server.

Agents can add canaries but can never reveal or remove them. No tool tells an agent where a decoy is, so a prompt-injected agent can't give your canaries away.

### Plant canaries where agents can reach

AI agents hold secrets too. Put a canary where an agent can read it: environment variables, MCP configs, agent memory or RAG documents.

If a prompt-injected agent leaks its secrets, whoever ends up with the key sweeps the bitcoin, and you're alerted. No integration with any AI vendor is needed.

## Planned pricing

Early-access users are free. These prices are planned and may change before launch. The bait is your own bitcoin, not a fee, and you can take it back.

| Plan | Price | Canaries | Includes |
|---|---|---|---|
| Free | $0 | 3 | Email alerts |
| Pro | $29 per month | 25 | Slack, Discord and webhook alerts; mempool-speed alerts |
| Team | $199 per month | 250 | Everything in Pro; fleet controls; multiple users |
| Enterprise | Custom | Custom | For larger fleets, priced by agreement |

## Questions, answered

### What is a bitcoin canary?

A bitcoin canary is a private key holding a small amount of real bitcoin, planted where an attacker might find it, such as in a server's files or environment. Nobody legitimate should ever touch it. If the coins move, someone has taken the key, and because bitcoin transactions are public, the theft shows up on the blockchain. SnitchWallet plants and watches bitcoin canaries for you.

### How do I know if my server has been hacked?

Often you don't, until the damage shows, because a careful intruder cleans up after themselves. Unusual logins, processes, outbound connections and changed files are the usual signs, and logging and intrusion detection help you spot them. A canary adds a signal that's hard to erase: plant something an intruder will want, and get an alert when it's taken. With SnitchWallet the bait is a bitcoin key. If its coins move, someone had access to that server.

### Why use real bitcoin as bait?

Because attackers can cash it out, they have a reason to take it, and cashing out means making a public transaction. A fake credential only alerts you if the attacker tries it against something that reports back. A bitcoin key needs nobody to report anything, because the blockchain is public.

### Is there a Canarytokens alternative for crypto, or a bitcoin honeytoken?

Yes. SnitchWallet is a bitcoin honeytoken for servers. Canarytokens, by Thinkst, is free and open source, with many token types. At the time of writing (November 2026), to our knowledge it doesn't offer a bitcoin-wallet canary. The two work well together; see [SnitchWallet vs Canarytokens](https://snitchwallet.com/vs/canarytokens.md).

### Do you hold my bitcoin?

No. Keys are created on your own machines, and we only see addresses or encrypted data we can't read. You fund the bait yourself, by card through a licensed on-ramp partner or from your own wallet, and the coins never pass through us.

### What happens if SnitchWallet shuts down?

Your bait stays yours. Keys use standard formats, so you can import them into a mainstream wallet such as Sparrow, Electrum or Bitcoin Core and move the coins wherever you like. If we disappear, your money doesn't.

### How much bitcoin goes into a canary?

Typically about $10–25. That's enough to be worth stealing and little enough to lose. You can take it back at any time; only a theft costs you the bait.

### Does anything keep running on my server?

No. The installer plants the decoy, arms the canary and deletes itself. There's no agent, no open port and no outbound traffic. All monitoring happens on our side, on the public blockchain. SnitchWallet supports Linux servers first.

### Can AI agents install it?

Yes. Through MCP, an AI agent can install canaries for you, for example when you ask it to "Put a SnitchWallet canary on every server." Agents can add canaries but can never reveal or remove them, so a prompt-injected agent can't expose or switch off your canaries.

### Can SnitchWallet protect AI agents?

Yes. Plant a canary where an agent can reach it: environment variables, MCP configs, agent memory or RAG documents. If a prompt-injected agent leaks its secrets, whoever ends up with the key sweeps the bitcoin, and you're alerted.

### What does SnitchWallet cost?

Early-access users are free. Planned pricing after launch: Free, with 3 canaries and email alerts; Pro, $29 per month, with 25 canaries, Slack, Discord and webhook alerts, and mempool-speed alerts; Team, $199 per month, with 250 canaries, fleet controls and multiple users; and Enterprise, priced by agreement. The bait is your own bitcoin, typically about $10–25 per canary, and you can take it back.

### What does a bitcoin canary not catch?

A canary only fires when someone takes the key and moves the coins. An intruder who never looks at the decoy won't trip it, and a sophisticated attacker may recognise the bait or simply ignore it. SnitchWallet doesn't block attacks, find vulnerabilities or replace patching, logging and endpoint security. Treat it as one layer: a cheap, loud tripwire for the thefts it does catch.

### When can I use SnitchWallet?

SnitchWallet is pre-launch. [Join the waitlist](https://snitchwallet.com/#waitlist) and we'll email you when early access opens. Early-access users are free.

## Get a snitch on the inside

When someone breaks in, you want to be the first to know. [Join the waitlist](https://snitchwallet.com/#waitlist) for early access. Early-access users are free.

We keep your email address and your answer. Not your IP address.

---

© 2026 SnitchWallet. Pre-launch: features and prices may change. More: [SnitchWallet vs Canarytokens](https://snitchwallet.com/vs/canarytokens.md), [llms.txt](https://snitchwallet.com/llms.txt).
