FarmDash Glossary: DeFi Airdrop and Agent Terms

Glossary Terms & Definitions

Sybil (Core Concepts)

A Sybil pattern is evidence that multiple accounts may be controlled or coordinated by one operator. FarmDash surfaces clustering indicators defensively; the score is not proof of abuse, a guarantee of eligibility, or guidance for evading protocol controls.

Pioneer Pace™ (Metrics)

FarmDash's cross-ecosystem normalization layer for otherwise incompatible protocol activity. The current model uses maintained multiplier inputs to support comparison; it is not a token-price model or expected-airdrop valuation.

Trail Heat™ (Metrics)

A 0-100 quantitative research-prioritization heuristic based on current protocol and market inputs. A high Trail Heat score means the protocol deserves closer review under the published method; it does not imply an imminent snapshot, eligibility, or payout.

Dusting (Core Concepts)

The act of leaving trace amounts of crypto (dust) in a wallet to keep it "active." Protocols now filter out wallets with only dust. FarmDash warns you if your wallets fall into the dusting danger zone.

Entropy (Security)

A descriptive measure of how repetitive or diverse observable wallet activity appears. Entropy can inform clustering analysis, but users should not manufacture randomness to misrepresent common control or evade anti-abuse systems.

HyperEVM (Networks)

The highly anticipated L1 blockchain from Hyperliquid. It brings EVM compatibility to their massive perp DEX ecosystem. FarmDash is optimized to track HyperEVM early-mover activity.

Oxen (Core Concepts)

FarmDash terminology for your connected wallets. Just as pioneers needed oxen to pull their wagons, you need wallets to farm. Free users get 2 Oxen, Pro users get 15.

Dysentery (Status)

A critical warning status. In FarmDash, getting "Dysentery" means your Pioneer Pace™ has stagnated for over 7 days. You need to redeploy capital or activity to avoid falling behind.

Dust Storm (Status)

A degraded-data state indicating that FarmDash could not validate the expected live source. The affected value should remain unavailable, or explicitly stale when a previously validated cache entry exists; a provider failure must not become synthetic live data.