BTC Medusa scans every coin in your wallet against 17 privacy heuristics, including address reuse, change leaks, exchange links and transaction entropy, then shows you exactly how exposed you are. The scan runs blind: we never learn which coins you hold, what you ask, or who you are. No node required.
Bitcoin is public and permanent. Every payment leaves a trail. Surveillance firms use that trail to cluster your addresses, identify your change outputs, and connect your coins back to the exchanges that touched them. Most people have no idea how much of their financial history is already exposed.
The single biggest privacy killer. Every reuse merges your activity into one identity.
Spending two coins together tells the world they belong to the same person.
Address-type mismatches and round amounts quietly reveal which output is your change.
Coins are flagged when their ancestry links to an exchange, a sanctioned entity, or a darknet market.
Boltzmann analysis measures how many interpretations of a transaction actually exist.
Version flags, input ordering and signature quirks can identify the software you use.
BTC Medusa runs the same battle-tested privacy heuristics that the open-source community has refined over years against your UTXOs, and returns a plain 0–100 score, a letter grade, and a list of exactly what's leaking, and how to fix it.
Three of your receive addresses appear in more than one transaction, collapsing them into one cluster.
A change output traces two hops back to a deposit address at a major exchange.
The deterministic link between inputs and outputs is unambiguous. Entropy ≈ 0 bits.
A round-number output makes the payment-vs-change split obvious to any observer.
Every UTXO is run through the same set of checks, grouped by how much they give away, from deterministic leaks that collapse your privacy outright down to subtle wallet fingerprints. Each finding comes with a plain explanation and a fix.
Change returned to an address that was also an input, merging your activity into one identity.
The input → output link is unambiguous, so the observer knows exactly which output is yours.
Tainted coins merged into the ancestry, dragging their history onto your funds.
Multiple inputs spent together reveal that one entity controls them all.
A consecutive single-hop payment chain, a classic signature of one wallet spending down.
Fan-in, fan-out and cross-wallet merging that ties separate stashes together.
Script structure that exposes a multi-party or escrow arrangement.
Ancestry that links to a sanctioned entity, a serious compliance exposure.
History that touches a known darknet market, a strong deanonymization vector.
Coins that trace back to a known exchange or service, often a KYC chokepoint.
Flagged dust used to bait you into co-spending and revealing your wallet.
Low, zero, or zero-sweep entropy (Boltzmann-style) where only one interpretation exists.
Arbitrary data attached to the transaction that can carry identifying breadcrumbs.
Uneconomical outputs that linger and quietly link future spends together.
nSequence flags that reveal fee-bumping behavior and narrow down your software.
nLockTime = 0 plus a legacy transaction version that shrinks the set of wallets you could be using.
All output amounts unique, with no equal-value ambiguity to hide behind.
The open-source engine is brilliant, but using it privately meant making a hard choice: leak every address you look up to a third-party API, or run a full node and self-host the stack. Most people can't, or won't, do that. BTC Medusa removes that requirement.
We take the open-source heuristic data, encrypt it, and pack it into the block filters your wallet downloads. You get the full privacy analysis without ever broadcasting what you're looking at.
We don't ask you to trust our server. We designed the whole protocol around the strongest possible assumption: that the operator, us, is actively hostile, colluding, and trying to deanonymize you. Under that assumption, here's what an attacker is up against.
Full control of our own software, database and network, and it still can't see your coins or your queries.
ISPs and state actors watching the wire see Tor traffic: no IP, no payload, no link to you.
Even if we hand everything to an exchange or chain-analysis firm, there's nothing in our logs to hand over.
A growing anonymity set plus per-request Tor circuits leave only a guess that decays as the user base grows.
You want to ask one question: "How exposed is this coin?" without anyone, including us, seeing what you asked. Your wallet blinds the query before sending it. We answer the blinded version without being able to read the original. Your wallet then unblinds the result and shows you the answer.
α = k · H(input), which looks like pure noise.k and reads the answer. We never saw the question.β = v · α, without ever learning your input.DLEQ proof that proves we used the real key and didn't cheat.f(x) without ever seeing x, and proves it did so honestly.
After the blinding, the zero-knowledge proofs and the Tor transport, our entire view of you reduces to this. Almost every meaningful fact is simply never knowable to us.
| About you | Can we see it? | Why not |
|---|---|---|
| Which coin you're scanning | No | blinded before it ever leaves your device |
| What the result says | No | unblinded only inside your wallet |
| How many coins you hold | No | tokens are spent without a counter we can read |
| Your IP address | No | Tor hidden service, traffic never exits the network |
| Your identity | No | no accounts, no email, no sign-up |
| Whether two scans came from you | No | each request is cryptographically unlinkable |
| That some valid scan happened | Yes | by design, it's all we need to keep the system running |
Every cryptographic primitive, every circuit constraint, every protocol flow is open and auditable. You don't have to take our word that we can't see your data. You can read exactly why we can't.
Our launch release runs as a plugin for Sparrow Wallet on desktop. We choose Sparrow since it's one of the most popular and robust desktop wallets around. However, it has not been endorsed by its creator. In the future, we hope to have all wallets, including Sparrow, bundle our plugin natively, since a percentage of every subscription will go straight to the open-source development team.
Send us a message below. We're happy to walk through the cryptography, the threat model, or wallet integration, and your note reaches both of us directly.