Why Device Fingerprinting Misses Sybil Farms
Why Device Fingerprinting Misses Sybil Farms

Why Device Fingerprinting Misses Sybil Farms

Yos Riady

Yos Riady

ยท Published

ยท Updated on

Updated

Updated

Key Takeaways

  • Device fingerprinting recognises a returning device. It fails against a sybil farm that gives each wallet its own device profile, which antidetect browsers make routine.

  • Chain analytics sees every wallet and transfer, but it does not know which wallets use your app or belong to one of your users.

  • Identity resolution joins the two views. It links wallets through shared identity and through a shared funding address, the account that sent each wallet its first gas.

  • In our platform data, one operator funded a batch of wallets within minutes and then ran each wallet from its own devices. Device and identity data saw unrelated users. The funding address linked them.

  • No signal is enough alone. The funding signal has its own blind spot: exchanges and bridges fund many unrelated wallets and must be removed first.

Device fingerprinting fails against sybil farms because a farm can change everything that a fingerprint measures. An operator who gives each wallet its own device profile and network looks like many unrelated users. What the operator cannot cheaply change is where each wallet got its first gas. Identity resolution for onchain apps uses that record, together with identity data from your app, to link the wallets.

This guide compares device fingerprinting, chain analytics, and identity resolution: what each one catches, what each one misses, and how to combine them.

What Is Device Fingerprinting?

Device fingerprinting identifies a browser or device from its attributes: operating system, browser version, screen size, fonts, language, time zone, and hardware details. Combined, these attributes are distinctive enough to recognise the same device on a later visit, also after cookies are cleared.

It is good at three things:

  • Recognising a returning device without a cookie.

  • Catching low-effort abuse, where one person opens ten accounts in one browser.

  • Spotting automation, such as headless browsers and emulators.

Most abuse is low-effort, so a fingerprint stops a large share of it cheaply. The problem is the rest.

What Is an Antidetect Browser?

An antidetect browser is a browser built to present a different, consistent fingerprint for each profile. Each profile has its own operating system, screen, fonts, time zone, and stored cookies, and each one can use a different proxy. To a fingerprinting tool, 50 profiles look like 50 separate people on 50 separate computers.

These tools are sold openly, and they have legitimate uses: agencies and marketplace sellers use them to manage many client accounts. They are also the standard tool for airdrop and points farming. A farmer opens one profile for each wallet, connects, completes the task, and closes it.

This is the core weakness. The fingerprint is not wrong. Each profile really does look like a different device. What fails is the assumption behind it: that one device means one person, and many devices mean many people.

Why Does Device Fingerprinting Miss Sybil Farms?

Three things combine against it in crypto.

  1. Profiles are cheap. An antidetect browser creates a new, clean device profile in seconds.

  2. Networks are cheap. Residential proxies give each profile an ordinary home connection, so network checks pass too.

  3. Accounts are free. In a crypto app the account is a wallet. Creating one needs no email, phone number, or card, so nothing else ties the accounts together.

In most software, the third point does not hold. A farm still needs an inbox or a phone number for each account, and those cost money. In crypto, the only thing an account needs before it can act is gas. That is the detail that matters, and we return to it below.

What Does Chain Analytics See, and What Does It Miss?

Chain analytics sees every wallet and every transfer on a public chain. It is strong at tracing funds and at flagging exposure to sanctioned addresses, scams, and mixers.

What it cannot see is your app. It does not know which wallets visited your site, which referral code they used, when they connected, or which of them belong to one of your users. It can tell you that a wallet is risky in general. It cannot tell you that twelve of the wallets in your campaign are one operator.

How Do the Three Approaches Compare?


Device fingerprinting

Chain analytics

Identity resolution

Looks at

The browser or device

Wallets and transfers on the chain

Your app's wallets, linked by identity and by funding

Answers

Is this the same device as before?

Is this wallet risky?

Which of my wallets belong to one person?

Catches

Many accounts on one device, bots

Risky counterparties, traced funds

Wallets that one operator controls

Misses

Farms with a profile for each wallet

Which wallets are your users

Wallets funded from unrelated sources

Weak point

Cheap to defeat

No view of your app

Exchanges and bridges must be removed

Identity resolution is the approach that asks the right question for a growth or product team. It does not judge one wallet. It groups your wallets by who probably controls them.

What Can a Sybil Farm Not Hide?

Every new wallet needs gas before it can do anything, and someone has to send it. That first transfer is public and cannot be changed afterwards. The account that sent it is the wallet's funding address.

An operator who prepares 50 wallets usually funds them from one place: one wallet, or one disperse contract call. Funding each of the 50 from a different and unrelated source is possible. It needs a separate funding path for every wallet on every chain, which costs far more than a new browser profile.

We saw this in our own platform data. One account funded a batch of wallets within a few minutes. Each wallet then became active in an app over several months, each from its own devices, with no device shared between any two wallets. Device data would have seen unrelated users, and so did identity data. The funding address linked all of them.

What Is the Blind Spot of Funding Data?

Funding data has a large blind spot of its own: services. When someone withdraws from an exchange to a new wallet, the exchange's hot wallet becomes the funding address. Bridges, relayers, and gas top-up services behave the same way. One such address funds thousands of unrelated people.

When we built funding clusters in Formo, about seven in ten of the funding addresses that had funded more than one wallet were exchanges, bridges, or other services. Among the addresses that had funded ten or more wallets, nearly all were. A method that skips this step reports groups of exchange customers as sybil farms.

