Skip to main content
Sentinel does not enforce limits purely by wallet address. It correlates behavior across multiple signals to catch multi-wallet abuse that simple address-based limits would miss. This is what makes it ~90% harder for one user to bundle supply across multiple wallets.

​
Detection signals

Sentinel correlates behavior across:
  • account identity,
  • funding source,
  • and device or session signals.
This helps Burst detect multi-account activity, apply shared limits across linked wallets, and restrict abusive patterns.

​
Identity correlation

When multiple wallets show correlated behavior, Sentinel links them to the same underlying actor. This means rate limits and cooldowns apply across the full set of linked wallets, not just individually. A user who creates 10 wallets does not get 10x the deployment throughput. They get treated as one actor.

​
Funding source analysis

Sentinel tracks where deployment funds originate. If multiple wallets are funded from the same source, that signal is factored into enforcement decisions. This catches the most common bundling pattern: one user splitting SOL across fresh wallets to buy up supply from multiple addresses.

​
Device and session signals

On-platform behavioral signals from devices and sessions add another layer. This makes it harder to circumvent limits by simply creating new wallets.

​
What this prevents

  • Supply bundling where one user buys from multiple wallets to control a token’s early market.
  • Coordinated spam launches across many wallets.
  • Sybil attacks that try to game deployment limits.
  • Multi-wallet manipulation of early token prices.
Sentinel keeps creation permissionless. It raises the cost and complexity of abuse without blocking legitimate users.