pub const PROVISION_RATE_LIMIT: u32 = 1000;Expand description
How many bot.did.createAccount and bot.did.createSession calls one
caller address may make per PROVISION_RATE_WINDOW, the two together.
Sized against a legitimate caller rather than against a read route:
crates/didbot-swarm, the local agent simulator, defaults to 8 events per
second (didbot-swarm --rate, scripts/dev-swarm.sh) and spends most of
them on Spawn while its population is below target, all from the one
address a local run shares.
Sustained, that is up to 480 provisioning calls a minute from a single
caller with nothing wrong — the case plan/pds-xrpc.md’s “what [rate
limits] do to a swarm sharing one address” names. This limit clears that
with better than double the headroom, while still bounding what a caller
this route does not authenticate can spend of this deployment’s signing
keys, Route53 record-set quota and blob storage per minute.