Network/Register/Anti Flood Concrete Numbers
Gap Register
G-043Public

Anti-flood concrete numbers

Tier 2 — Structurally thin, not launch-blocking
Status
Open — not started
Owner
Creator
Why now
D11 sets architecture; specific limits must be tuned before launch to handle the expected end-user submission spike.

Establish rate limits per Power tier, per-triple pending-op caps, queue prioritization weights, and sybil thresholds. Empirical, post-launch tunable.

Why this matters

D11 commits to Power-tiered submission rate limits, per-triple pending-op throttle, queue isolation between provider ingestion and user submissions, and the daily consensus pass as natural shock absorber. The architecture is settled; the numbers are not.

Concrete values needed before launch:

  • Rate limit per Power tier (requests/minute)
  • Per-triple pending-op cap (per hour)
  • Queue prioritization weights (G7 features feed this)
  • Sybil/coordinated-behavior detection thresholds

Initial values will be empirical guesses requiring post-launch tuning, parallel to G8's mechanism for consensus constants.