pull down to refresh

═══════════════════════════════════════
am-i.exposed - Bitcoin Privacy Report
═══════════════════════════════════════

Query: bc1qs2kcm45p83sq4mj0x09jl80kw7ewcue4vh9dqe
Grade: F (0/100)

─── Score Breakdown ───
Base score: 93
Address reused across 191 transactions: -92
High activity address (191 transactions): -5
Recurring payment pattern: 1 repeated counterparty: -5
High transaction volume (191 transactions): -3
Transacted with 30+ counterparties: -2
3 transactions within 2 hours: -2
Final score: 0/100

─── Findings (8) ───

🔴 [CRITICAL] Address reused across 191 transactions
This address appears in 191 transactions. Every transaction to and from this address is now trivially linkable by chain analysis. Address reuse is the single most damaging privacy practice in Bitcoin.
→ Use a wallet that generates a new address for every receive (HD wallets). Never share the same address twice. Send remaining funds to a new address using coin control. For stronger unlinking, use CoinJoin - but note that some exchanges may flag CoinJoin transactions.
Score impact: -92

🟠 [HIGH] High activity address (191 transactions)
This address has 191 transactions and has received funds 160 times. This level of activity suggests a service, merchant, or frequently-used deposit address. Multiple senders to this address can be linked to the same entity.
→ Addresses with high transaction counts are likely services or exchanges. Request a fresh address for each payment to avoid linking your transaction to other senders.
Score impact: -5

🟡 [MEDIUM] Recurring payment pattern: 1 repeated counterparty
This address has transacted with 1 counterparty more than once (most frequent: 2 times). Recurring payments to or from the same address reveal an ongoing financial relationship. A chain analyst can identify regular payment patterns (salary, subscriptions, rent) and use them to profile the address owner.
→ For recurring payments, use different addresses each time. BIP47 (PayNym) provides reusable payment codes that generate unique addresses per payment. For receiving, provide a fresh address for each invoice. Never reuse addresses for repeated transactions with the same counterparty.
Score impact: -5

🟡 [MEDIUM] High transaction volume (191 transactions)
This address has been involved in 191 transactions. High-volume addresses are more likely to be monitored by chain analysis firms and may be associated with services, exchanges, or businesses.
→ Use HD wallets to spread activity across many addresses. Avoid concentrating activity on a single address.
Score impact: -3

🟡 [MEDIUM] Transacted with 30+ counterparties
This address has sent or received funds involving 30+ different addresses. A large number of counterparties creates a wide exposure surface and makes the address easier to cluster with other known entities.
→ Use separate addresses for different transaction partners. HD wallets do this automatically.
Score impact: -2

🟡 [MEDIUM] 3 transactions within 2 hours
3 transactions were confirmed within a 2-hour window. This temporal clustering can help analysts correlate activity from this address with other on-chain behavior.
→ Consider spacing transactions over longer periods to reduce temporal correlation.
Score impact: -2

🔵 [LOW] Partial history analyzed (50 of 191 transactions)
This address has 191 total transactions but only the most recent 50 were analyzed. Older transactions may contain additional privacy-relevant patterns not reflected in these results.
→ For a complete analysis of high-activity addresses, consider running a full node with a local Electrum server.

🟢 [GOOD] Native SegWit address (P2WPKH)
P2WPKH (native SegWit) has the largest anonymity set of any address type, making single-sig transactions highly private. While it reveals the script type on spend, for single-sig this is not a privacy concern since the vast majority of P2WPKH users are single-sig.
→ P2WPKH has the largest anonymity set for single-sig transactions. No change needed.

─── Link ───
https://am-i.exposed/#addr=bc1qs2kcm45p83sq4mj0x09jl80kw7ewcue4vh9dqe

Scanned with am-i.exposed

I also re-use addresses 😱

reply

Don't ever do that after spending. Not even if you don't care about privacy.

You weaken the h of p2pkh/p2wpkh in doing so because on spend you reveal the pubkey to a hash.

Basically you can accumulate to an address (though it'd still be better not to, also to protect those that send you sats) but then once you spend, you must spend it all.

reply

I don't reuse addresses. I just picked this one at random on mempool to see what the report looked like.

reply
6 sats \ 0 replies \ @OT 18 Mar

Naughty naughty

reply