Table Overview
All tables live in theallium_identity.geo schema.
Corridor history starts 2026-01-01, across 30 chains (ethereum, tron, solana, base, bsc, polygon, arbitrum, avalanche, optimism, and 21 more).
For enum/field-value definitions see the Field Values Reference.
1. Addresses Geography
Table:allium_identity.geo.addresses_geography
Country-level attribution for addresses with a confident signal. Combines label-derived country signals with flow-based wallet-relatedness propagation.
Grain: One row per (chain, address). Chain values: evm, solana, tron (all EVM chains collapse to evm). Coverage: ~20M addresses.
Example — top countries at high conviction:
2. Corridors Tiered Daily
Table:allium_identity.geo.corridors_tiered_daily
The full-grain corridor table: every stablecoin transfer’s USD volume, with both legs resolved to a geography where possible and graded by measurability tier where not. Non-attributable volume is retained (tiers prefixed x_), so any slice reconciles back to total transfer volume — nothing is silently dropped or silently overclaimed.
Grain: One row per (activity_date, chain, classification, subcategory, tier, from_geo + leg type, to_geo + leg type).
A geography key can appear with different leg types —
from_geo = 'TR' from an unhosted wallet and from an exchange fan-out are distinct rows. Include the leg types when you need the full grain.3. Corridor Matrix Daily
Table:allium_identity.geo.corridor_matrix_daily
The clean country↔country matrix: only rows where both ends resolved to a geography (an alpha-2 country or a region:* key from the top-5 exchange fan). Subcategory and leg types are aggregated away. This is the table for “how does money move between geographies?”
Grain: One row per (activity_date, chain, classification, tier, from_geo, to_geo).
Example — top cross-border corridors, exact tier (last 90 days):
4. Country Flows Daily
Table:allium_identity.geo.country_flows_daily
Per-geography daily inbound/outbound totals, including one-sided flows (tier 3_partial): a country’s outbound volume is countable even when the counterparty leg is dark. counterparty_geo carries the other end, so known vs unknown counterparties split cleanly. Domestic transfers appear once per direction.
Grain: One row per (activity_date, chain, classification, subcategory, tier, geo, direction, counterparty_geo).
Example — a country’s net flow by counterparty (year to date):
5. Corridors Coverage Daily
Table:allium_identity.geo.corridors_coverage_daily
The measurability dashboard: how much of each chain’s daily stablecoin volume carries geographic signal, by classification and tier. Totals include the x_* tiers, so this table reconciles to full transfer volume — use it as the denominator for any corridor analysis.
Grain: One row per (activity_date, chain, classification, tier).
Example — geo-signal share per chain (last 30 days):
Coverage varies by chain in ways that are themselves informative: retail/remittance-heavy chains (e.g. tron ~20%+) carry far more geographic signal than DeFi-dominated (ethereum) or bot-heavy chains (near 0%) — the measurability column makes chain character visible at a glance.
6. Transfers Geo Resolved (Gated)
Table:allium_identity.geo.transfers_geo_resolved
Transfer-grain geo resolution for advanced users who need to join geography at row level: one row per stablecoin transfer (same population as the enriched transfers), with each leg resolved exactly as the corridor tables resolve them — so row-level drill-downs reconcile with the published aggregates.
Grain: One row per transfer (unique_id). Chain values: per-chain. Live view — every query resolves against the latest attributions.
Example — fan a slice yourself with LATERAL FLATTEN:
Always filter
chain and activity_date — this view sits on billion-row transfer tables. Total USD reconciles to the corridor aggregates to the dollar; tier composition on older days can differ slightly, because this view resolves against today’s attributions while corridor partitions freeze at their last rebuild.Data Freshness
Next Steps
Example Queries
Corridor matrices, country flow balances, payment-purpose geography
Field Values Reference
Data dictionary, data quality, and best practices