Skip to main content
Recipes for the allium_identity.geo schema. All corridor examples work across the 30 supported chains; add a chain filter to scope to one.

1. Top cross-border corridors (exact tier)

The highest-confidence view: both ends attributed to a country.

2. A country’s flow balance — who is it a net receiver from?

Asymmetric corridors (heavily one-directional) usually indicate a real-world flow — remittances, settlement — where near-symmetric ones indicate round-trip trading.

3. Payment purposes with geography

Where do consumer-to-consumer payments actually move? Combine the payments classification with its purpose subcategories:

4. Consumer vs institutional exchange flows by origin country

The cex_flow subcategories type the counterparty of every exchange flow — c2x is a consumer depositing, i2x an institution:

5. Coverage first: how much of a chain can be measured?

Run this before any cross-chain comparison — coverage differences are findings, not noise:

6. Corridor trend over time

Watch a specific corridor month by month (directionality shifts are the story):

7. Compliance lookup: country attribution for a set of addresses

For EVM lookups use chain = 'evm' (all EVM chains collapse to one value in addresses_geography); preserve address case for Solana/Tron.

8. Reconciliation check

Any corridor slice reconciles to total transfer volume when the x_* tiers are included — use this to sanity-check your own aggregations:

Next Steps

Table Reference

Full column-level schema for every table

Field Values Reference

Data dictionary, coverage, and best practices