AntfarmDAO
HomeGovernanceTreasuryDelegatesContractsUpdatesCareersAbout
View ProposalsOpen Antfarm App
AntfarmDAO

Public governance and transparency portal for the Antfarm ecosystem. Review proposals, treasury activity, delegates, and verified contracts.

Verify official contracts, proposals, and community links before interacting. Review security guidance.

Last synchronized: Jul 11, 2026, 6:23 PM GMT+2

Governance

  • Proposals
  • Delegates
  • Treasury
  • Governance parameters

Participate

  • Careers
  • Contribute

Community

  • X Opens in a new tab.
  • LinkedIn Opens in a new tab.
  • Discord Opens in a new tab.
  • Telegram Opens in a new tab.

Resources

  • Documentation Opens in a new tab.
  • Protocol Opens in a new tab.
  • GitHub Opens in a new tab.
  • Contracts
  • Security

© 2026 The Antfarm DAO. Informational purposes only.

SecurityPrivacyTermsDisclaimer

Security contact: support@antfarmdao.com

Update

Treasury Transparency: Methodology and Data Sources

How the Antfarm DAO portal calculates treasury estimates, which addresses and chains are included, and the limitations you should understand before relying on displayed values.

Jun 2, 20265 min readBy Treasury Working Group
Source: Local MDX contentUpdated Jul 11, 2026, 6:23 PM GMT+2

Status: published · Last reviewed: Jun 2, 2026

Editorial analysis

This article is editorial content reviewed separately from live metrics.

Treasury transparency is a core commitment of the Antfarm DAO public portal. This article documents how treasury values are estimated, which data sources feed the dashboard, and where methodological limits apply.

Scope: what counts as treasury

The portal tracks assets controlled by **DAO governance addresses**, not the full protocol Total Value Locked (TVL).

Primary treasury address

The primary treasury on Ethereum is the **Antfarm Timelock** at `0x529C78Ee582e4293a20Ab60c848506eADd8723D8`. Governance-approved outflows execute through this contract after timelock delays.

Additional addresses may be added to the registry as governance authorizes new vaults or chain deployments. The Contracts page lists all registered addresses with verification status.

Multi-chain coverage

Initial reporting focuses on **Ethereum mainnet**. Configured RPC endpoints for Arbitrum, Avalanche, and Polygon zkEVM support future expansion when DAO-controlled assets on those networks are formally registered.

Assets held by user wallets, liquidity pools outside DAO control, or unaudited deployer addresses are **excluded** unless explicitly added through governance.

Asset valuation methodology

Balance reads

Token balances are read via RPC or indexer APIs using **raw integer balances** (`balanceRaw`) with token-specific decimals. Formatted balances are derived for display; aggregation uses USD estimates where price feeds are available.

Price sources

USD values come from recognized price oracles or aggregated market feeds configured in the data adapter layer. Each asset row shows:

  • **Price per unit** in USD
  • **Estimated value** (balance × price)
  • **Price source** label (e.g., oracle name or API provider)
  • **Updated time** for the price snapshot

Prices are point-in-time estimates. They can diverge from execution prices during large swaps or illiquid markets.

Total treasury value

Total estimated value is the **sum of included asset USD values**:

``` totalUsd = Σ (asset.valueUsd ?? 0) ```

Assets without a reliable price show balance data but may omit USD value rather than invent a number. The portal never silently substitutes mock prices in live mode.

Allocation and charts

**Allocation percentages** divide each asset's USD value by total treasury USD. When some assets lack prices, allocation charts may exclude them or show them in an "unpriced" category—check the methodology panel on the Treasury page for the current behavior.

Charts include textual summaries for accessibility. Do not rely on chart colors alone to identify asset classes.

Transaction classification

Treasury **transactions** are indexed from onchain transfer events involving registered treasury addresses. Each row includes:

  • Timestamp, asset, amount, direction (in/out/internal)
  • From and to addresses
  • Transaction hash with explorer link
  • Optional related proposal ID when execution metadata links the transfer

Classification rules

| Classification | When applied | | --- | --- | | Governance execution | Outflow from timelock after proposal execution | | Protocol revenue | Inflow from protocol fee collectors with documented routing | | Grant | Transfer matching approved grant proposal | | Contributor payment | Transfer to known contributor multisigs per proposal | | Internal transfer | Movement between DAO-controlled addresses | | Unclassified | Insufficient evidence to assign a label |

**Unknown or unclassified transactions remain labeled honestly.** The portal does not infer purpose from heuristics alone without supporting evidence—consistent with reporting standards adopted in `prop-4`.

Update frequency and caching

  • **Live mode:** Data refreshes on a server-side schedule with short TTL caches (typically 60–120 seconds for treasury summaries).
  • **Mock mode:** Demo seed data is displayed with a visible **Demo data** banner.

The footer shows **last synchronized** time. Stale data notices appear when upstream APIs fail rather than falling back to fabricated values in production.

Limitations you should understand

1. **Estimates, not audits** — Displayed USD values are estimates for transparency, not certified financial statements. 2. **Not protocol TVL** — Treasury value excludes user deposits in pools the DAO does not control. 3. **Oracle risk** — Prices depend on external feeds that may lag or fail during volatility. 4. **Indexing gaps** — Rare token standards or internal accounting may require manual reconciliation. 5. **Cross-chain delay** — Multi-chain treasuries may update at different intervals per chain indexer.

Governance-linked reporting

Proposal `prop-4` established quarterly reporting standards requiring asset breakdowns, methodology notes, and onchain verification links. This portal implements those standards in machine-readable form; PDF or forum archives may supplement but do not replace explorer verification.

Proposal `prop-5` (Contributor Working Group budget) illustrates treasury outflows tied to explicit governance authorization—look for related proposal IDs on transaction rows.

How to verify independently

1. Copy treasury addresses from the Contracts page—never from social media or DMs. 2. Check token balances on Etherscan for each registered address. 3. Compare summed balances against portal totals, allowing for price timing differences. 4. Trace large outflows to execution transactions and proposal IDs. 5. Report discrepancies to support@antfarmdao.com with hashes and screenshots.

Related reading

  • Understanding the Antfarm DAO Governance Lifecycle
  • How to Read an Executed Governance Proposal
  • Treasury dashboard

Related proposals

  • Proposal prop-4
  • Proposal prop-5

Related contracts

  • 0x529C78Ee582e4293a20Ab60c848506eADd8723D8
  • 0x518b63Da813D46556FEa041A88b52e3CAa8C16a8
  • 0x0BF43350076F95e0d16120b4D6bdfA1C9D50BDBD

Sources

  • Treasury page
  • Proposal 4 — Reporting Standards
  • Antfarm documentation — Governance
← Back to all updates