Browser Fingerprinting: Why Crypto Users Need Protection

Saw a post on Reddit a while back. Guy was confused why his airdrop allocation got slashed. He'd done everything right. 12 wallets, different VPNs, funded through different sources, different emails for exchanges. By every metric people talk about, he should've looked like 12 different people.

Got flagged anyway.

The reason was browser fingerprinting. All 12 wallets connected through the same Chrome install on his laptop. The on-chain data looked fine. The off-chain data told a different story: one browser hitting 12 different addresses over a few weeks.

This happens more than people realize.

What your browser tells websites

So every time you visit a website, your browser leaks information. This isn't a bug or hack. It's how the web works. Sites need to know your screen size to render properly, your timezone for local time, your language for content.

Problem is all these small pieces add up to something unique.

Your screen resolution isn't just "1920x1080." It's 1920x1080 at 125% scaling with 24-bit color on this specific display configuration. Your graphics card shows up through WebGL. Your audio processing has measurable characteristics. The fonts installed on your system create a detectable signature.

Each piece is boring alone. Combined, they form a fingerprint that can be 99%+ unique across all browsers on the internet.

I didn't believe this until I tested it. Went to one of those fingerprint testing sites with my normal browser. Then with Firefox. Then with Chrome on my phone. Three completely different fingerprints. Same person, same network, looked like three different humans to any tracking system.

The canvas thing

This one blew my mind when I first learned about it.

Websites can ask your browser to draw something. A bit of text, some colors, a shape. Every browser renders this slightly differently because of:

• How your OS handles fonts
• Quirks in your GPU
• Anti-aliasing implementation
• Color management

Site converts the rendered image to a hash. Your hash is different from mine even with identical computer models. Tiny differences in hardware and software create unique outputs.

This is why the "just use a VPN" advice misses the point completely. Change your IP all day. Canvas fingerprint stays the same.

Why normal privacy stuff doesn't help

Let me just address these directly since I see them come up constantly:

Incognito mode does nothing for fingerprinting. It stops local history storage. To the website you look identical to normal browsing.

VPNs change your IP. That's it. Browser still reports same screen, same fonts, same GPU, same everything else.

Clearing cookies is literally what fingerprinting was designed to defeat. The whole point is tracking people who clear cookies.

Multiple Chrome profiles share the same browser engine. They report identical fingerprints because they run on the same hardware with the same software.

People suggest "just use Firefox" or Brave. Better than nothing. But if you're using multiple wallets from the same Firefox install, they're linked by the same fingerprint. Browser choice isn't the issue.

How this actually gets used

For airdrop filtering and Sybil detection, projects typically check two things:

On-chain patterns. Funding sources, timing, protocol usage. What most people think about.

Off-chain signals. Browser fingerprints, IP addresses, device characteristics. What catches people who were careful on-chain.

The combination is powerful. Your wallets can look completely independent on-chain, but accessing them from the same browser creates linkage. Detection sees: "Wallets A through E all interacted with our dApp from fingerprint X."

You never explicitly shared your fingerprint. It got collected passively just from visiting their site.

What antidetect browsers actually do

Good antidetect doesn't just "block" fingerprinting. A browser that refuses to answer fingerprint queries is itself suspicious. Sites know about fingerprint blockers.

Instead, antidetect gives different answers for each profile.

Profile A reports:

• Screen: 1920x1080
• GPU: Intel UHD Graphics 630
• Timezone: America/New_York
• Language: en-US
• Some specific font list

Profile B reports:

• Screen: 1440x900
• GPU: AMD Radeon RX 580
• Timezone: Europe/London
• Language: en-GB
• Different fonts

To a website these look like different computers. Because from the fingerprint perspective, they are.

The consistency problem

I've tested a bunch of antidetect tools over the years. Most fail on consistency.

They'll spoof the user agent to say macOS but report Windows fonts. Claim 4K resolution with a GPU that doesn't support 4K. Tokyo timezone with Spanish language settings.

Detection systems check for inconsistencies. If your browser says macOS but your font list is clearly Windows, you're flagged as using antidetect. Which might be worse than just having matching fingerprints.

Getting consistency right is tedious. Dozens of parameters need to tell a coherent story about a computer that could actually exist. Miss one detail and the whole thing falls apart.

WebRTC, the thing nobody remembers

WebRTC powers video calls in your browser. It's designed for peer-to-peer connections so it needs network info.

Here's the problem: WebRTC can leak your real IP even through a VPN.

It can also leak your local IP. The 192.168.x.x that identifies where you are on your home network. Another unique identifier that correlates browser sessions.

I've seen people do everything right with fingerprint spoofing then leak their real IP through WebRTC. Check the browser console on some fingerprint test sites. You might be surprised.

What we built into Raven

When we designed browser profiles, fingerprint protection wasn't optional. It's part of every profile.

Each profile gets its own fingerprint config. Screen, GPU, timezone, language, fonts. All matched to create a consistent identity. Canvas and WebGL get profile-specific noise that produces unique but stable outputs. (Stable matters because random noise on every page load is itself detectable.)

WebRTC is handled automatically. Either uses your proxy IP or gets disabled, depending on settings. No leaks.

Goal isn't just "different fingerprints." It's fingerprints that look normal. Detection should see your profile and think it's a regular Chrome user on a regular Windows laptop. Not "obviously someone using antidetect."

Test your setup

Before trusting any antidetect solution (including ours), test it.

Go to fingerprint testing sites with two different profiles. Results should be completely different. If you see any identical values, same canvas hash or same WebGL renderer, something's broken.

Check WebRTC specifically. Search for WebRTC leak test. If your real IP shows up anywhere, fix it before doing anything else.

Compare to a normal browser. Your antidetect profile should look as normal as a regular Chrome install. Just with different parameters.

Point isn't to be invisible. It's to look like a different normal person for each wallet identity.

---

Fingerprinting isn't going away. It's too useful for fraud prevention and advertising. The best you can do is understand it and use tools that give each identity a distinct, believable fingerprint.

Or keep using one browser for all your wallets. I'm sure that'll work out fine.

Related: Why we chose local storage over cloud sync. The security tradeoffs of where your wallet data lives.