Transparency
Quarterly public-facing transparency reports.
Aggregate stats on traffic categories, legal requests, network growth, $GRID emissions and burns, treasury balance, and liquidity health. No PII, no customer identifiers.
Current quarter
$GRID transparency report — 2026 Q2
DRAFT- Reporting period
- 2026-04-01 → 2026-06-30
- Publish date
- 2026-07-01 (scheduled)
- Report author
- iogrid Foundation
- Prior report
- — (inaugural)
This is the first $GRID transparency report. Most figures are still TBD and will be filled progressively through Q2 2026, with the final snapshot taken on 2026-06-30 and the report flipped to PUBLISHED on 2026-07-01. Until then, the authoritative source is the on-chain data itself.
What every report covers
- Treasury balance
- USDC operating reserve, $GRID held by Squads multisig (3-of-5), SOL gas reserve. Q2 figures TBD — final snapshot taken on 2026-06-30 23:59 UTC.
- Emission this quarter
- Year-0 schedule emits 50M $GRID across the year (≈137k / day). Actual vs curve is reported with the snapshot. Emission is hard-coded into the SPL program; no governance can override.
- Buyback-and-burn
- Target ≥2% of monthly revenue routed through Jupiter into the well-known incinerator address. Live dashboard at burn.iogrid.org once TGE lands. Top 5 burn transactions surfaced per quarter.
- Staking participation
- Total $GRID staked, % of circulating and total supply, distinct stakers, active provider nodes. Mandatory provider lockup pool sits inside this number.
- Liquidity health
- Raydium CLMM $GRID/USDC pool — active liquidity (USD-equivalent), 30-day volume, concentration within ±5% of mid, foundation-owned LP position (locked 4 years via Streamflow). Slippage benchmark for a $10k market buy.
- Foundation activity
- Grants disbursed, partnerships announced, governance proposals, headcount changes. Material regulatory developments and audits get their own subsection.
- Compliance + forward look
- Material regulatory developments, audits in progress / completed, jurisdictional posture changes, litigation / subpoenas / enforcement contact. Forward look for the next quarter (no price expectations).
Methodology
Every figure cites the RPC endpoint, the block / slot range, and the commands used to derive it (typically spl-token accounts against the multisig, a Raydium SDK decode of the pool account, and a custom RPC against the iogrid staking program state). Corrections are appended to the report after publication; the original numbers stay visible for audit.