treasury protocol
- never sell/swap $antihunter.
- fees in weth fund inference, hardware, crypto, and nfts as assets/investments.
- $antihunter may be used to pay community members for tasks + rewards.
- protocol changes: 7 days notice for community feedback.
Canonical wallet
0xa668ddf22a4c0ecbb31c89b16f355b26ae7703c3
View on BaseScan
Every important number should be traceable back to a transaction.
What you’re looking at
- Balance: current token balance held by the treasury wallet (best-effort aggregation by the data provider).
- Entry: earliest observed acquisition timestamp for the position (best-effort; some assets may have incomplete history).
- Cost basis: inferred from on-chain settlement flows (ETH/WETH) associated with acquisitions.
- FMV: current fair market value (USD) from the pricing data source.
- PnL: FMV minus inferred cost basis.
Data sources
Onchain receipts
BaseScan is the source of truth for transfers, swaps, and balances.
Treasury wallet on BaseScanPortfolio + USD annotations
The site uses Arkham Intel’s portfolio view + transfer USD annotations as best-effort pricing inputs.
Arkham IntelPricing sources can disagree (DEX spot vs aggregator vs CEX). We keep the pipeline explicit so you can audit the assumptions.
links
Static snapshot (fast)
Daily-generated JSON used by the homepage when available.
Live API (fallback)
Real-time computation; slower and more failure-prone than the snapshot.
Known limitations
- Best-effort accounting. The table is a reporting layer, not audited financials.
- Incomplete attribution. Some purchases/sales may not be cleanly attributable to a specific tx hash (e.g., multi-hop routes, aggregator bundling, internal transfers).
- USD pricing drift. USD values are based on a third-party portfolio view and can differ from DEX spot or centralized exchange price.
- Cost basis approximation. When the treasury spends $ANTIHUNTER to acquire other tokens, cost basis may be approximated using spot pricing (non-historical) rather than trade-time execution price.
- Chain truth. If you’re verifying a claim, use BaseScan and the underlying transactions.