Security / Audit·EVM · Multi-chain
Harpie
Onchain firewall that monitors wallets in real time and intercepts theft before it lands. Pre-signature transaction validation plus an enrolled-vault layer that auto-recovers assets if a malicious tx slips through. Exposes a Background Check API for address/contract/transaction reputation backed by 2M+ known-malicious actors and active drainer contracts.
- 01pre-signature transaction validation
- 02address + contract reputation lookups
- 03wallet-level theft recovery (vault)
- 04discord/telegram link safety
- 05consumer wallet UX warnings
| Variable | Scope | Description |
|---|---|---|
| HARPIE_API_KEY | Server | Harpie Enterprise API key for the Background Check API, sent in the `Authorization: Bearer` header. |
Use Harpie before any signature and to surface wallet risk. Address check: `POST https://api.harpie.io/v2/validateAddress` with `Authorization: Bearer ${HARPIE_API_KEY}` and `{ address, chainId }` returns `{ isMaliciousAddress: boolean, isFlaggedByHarpie: boolean, attackTypes: [...], confidence }`. Transaction check (pre-signature): `POST /v2/validateTransaction` with `{ from, to, value, data, chainId }` returns `{ isFireblocksFlagged?, isMalicious, riskLevel, attackTypes: ['drainer'|'phishing'|'rug'|'wash-trade'|...] }`. URL/site reputation: `POST /v2/validateUrl` with `{ url }`. Wire the validateTransaction call into your wallet's tx confirmation step: block on `riskLevel === 'high'`, surface a confirmation modal with `attackTypes` listed on `medium`, and pass-through on `low`/`none`. For protected users, deep-link to `https://harpie.io/connect` so they can enroll the vault recovery layer.
- ⚑Harpie's enrolled-vault recovery is only available to users who explicitly opt in and approve the Harpie monitoring contract — the API alone does NOT recover funds; communicate the two-tier model (warn vs recover) clearly in your UX.
- ⚑Chain coverage on the consumer firewall is currently EVM-focused (Ethereum, Base, Arbitrum, Polygon and similar) — Solana / Bitcoin / Cosmos are not covered for the recovery flow; gate any recover CTA on supported chains.
- ⚑False positives on legitimate brand-new dApps and contract redeploys exist (cold-start) — provide an explicit 'proceed anyway' path with prominent warning copy rather than hard-blocking.
- ⚑Pre-signature validation latency is typically 100–400ms but can spike under high traffic; run it in parallel with rendering the confirm modal and fail-open on timeout for retail UX, fail-closed for treasury/multisig flows.
- ⚑API rate limits apply per-key — for high-volume wallets cache `(address,chainId)` lookups for 5–15 minutes and only call `validateTransaction` for fresh `to`+`data` combinations.
- ⚑Background-check confidence is heuristic — pair with a transaction simulator (Blowfish/Blockaid/Tenderly) for asset-diff visibility, since Harpie tells you 'is this party shady' but not 'what does this tx actually do'.