Default release-profile tiers
These are the default request-submission tiers when the operator is built withoutalpha1 tranche changes and without the no_rate_limit feature.
| Tier | DDX balance | Average limit per hour | Burst |
|---|---|---|---|
| Tier 0 | < 1,000 | 900 | 1 |
| Tier 1 | >= 1,000 | 1,800 | 5 |
| Tier 2 | >= 1,000,000 | 180,000 | 50 cap |
What this page can answer safely
| Question | Public answer |
|---|---|
| what the default repo-backed REST write-path tiers are | this page answers that directly |
how build flags such as alpha1 or no_rate_limit change the request path | this page answers that directly |
| what the current hosted public deployment is enforcing right now | this page cannot guarantee that by itself; verify the target deployment and observed 429 behavior before hardcoding one live quota |
Feature-gated variants
alpha1keeps the same request-rate tiers, but changes collateral tranche limits.no_rate_limitcompiles out the tiered request guards and raises the supporting burst-cap constant from50to100000.- Treat
429behavior as deployment-conditional rather than as a permanently fixed public-law constant.
Burst behavior
| Topic | Contract |
|---|---|
| Burst queueing | The inbound webserver and sequencer path can delay requests before outright rejection once the burst buffer fills |
| Explicit rejection | 429 RateLimit is the canonical request-level rejection when the trusted path enforces the limit |
| Deployment variance | A build with no_rate_limit changes both rejection posture and queue depth materially; do not assume public-host behavior matches every private operator deployment |
Client behavior
- Back off and retry on
RateLimitresponses. - Do not retry validation or safety failures unchanged.
- Track request IDs, timestamps, and observed tier posture to correlate retry loops.
- Treat prolonged response delay during bursts as rate-limit pressure even before a visible
429. - Keep the live-deployment question separate from the build-profile question. Public source constants are useful planning inputs, but they are not a substitute for current deployment verification.