Qualify for the Lombard airdrop in 2026 without getting sybil-flagged
Qualify for the Lombard airdrop in 2026 without getting sybil-flagged
Lombard is one of the more interesting protocols to watch in 2026. It wraps Bitcoin into LBTC, a liquid staking token backed by Babylon’s Bitcoin staking layer, and it has been distributing “Bera Points” and other engagement signals that protocols typically use to determine retroactive allocations. There is no confirmed token yet, but the on-chain activity requirements are real, the point system is live, and the sybil-detection infrastructure is clearly being built. Farming it now, carefully, is the rational move.
The problem is that BTC-native farming attracts a specific kind of operator who either runs too many wallets too sloppily or treats LBTC like a passive hold-and-forget position. Both approaches leave points on the table. The sybil risk is real too. Protocols that touch Babylon’s staking layer have access to a lot of behavioral data, and Lombard’s team has been explicit about wanting “genuine” liquidity rather than wash activity.
This guide is for operators who already have BTC, understand basic EVM and BTC wallet hygiene, and want a structured approach to building a credible, un-flagged position. i’ll cover what to set up, how to actually interact with the protocol in a way that looks organic, and where the edge cases will bite you.
what you need
- BTC on mainnet, minimum 0.01 BTC per wallet to keep fees proportional. More is better. Below 0.005 BTC the gas-to-position ratio gets ugly fast.
- A hardware wallet or cold wallet per identity , Ledger, Trezor, or Keystone. Do not reuse a wallet address across identities.
- An EVM wallet (MetaMask or Rabby) for each identity. Rabby is better for this because it shows per-chain gas estimates and approval risk.
- Ethereum mainnet ETH for gas , bridge interactions and LP positions on LBTC pairs cost real gas. Budget $15-40 per wallet for a full setup cycle.
- An antidetect browser if you are running more than one identity. Multilogin or AdsPower both work. For a comparison of current options and pricing see antidetectreview.org/blog/ before you commit to a subscription.
- Residential proxies, one IP per identity. Datacenter IPs are fine for many protocols but Lombard’s web app fingerprints are aggressive. Rotating residential proxies are adequate for single-session use.
- A Babylon-compatible wallet , OKX Wallet currently has the best native BTC staking UX for Babylon integrations, though Unisat also works.
- Access to app.lombard.finance , no VPN from sanctioned jurisdictions. The app does geo-screening.
step by step
step 1: set up your identity stack cleanly
Before touching the Lombard app, get your wallet architecture right. Each identity needs: one antidetect browser profile, one residential proxy IP, one BTC wallet (derivation path that doesn’t share xpub with other identities), and one EVM address. Generate BTC wallets from separate seed phrases, not from the same 24-word root with different derivation indices. On-chain clustering analysis catches that pattern trivially.
If it breaks: if you already have addresses derived from the same seed, move funds to a freshly-generated seed before interacting with Lombard. Do not try to obscure this by routing through a mixer. That creates more flags, not fewer.
step 2: stake BTC into Babylon to receive LBTC
Go to app.lombard.finance and connect your BTC wallet. The minting flow asks you to stake BTC on Babylon’s layer, which locks it for a minimum staking period (currently 10 Bitcoin blocks for activation, then the Babylon unbonding queue applies). You receive LBTC on Ethereum at a 1:1 ratio minus the bridge fee, currently around 0.06%.
# check current Babylon unbonding queue time before committing
# Babylon dashboard: https://babylonlabs.io/
# typical unbonding: 7-21 days depending on queue depth
Expected output: LBTC appears in your EVM wallet within 2-6 hours of BTC confirmation. The Lombard app shows a “minting” status.
If it breaks: if LBTC doesn’t arrive after 12 hours, check the Lombard docs bridge status page. Sometimes relayer congestion delays the mint. Do not re-submit the transaction.
step 3: deploy LBTC into active DeFi positions
This is the most important step for point accrual. Holding LBTC in a wallet accrues base points. Deploying it into supported protocols accrues multipliers. Current high-multiplier integrations include:
- Curve Finance LBTC/WBTC pool
- Pendle Finance LBTC yield markets
- Morpho Blue LBTC lending markets
Interact with at least two of these per wallet. Splitting across protocols looks more organic than concentrating in one pool.
# Curve pool interaction (example via CLI with cast, for automation)
cast send <curve_pool_address> \
"add_liquidity(uint256[2],uint256)" \
"[<lbtc_amount>,0]" \
"<min_lp_out>" \
--rpc-url <your_rpc> \
--private-key <wallet_key>
Expected output: LP tokens in your wallet, points counter on Lombard dashboard increases.
If it breaks: Pendle markets have expiry dates. Check that the market you’re entering has at least 60 days to expiry before depositing, or your position will auto-exit at a potentially bad price.
step 4: use the Lombard referral system correctly
Lombard has a referral code system. Using a referral code when you first connect gives both the referrer and referee a points bonus. If you have multiple wallets, do not use the same referral code across all of them. That is a clustering signal. Either source codes from different community members on the Lombard Discord, or use each wallet’s own referral link for subsequent wallets in your set (with delays between each signup).
If it breaks: referral bonuses are applied retroactively based on first connection timestamp. If you forgot to enter a code, you cannot add one later.
step 5: maintain consistent transaction cadence
Airdrop eligibility snapshots are rarely a single point-in-time. Most protocols look at activity distribution over time. Set a recurring schedule: once or twice per week, do something with each wallet. Add a small amount to a pool, claim pending rewards, adjust a position. The action matters less than the cadence.
A simple cron approach if you’re running more than five wallets:
# example: weekly LBTC reward claim across wallets
# store wallet keys in a secrets manager, not plaintext
for wallet in wallets.txt; do
cast send <morpho_address> "claimRewards(address)" $wallet \
--rpc-url $ETH_RPC \
--private-key $(get_key $wallet)
sleep $((RANDOM % 7200 + 3600)) # 1-3 hour random delay between wallets
done
The random sleep between wallets is not optional. Uniform transaction timing across a wallet cluster is one of the most common sybil flags. See our guide to automating airdrop farming safely for more on cadence strategies.
If it breaks: if a wallet’s gas is too low for the claim transaction, the script will error. Pre-fund each wallet with at least 0.005 ETH buffer before running.
step 6: verify your points dashboard regularly
Check app.lombard.finance weekly. The dashboard shows total points, breakdown by activity type, and any multipliers currently active. If your points stop accruing unexpectedly, it can mean your wallet was flagged, a multiplier period ended, or your LP position was exited (e.g., Pendle expiry or Curve pool migration).
If it breaks: if you see zero points on a wallet that was active, raise a support ticket in the Lombard Discord before doing anything else. Sometimes it’s a display bug, not a ban.
step 7: document your position for snapshot proof
When an airdrop snapshot date is announced, you want to be able to prove your position was genuine. Keep records: transaction hashes, LP positions, timestamps. A simple local log is fine.
# snapshot your current positions
echo "$(date) - wallet: $ADDRESS - LBTC balance: $(cast call <lbtc> 'balanceOf(address)' $ADDRESS)" >> positions_log.txt
Expected output: a text log you can reference if you need to dispute a sybil flag in the claims process.
common pitfalls
running too many wallets on one IP. even with proxies, if you have session overlap, browser fingerprint overlap, or re-use cookies across profiles, clustering algorithms will find you. one IP, one browser profile, one wallet set.
unstaking BTC before the Babylon queue clears. Babylon unbonding is not instant. operators who try to pull capital quickly during a market move lose their staked position in a messy state. check the unbonding queue depth before entering.
ignoring gas on small positions. if your LBTC position is worth $300 and you’re spending $25 in gas per interaction cycle, you’re farming yourself into a loss. the minimum viable position per wallet at current gas rates is around $800-1,200 of LBTC.
using the same on-chain interaction patterns across wallets. if wallet A and wallet B both do the exact same sequence (mint LBTC, add to Curve, claim, remove from Curve) within the same hour, that’s a cluster signal. vary the sequence and timing.
not reading the Lombard eligibility criteria when they publish them. Lombard has not published final airdrop rules as of this writing. when they do, some activity types may be excluded or weighted lower. staying in the official Lombard documentation is mandatory, not optional.
scaling this
10 wallets: manageable manually with an antidetect browser and a spreadsheet to track positions. the main cost is time, roughly 2-3 hours per week across the set.
100 wallets: you need scripted interaction (see step 5), a secrets manager for private keys (HashiCorp Vault or AWS Secrets Manager, not a text file), and a proxy rotation setup with at least 100 clean residential IPs. the Lombard app’s web frontend becomes a bottleneck at this scale. move to direct contract calls. multiaccountops.com/blog/ has good writeups on infrastructure for this tier.
1000 wallets: this is institutional-scale farming. at this point you need dedicated RPC nodes (not shared endpoints like the free Alchemy tier, which rate-limits aggressively), a monitoring layer to detect flagged wallets early, and a legal review of your jurisdiction’s treatment of airdrop income. this is not legal advice. consult a tax professional familiar with crypto in your jurisdiction.
at every scale: the sybil risk scales with cluster size. larger clusters need more behavioral variation, not less. the temptation to use cookie-cutter scripts across all wallets is exactly what detection systems are tuned for.
where to go next
- How to stake BTC on Babylon and maximize your points before the next snapshot
- LBTC DeFi integrations ranked by points-per-dollar in 2026
- Return to the airdrop farming article index for more protocol guides
Written by Xavier Fok
disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-05-19.