Badges
Badges are progression markers a wallet earns automatically when it meets a set of conditions. They replace the old flat “levels”: a badge family is a progression axis (seniority, points volume, activity in a period), and each family holds ordered tiers — the evolutions of that badge.
A tier is awarded the moment a wallet crosses its conditions, and the award is kept (history is preserved). A wallet’s current tier in a family is the highest one it has earned; the leaderboard shows it next to the wallet.
The Levels family is a built-in, system family: it holds your former levels, one tier each (
points >= threshold). It is what the Level condition in an automation and the level filter used by views and campaign cohorts now read, so those keep working unchanged.
Views
A view is a saved, named filter over the leaderboard — a “season” or a segment. The same filter dimensions decide who appears on a public leaderboard tab and who a campaign targets when it’s built from that view. A view can filter by any combination of:- Event types — only points from specific events count.
- Time period — a start and/or end date.
- Rank range — e.g. positions 1–100.
- Points range — a minimum and/or maximum balance.
- Levels — one or more level numbers.
A view must set at least one filter — a view with no filters would just be the overall leaderboard. Names are unique within a point system.
Blacklist
The blacklist bans a wallet from a point system. A banned wallet:- is rejected by the trigger API — calls that would award it points return
403; - is excluded from every leaderboard and from all campaign cohorts, however they’re built.
0x or as an ENS name; a wallet already banned under either form is detected as a duplicate. Removing a wallet from the blacklist restores it immediately — but past point events it accrued before being banned are retained.
Managing levels, views, and the blacklist is available to owners, admins, and moderators.