Removing services takes more than a list of labels, because labels arrive late. We found an exchange hot wallet that was only a few weeks old and had no public label. Its "linked" wallets were spread across many devices and several countries. Its activity gave it away: no person sends that many transactions.

So the honest comparison is this. Device data is easy for a farm to defeat. Funding data is hard for a farm to defeat, but easy to misread. Each needs the other.

How Do the Signals Work Together?

Combine the signals by asking what each one confirms.

What you see

What it suggests

Shared device and shared funding address

The strongest link. Two independent signals agree

Shared device, different funding

Probably one user with several wallets, or a shared device

Shared funding address, different devices

An operator who separates devices, or a service that was not removed. Review it

Nothing shared

No link

The third row is where careful farms are, and it is the row that a device-only approach cannot see at all. It also needs a human review, because an unrecognised service lands there too. The funding window helps: wallets funded within minutes of each other point to one operator, and wallets funded months apart point to a service.

In our platform data, when the funding address is itself a wallet that uses the app, funding and identity agree in more than nine cases out of ten. When it is an outside address, agreement is much lower. That gap is not an error rate. It is the size of the group that only the funding signal can see.

Do You Need Device Fingerprinting at All?

Not necessarily. Formo does not fingerprint devices and does not store raw IP addresses. It links wallets through an anonymous ID in the browser, through the user ID that you set, and through the funding address onchain.

The reasoning is practical:

  • Cost to defeat. A fingerprint is the cheapest signal for a farm to change. The funding address is among the most expensive.

  • Privacy. A device fingerprint is personal data in many jurisdictions and is hard to explain to users. A funding address is public chain data.

  • Maintenance. Fingerprinting is an arms race with browser vendors and antidetect tools. Onchain history does not change.

If you already run a device tool, keep it. It stops the low-effort abuse that makes up most cases. Add identity resolution for the farms that it cannot see.

How to Link Wallets Without Device Fingerprinting in Formo

  • Cluster by identity or by funding address. On the Users page, open the Clusters tab and use Cluster by to switch between the two.

  • Read the confidence level. Each funding cluster shows High confidence or Needs review, with the reasons: whether the funding address is a wallet of your app, how many wallets also share an identity cluster, and the funding window.

  • Services are removed for you. Exchanges, bridges, relayers, and gas services do not form clusters. Formo recognises them from public labels and from their activity.

  • See every link and its reason. A wallet profile lists the linked wallets with an icon for each reason, and shows the funding address or the service that funded the wallet.

  • Export for review. Export clusters as CSV with the linked addresses, the reasons, the funding address, and the confidence level.

See identity resolution in the docs for the method and its limits, and sybil detection for onchain apps for every detection method compared.

Frequently Asked Questions

Why does device fingerprinting miss sybil farms?

Device fingerprinting identifies devices, and a sybil farm uses a separate device profile for each wallet. Antidetect browsers and residential proxies make this cheap. Every session then looks like a different user, and a wallet needs no email or phone number that could tie the accounts together.

What is an antidetect browser?

An antidetect browser presents a different, consistent device fingerprint for each profile, with its own operating system, screen, fonts, time zone, cookies, and proxy. Farmers use one profile per wallet, so a fingerprinting tool sees many separate devices.

Is device fingerprinting still worth running on a crypto app?

Yes, if you already run it. It stops low-effort abuse, such as many accounts in one browser, and it detects automation. It does not stop organised farms, so pair it with a signal that does not depend on the device.

What is identity resolution for wallets?

Identity resolution for wallets groups the wallets that one person or team probably controls. It links them through shared identity, such as the same device or user ID, and through a shared funding address, the account that sent each wallet its first gas.

Can VPN and proxy detection stop airdrop farming?

Only the low-effort kind. Residential proxies look like ordinary home connections, and many real users use a VPN. Network signals are useful as supporting evidence, not as the link between wallets.

Can a sybil farm hide its funding address?

It can fund each wallet from a different, unrelated source, for example a separate exchange account for each wallet. That costs time and money for every wallet. Most operators fund many wallets from one place, which is why the signal works.

Does a shared funding address prove that wallets belong to one person?

No. An exchange or a bridge funds many unrelated wallets, and one person can send gas to a friend. Remove services first, then treat a shared funding address as a reason to review.

Related reading

About the Author

About the Author
About the Author
Yos Riady

Founder

Founder

Yos is the founder of Formo, where he helps DeFi teams make analytics and attribution simple. Prior to Formo, Yos was a staff software engineer and tech lead at Chainlink Labs. He helped scale Chainlink into the industry-standard oracle for leading DeFi protocols. A long-time builder in crypto with experience across smart contracts, data engineering, and security.

Yos is the founder of Formo, where he helps DeFi teams make analytics and attribution simple. Prior to Formo, Yos was a staff software engineer and tech lead at Chainlink Labs. He helped scale Chainlink into the industry-standard oracle for leading DeFi protocols. A long-time builder in crypto with experience across smart contracts, data engineering, and security.

Table of Contents

Measure what matters onchain

Formo makes analytics and attribution simple for DeFi apps.

Measure what matters onchain

Formo makes analytics and attribution simple for DeFi apps.

Measure what matters onchain

Formo makes analytics and attribution simple for DeFi apps.

Stay up to date with weekly product updates and the latest industry insights.

Stay up to date with weekly product updates and the latest industry insights.

Stay up to date with weekly product updates and the latest industry insights.