Use casesdApps, token launches, airdrops and NFT projects
Keep airdrops and mints for real people
HEIP tells your server whether a person is in control when a wallet claims, mints or joins a sale in your app. Your app decides what happens.
Request
Airdrop claimed
By a wallet connected a minute ago
One operator, a thousand wallets, every claim.
Wallets are free to create and scripts can drive hundreds at once. Airdrops, allowlists and mints end up with whoever runs the most automation, not with your community. HEIP checks the claim itself, at the moment it's made.
Why now
500 scripted wallets × 2,000 tokens per claim = 1,000,000 tokens to one operator.
What you get
- Airdrops and rewards that reach people
- Because HEIP checkswhether a person was in control when the claim was made
- Fairer mints and token sales
- Because HEIP checkseach mint or purchase made in your web app, with its own policy
- Claims that can't be replayed
- Because HEIP checksthat the action token was issued for this claim, in this session, and used once
- No identity checks to filter scripts
- Because HEIP checkswithout names, documents or wallet ownership data
Actions to protect
| Action | Suggested policy | On step up, you usually |
|---|---|---|
| Airdrop or reward claim | Critical | Hold for review, or ask the wallet to sign again |
| Mint or token sale purchase | Fast | Ask to confirm again |
| Joining an allowlist or quest | Standard | Verify email or a social account |
| Faucet request | Standard | Ask to try again later |
| Browsing the app | Observe | Nothing: observe only, never blocks |
Policies are named presets you set per action. Critical asks for the most evidence. Fast suits frequent actions that still matter. Standard fits everyday actions. Observe never blocks.
Where it fits
HEIP checks actions taken in your web app. It never sees keys or seed phrases, and it doesn't analyse on-chain activity.
Works alongside
- Wallet connect and sign-in
- Allowlists and quests
- Sybil and on-chain analysis
- Your contract's claim limits
Roll it out on airdrop claims
Baseline
Pick airdrop claims. Note how they're protected today.
Observe
HEIP decides on real traffic but blocks no one.
Compare
Review its decisions against what you already know.
Enforce
Turn it on for airdrop claims only if it earns it.
Most teams go from observe to enforce in 6 to 8 weeks. Observe mode blocks no one while you compare. How onboarding works
Questions
Does HEIP touch wallets or private keys?
No. HEIP runs in your web app and returns a decision to your server. It never sees keys, seed phrases or signatures.
Does it stop claims made directly on-chain?
No. HEIP protects actions taken in a browser. Pair it with limits in your contract for calls that skip your app.
Does it replace sybil analysis?
No. Sybil tools look at wallets and their history. HEIP checks whether a person was in control of the claim itself. They answer different questions.
Can we run it on our next drop without blocking anyone?
Yes. In observe mode HEIP records what it would have decided and changes nothing for your users.
Trust has to move with the action.
When digital actions can be automated, trust must move with them.