Overview - Allium Documentation Hub

Wallet Classification turns raw stablecoin activity into a compact wallet profile: a balance tier, a wallet type, a behavioral segment, and 0–100 engagement and risk scores. Use it to size cohorts, segment users, and screen for volatile or anomalous wallets without building the feature pipeline yourself. Each row is a daily snapshot of one wallet on one chain — (chain, address, snapshot_date) is the unique key.

Classification is derived from stablecoin transfers and balances (the top stablecoins per chain), not from a wallet’s full on-chain footprint. A wallet’s tier and scores describe its stablecoin behavior. A heavy NFT or DEX trader who rarely touches stablecoins will look small here. For a wallet’s broader activity, see Wallet 360.

Always filter by chain. The crosschain table unions 30+ chains, so an unfiltered scan reads every chain at once. Filtering by chain (and, where possible, snapshot_date) keeps queries fast and cheap — the table is clustered on snapshot_date, and chain is the natural partition. Every sample query below filters by chain for this reason.

Where it lives

Surface	Table	Use when
Crosschain (all chains)	`crosschain.wallet360.wallet_classification`	You want one query across chains — filter by `chain`.
Per chain	`<chain>.wallet_features.wallet_classification`	You only need one chain (e.g. `ethereum.wallet_features.wallet_classification`).

The crosschain table is a union of the per-chain tables, so both share the same columns. A wallet active on several chains appears as one row per chain — aggregate across rows (group by address) for a wallet’s multi-chain view.

How addresses are selected

The address universe is built from filtered stablecoin transfers, then snapshotted to each wallet’s most recent activity day.

Start from top stablecoins

Transfers of the top stablecoins per chain (the largest by volume) are the raw input. Activity in non-tracked tokens does not contribute.

Keep only organic, real-payment transfers

A transfer is included only when it is the largest USD leg of its transaction that day, the sender is organic, and the transfer is not a mint or burn. An address is flagged inorganic (and dropped) when it moves ≥ $10M or makes ≥ 1,000 transfers in a rolling 31-day window, or carries a bot/MEV label.

Exclude non-end-user addresses

Addresses labeled as exchanges, DeFi protocols, infrastructure, bridges, treasuries, tokens/contracts, or sanctioned are excluded, along with dust (max balance <

10 and 30-day volume &lt;

100) and obvious bot/test wallets (active nearly every day with an average transfer < $3).

Snapshot to the latest activity day

snapshot_date is the wallet’s last day of recorded stablecoin activity. Models run daily with a 30-day lookback so the rolling 30-day metrics stay correct. Downstream consumers typically take the latest snapshot per wallet.

No attribution labels (CEX / DeFi / infrastructure / entity names) are exposed in this table by design. Labels are used internally to assign wallet_type, but are not output as columns.

Classification dimensions

Dimension	Column(s)	What it answers
Size	`balance_tier`	How large is the wallet? (whale → dust, by max stablecoin balance)
Type	`wallet_type`	Consumer, Business, or Institutional behavior
Lifecycle	`behavioral_segment`, `combined_segment`	New, active, dormant, or churned
Engagement	`engagement_score`, `engagement_tier` (+ recency/frequency/consistency)	How consistently active is the wallet? (0–100)
Risk	`risk_score`, `risk_flag` (+ volatility/anomaly)	How volatile or anomalous is its balance? (0–100)

See Wallet Classification Attributes for every column, its formula, and exact thresholds.

Sample queries

Cohort sizing (one chain)
High-value active users
Risk screen
Multi-chain footprint

Distribution of wallets by balance tier and lifecycle on Ethereum, latest snapshot per wallet.

with latest as (
    select *
    from crosschain.wallet360.wallet_classification
    where chain = 'ethereum'                      -- always filter by chain
    qualify row_number() over (
        partition by address order by snapshot_date desc
    ) = 1
)
select
    balance_tier,
    behavioral_segment,
    count(*) as wallets
from latest
group by all
order by wallets desc

Engaged whales and large wallets currently active on Base.

select address, balance_tier, engagement_tier, engagement_score, current_balance_usd
from crosschain.wallet360.wallet_classification
where chain = 'base'                              -- always filter by chain
    and balance_tier in ('whale', 'large')
    and behavioral_segment = 'active'
    and engagement_score >= 60
qualify row_number() over (partition by address order by snapshot_date desc) = 1
order by current_balance_usd desc
limit 100

Wallets flagged high risk on Polygon in the last 7 days.

select address, risk_score, volatility_risk_score, anomaly_risk_score, current_balance_usd
from crosschain.wallet360.wallet_classification
where chain = 'polygon'                           -- always filter by chain
    and snapshot_date >= current_date - 7         -- and bound the date range
    and risk_flag = 'high'
order by risk_score desc

Wallets present on more than one chain (aggregate across the per-chain rows).

with latest as (
    select chain, address, balance_tier
    from crosschain.wallet360.wallet_classification
    where chain in ('ethereum', 'base', 'polygon', 'arbitrum')  -- scope the chains
    qualify row_number() over (
        partition by chain, address order by snapshot_date desc
    ) = 1
)
select address, count(distinct chain) as chains, array_agg(chain) as chain_list
from latest
group by address
having count(distinct chain) > 1
order by chains desc

On chains without native end-of-day stablecoin balances, current_balance_usd and the balance-derived fields are reconstructed from net transfer flow and are best-effort rather than exact. Tiering and engagement signals remain directionally reliable.

​Where it lives

​How addresses are selected

​Classification dimensions

​Sample queries

Where it lives

How addresses are selected

Classification dimensions

Sample queries