Skip to main content
Sentinel layers multiple deployment limits to prevent spam without gating legitimate creators.

​
Deployment cost

Each token deployment requires 0.1 SOL paid at creation. This is the first economic filter. It helps:
  • prevent zero-cost spam,
  • introduce real capital cost to mass deployments,
  • and align deployers with some minimum level of intent.
Cost alone is not enough. That is why Sentinel adds throughput and identity controls on top.

​
Per-account rate limiting

Each Burst account is subject to deployment throughput limits. Burst applies this as a rolling time window rather than fixed intervals. That means:
  • small bursts can still be allowed,
  • but sustained rapid deployment gets blocked.
This helps stop bot loops, scripted mass launches, and rapid identity flooding.

​
Deployment cooldown

After each deployment, Burst can apply a short cooldown period. This prevents back-to-back launches from running indefinitely. Cooldowns can be fixed or adjusted dynamically based on system conditions.

​
Global throughput limits

Burst also enforces a system-wide deployment ceiling. This protects core infrastructure during spikes, including indexing systems, metadata resolution, and Meteora pool creation flow. If the system is under heavy load, deployments can be throttled, delayed, or rejected.