Methodology.
How every number is made, what it leaves out, and where it can mislead. Activity is read from the chain; market data is third-party and labelled; missing data is shown as missing.
Pipeline
- Read. A worker follows Arc mainnet's tip over public RPC, fetching each block's receipts with
eth_getBlockReceipts(two RPC calls per block). It rotates across several RPC endpoints with retry and backoff, because a single free endpoint throttled CI traffic during development. - Aggregate. Receipts are summed in memory into one rollup per UTC day: per network, per contract, per token, active senders and per-contract users. No per-transaction rows are stored; the free database tier cannot hold Arc's 1 to 2 million transactions a day.
- Commit atomically. A batch of rollup changes and the new checkpoint are written in one database transaction (
apply_ingest_batch). A crash cannot double-count or skip a block. - Score. Every four hours a job reads the rollups and live on-chain balances and writes TVL and score rows.
- Serve. A read-only API is the only reader of the database. The dashboard, the badge and third-party apps all go through it.
Because only rollups are kept, a metric can be recomputed only for days still in the rollups, and a definition change means re-ingesting from the chain. This has happened once: see USDC.
Network metrics
| Metric | Definition |
|---|---|
| Transactions | Transactions included in blocks on that UTC day, taken from receipts. |
| Failed rate | Failed transactions divided by transactions. A failed transaction still pays gas. |
| USDC gas | Gas used times effective gas price, summed, in USDC (6-decimal view). Includes failed transactions. |
| Gas per transaction | USDC gas divided by transactions. |
| Contracts deployed | Contract creations that day. |
| Active addresses | Distinct transaction senders that day. |
| Blocks | Blocks applied that day. |
| USDC movement | Gross USDC transferred; see below. |
Partial days. The current UTC day is still accruing and is hatched in charts. If ingestion is behind the tip, the newest days are also incomplete and the status pill says so. Early days. 27 and 28 September 2026 predate the rollup pipeline: their transaction and gas totals exist, but failure, deployment, block and active-address counts are blank, and are not zero.
USDC
USDC is Arc's native gas asset. It is exposed two ways: an 18-decimal native balance used for gas and msg.value, and a 6-decimal ERC-20 at 0x3600…0000. These are the same funds, not two assets. Isogram never adds them, never treats a move between them as a swap, and stores every USDC amount in the 6-decimal view, converting exactly once at ingestion.
Arc emits USDC Transfer logs from two places: a native system log (0xffff…fffe, 18 decimals, once per explicit USDC movement including plain native sends) and the ERC-20 contract (6 decimals, ERC-20 calls only). One ERC-20 transfer emits both. Isogram counts USDC movement from the system log only. Measured on 200 live blocks, the ERC-20 stream alone missed 74% of USDC volume, because many transfers are plain native sends.
- The figure is gross movement: every transfer log counts, including intermediate hops through routers and pools, so one swap can contribute several. It is not economic volume.
- Mints and burns (a transfer to or from the zero address) are excluded as supply changes.
- EURC and USYC are ERC-20 only and are counted from their own transfer logs, in their own units. Volumes of different tokens are never summed.
Projects
Discovery
Each run looks at which contracts received meaningful activity in the rollups. New ones are classified and, when the classification is confident, promoted to a tracked project. Classification uses GeckoTerminal and explorer metadata and, for anything ambiguous, manual review. Plain wallets (no bytecode) are rejected before any lookup is spent.
Trust
- Verified projects were seeded or checked by a person, with every contract confirmed on-chain. Their category and contracts are protected by a database trigger, so automated discovery cannot overwrite them.
- Discovered projects were promoted automatically. Their names come from public metadata that the deployer chose, so they can be misleading. Listing is not endorsement.
- Tokens whose name or symbol impersonates a brand (including Circle) are never auto-promoted. The stablecoin category is applied only to hand-seeded tokens, never inferred from a name containing “usd”.
- A discovered contract can never claim the slug or the contracts of a seeded project.
Attribution
Gas and usage are attributed to a project through its list of contracts at read time, so a contract promoted later is attributed retroactively for days still in the rollups. Per-project unique users are recorded only for contracts that were tracked when the day was ingested, so a newly promoted project accrues users from its promotion forward. Per-contract daily rows with fewer than three transactions on a closed day are dropped; network totals stay exact, so per-contract sums never exceed them.
Holders and links
Holder counts come from Arc's explorer, refreshed about every 12 hours; a dash means the explorer does not index the address as a token, and a count older than 72 hours is treated as unknown. Links are validated (https only, no credentials or unusual ports, real DNS names, platform handles rebuilt on each platform's own host). Links set by Isogram are tinted; links registered by a token's deployer are shown as unverified and opened with noopener nofollow ugc.
Submissions
Project owners can propose a contract through the API. A submission never lists anything by itself: it waits in a queue for a person to review.
Segments
Every project belongs to a segment derived from its category, and each segment shows only the metrics that mean something for it. A score or TVL for a memecoin would be noise, so non-DeFi segments show a dash there.
| Segment | Categories | Measured with |
|---|---|---|
| DeFi | dex, lending, yield, liquid-staking | TVL, Arc Native Score, usage, gas |
| Launchpads | launch platforms (a curated list) | Usage, holders, price of the platform token |
| Infrastructure | infra, bridge, oracle, governance | Usage, users, gas, failure rate |
| Stablecoins | stablecoin, institutional | Price and market data, holders, usage |
| Tokens | token, meme, wrapped | Price, 24h change, volume, liquidity, holders |
| Other | no category yet | Usage only. A category is never guessed. |
Tokens launched through a launchpad are always filed as tokens; the launchpad row is the platform itself, not its clones.
TVL
TVL exists only for DeFi protocols. It is the live on-chain balance of the tracked tokens held by the protocol's contracts, read with balanceOf at scoring time, not reconstructed from history. USDC is counted once (see above). It is a snapshot every four hours, not an average, and covers the tracked tokens only.
Arc Native Score
A single number from 0 to 1 that ranks DeFi protocols against each other. Four inputs, equal weights, each scaled to 0 to 1 across the DeFi peer group:
score = 0.25 * normalize(usdc_gas_7d)
+ 0.25 * normalize(unique_users_7d)
+ 0.25 * normalize(tvl_usd)
+ 0.25 * contract_age_bonus- normalize is min-max within the DeFi segment only: the least active protocol gets 0 on that input and the most active gets 1.
- usdc_gas_7d is USDC gas paid by the protocol's contracts over the last 7 UTC days (today partial).
- unique_users_7d is distinct transaction senders that called the protocol's contracts in the window.
- contract_age_bonus ramps linearly from 0 at deployment to 1 at 30 days.
Token market data
Price, 24h change, volume, liquidity and fully diluted value come from GeckoTerminal (CoinGecko's on-chain data) for token, stablecoin and launchpad projects, refreshed hourly. This is third-party data, not read from Arc by Isogram, and every surface says so. Roughly half of tracked tokens have a priced pool at all, and most of those are thin. A token's name is chosen by its deployer: one called “Bitcoin” was priced at $82,000 with $59 of daily volume.
| Flag | Rule | Effect |
|---|---|---|
ok | At least $10,000 liquidity and 24h volume of at least 1% of it | Price, volume, FDV and market cap shown |
thin | Liquidity unknown or under $10,000 | Price shown dimmed; FDV and market cap hidden |
inactive | $10,000+ liquidity but under 1% of it traded in 24h | Price may be stale; FDV and market cap hidden |
- FDV is price times supply on Arc, not a global figure, and is withheld unless quality is
ok, because it inherits every flaw of the price. - The CoinGecko tag means GeckoTerminal maps the token to a CoinGecko listing. Without it the price comes from a DEX pool and is unverified.
- 24h volume covers all pools. 7-day volume covers only the most liquid pool, so it can understate tokens that trade in several pools.
- 24h change is the top pool's change and is shown only when the token is that pool's base token, because a pool's change describes its base asset.
- A price of 0 is stored as unknown. Data older than 24 hours is hidden, never shown stale. The thresholds are judgement calls from early data and are published here so they can be challenged.
DEX volume
Each venue's own busiest pools (up to 200) are read from GeckoTerminal every hour and summed. Uniswap V2, V3 and V4 are separate venues, as GeckoTerminal and CoinGecko list them. Venues are shown as DEXes unless confirmed as launch platforms.
Anomaly filter. Raw sums were wrong on Arc: one venue summed to $27.8M against $0.4M on CoinGecko, because a few pools reported millions in volume from two or three wallets. A pool is excluded when it has fewer than 10 traders in 24 hours, or its volume exceeds 25 times its reserves (or it has volume and no reserves). The excluded amount is reported beside each venue and in the API (excluded_volume_usd), never hidden. Applied to that venue it leaves about $0.5M against CoinGecko's $0.4M; the other venues agreed within about 25% without any filtering, and turnover cutoffs between 10x and 100x change nothing, so 25x is not a sensitive choice. CoinGecko's own rule is not public, so totals can still differ.
- A leading “≥” means the venue has more pools than the scan covers, so the figure is a lower bound.
- Only venues whose scan finished are updated; others keep their previous row, which is hidden after 24 hours. If transaction counts are missing for a venue it is refused rather than reported unfiltered.
- Liquidity is deliberately not summed per venue: reserves are self-reported and one spoofed pool distorts a sum.
Freshness
| Data | Refresh | Hidden when older than |
|---|---|---|
| Network and project activity | Continuous | n/a (days after data_through are partial) |
| TVL and score | Every 4 hours | n/a (shows the latest run's time) |
| Market data and venues | Hourly | 24 hours |
| 7-day token volume | About every 6 hours | 48 hours |
| Holders | About every 12 hours | 72 hours |
| Links | Weekly | n/a |
The status pill reads /metrics/status: the timestamp of the last block applied and how far behind now that is. It says live only when that lag is under ten minutes. Scheduled jobs on GitHub Actions are best effort, so the worker chains its own runs to keep following the tip.
Known limits
- Coverage starts on 27 September 2026. Earlier days are not backfilled.
- USDC movement is gross, and counts router and pool hops.
- Blocklist reverts consume gas without producing a receipt, so those transactions are absent from transaction and gas totals. This is a small gap, documented by Arc.
- Unique users are senders that called a project's contracts directly. Calls through a router are attributed to the router.
- Token and DEX data is third-party. Isogram can only be as accurate as GeckoTerminal, and filters what it can prove is anomalous.
- Names are deployer-chosen. Verify an address before trusting a name; the search box accepts a contract address.
- Scores are relative to a small group and not comparable across the 8 October 2026 change.
- Single instance. The API runs on free hosting and can take a few seconds to wake; rate limits are per process.
Isogram is research and ecosystem infrastructure. Nothing on it is a trading signal or financial advice.