BerachainBERA
Berachain airdropped 15.75% of BERA to testnet users, grant recipients, Boyco depositors, social contributors and NFT holders after its February 2025 launch.
- Own L1
Testnets let teams try things before real money is at stake. Only some pay users for the effort. This is the map; the how-to lives in our guide.
Berachain airdropped 15.75% of BERA to testnet users, grant recipients, Boyco depositors, social contributors and NFT holders after its February 2025 launch.
No campaign is currently tagged as a testnet airdrop in our tracker.
At our last verification, exactly one tracked campaign carries the testnet tag: Berachain, and its distribution is finished. That is not a gap in coverage. It reflects how rare it is for a project to publish a testnet reward rule that we can read in its own documents.
Plenty of testnet campaigns are announced through social posts, quest platforms or points dashboards. If a rule is not in an official document we can open, we do not list it as documented. The verification method explains the standard. For campaigns that are still unannounced, see potential airdrops.
Ethereum.org defines testnets as public networks where developers and stakers test before anything reaches mainnet, and says testnet ETH is meant to have no real-world value; most people get it free from faucets. Three practical consequences follow.
The attraction of testnets is that cost looks like zero. The catch is that when everything is free, a project has little to distinguish real testers from scripts, so any reward rule has to use something other than raw volume.
The ratings below are our editorial judgement, not data from any project. They exist to help you decide where your hours go.
| Task type | Time | Direct cost | Main risk | Signal to a project |
|---|---|---|---|---|
| Bridging test assets | Low | None to minimal | Fake faucet or bridge sites | Weak; trivial to repeat |
| Swaps and liquidity | Low to medium | None to minimal | Malicious approvals | Weak to moderate |
| Minting, delegating, vault actions | Medium | None to minimal | Phishing front-ends | Moderate if varied |
| Deploying contracts | High | Skill; some tooling | Leaked keys in code | Strong |
| Bug reports | High | Skill | Report ignored or unpaid | Strong |
| Running a node | Very high | Hardware and hosting | Sunk cost if the network resets | Strong |
Notice the inverse relationship between how easy a task is and how much a project learns from it. That drives most of what follows.
The official airdrop overview (which our tracker cites; we could not re-open it during this review because of rate limiting) splits a 15.75 percent airdrop into categories. Testnet users received 8,250,000 BERA, 1.65 percent of supply, based on interactions with native and ecosystem apps across the Artio and bArtio testnets. Compare that with the other categories on the Berachain page:
Our reading: testnet was one of several routes and not the largest. The tracker also records that the overview did not describe an explicit Sybil-detection method for the testnet allocation, so we make no claim about one. Official documentation lists vesting for airdropped tokens as a one-year cliff, one sixth unlocked after it, then 24 months linear. The checker named in the overview, checker.berachain.com, could not be reached during our check, so we cannot confirm whether any category is still claimable.
Our Monad page records the opposite finding. The official results post does not list testnet usage as a criterion; the tracks it describes rest on onchain history, community nomination, builder participation and public-goods contribution. Whatever happened on the test network, the published rules did not turn it into a stated route to a reward.
Not every project fits either bucket. MegaETH split its community allocation across several routes and reserved 53 percent of supply for KPI-based rewards tied to milestones. Our data does not describe a testnet-activity airdrop there. Hyperliquid's official pages we opened say nothing about testnet tasks. Silence is information too: it means you should not assume a reward exists.
Putting numbers on the Berachain case helps calibrate expectations. The categories above add up to a 15.75 percent airdrop, and the testnet users’ 8,250,000 BERA is a little more than a tenth of that pool. It is also smaller than the NFT category (34,500,000 BERA), the grants category (11,730,000 BERA) and the Boyco deposits (10,000,000 BERA). This is our arithmetic from the official figures and should be read as a rough ratio, not a statement about any wallet’s payout.
Two other features of the case matter more than the ratio. The reward was retroactive: testnet users qualified months before any token existed, on the strength of interactions such as minting HONEY, delegating BGT or posting reward vault incentives, according to our tracker. And the distribution mixed very different kinds of participation. Someone who only ran testnet transactions was one of several groups sharing a pool, alongside builders, depositors, community members and NFT holders.
For planning, the useful lesson is about proportion. Even in the one documented case where testnet work was rewarded, it was one route among five and not the biggest. If you treat testing as a reason to use an early network, with a reward as a possible bonus, the Berachain numbers are consistent with that stance. If you treat testnet farming as a full-time job, they are not. Where a project has published nothing about testnet rewards, as Monad’s results post and the Hyperliquid pages we opened did not, the default assumption should be that no reward is coming.
Before you spend a weekend on a testnet campaign, run it through the questions below. They take ten minutes and filter out most of the noise. This is our editorial process, shaped by the gaps we keep meeting when we try to document these campaigns.
The hidden costs are rarely the transactions. They are the hours, the attention spent on a wallet you now have to keep tidy, and the temptation to treat a points counter as an income stream. Berachain's testnet users did receive an allocation, but it was 1.65 percent of supply set beside categories that required capital, grants or an NFT. That should shape how much of your week you hand over.
Put the two documented cases side by side and a sober picture emerges. In one, a testnet user category received a defined slice of supply. In the other, the published tracks did not mention testnet usage at all. Two data points are not a statistical rule, and we do not claim one. What they do show is that the question to ask about any campaign is not "is there a testnet?" but "has the project written down that testnet use is a criterion?" Until it has, any plan built on a reward is a plan built on a guess.
It also helps to separate learning value from reward value. Spending an evening on a testnet teaches you how bridges, approvals and signatures work in a setting where mistakes are cheap. That skill carries over to safer mainnet use whether or not a token ever appears.
This is informational, not financial advice. Scams ride on testnet hype too, so read crypto airdrop scams before connecting anything.
Yes, but they are the exception rather than the rule. Berachain, tracked on this site, allocated 8,250,000 BERA to testnet users based on interactions across its Artio and bArtio testnets. Other projects, such as Monad, documented that testnet usage alone was not a stated route to an allocation. Testnet activity is only sometimes rewarded.
By design, no. Ethereum.org describes testnet ETH as meant to have no real-world value, and most people get it free from faucets. Any reward comes later from the project itself, if it chooses to give one. A testnet balance is never a claim on a future token.
It carries the same phishing and approval risks as mainnet, because the wallet and browser are the same. Use a separate burner wallet with no real funds, confirm the app link from the official documentation, and never share a seed phrase. Faucet sites are a common lure, so use faucets named in official docs.
Documented cases cover interacting with native and ecosystem apps, bridging, minting, delegating and similar contract calls. Bug reports and running nodes are other common categories, though the rewards for them are set case by case. No project we track publishes a guarantee that a task will be rewarded.
The step-by-step walk-through, covering wallet setup, faucets and task routines, lives in our testnet airdrop guide. This page is the landscape view: which testnet campaigns are tracked, what categories of tasks exist, and what has been rewarded in documented cases.