Repository navigation
@odatano/nightgate 0.34.0
@odatano/nightgate 0.34.0
One throughput policy: rate classes, grant budgets per hour, one 429 answer. Schema delta: three nullable columns on AgentGrants. No circuit change.
- Nine rate classes replace the per-action limiters (
prove60/h per session,deploy5/h per session,sponsor120/h,compute120/h,read60/min,wallet10/min,signing10/h,admin10/h,public-verify60/min per address); each count isNIGHTGATE_<CLASS>_RATE_LIMITorrateLimits.<class>inNIGHTGATE_SPONSOR_POLICY_FILE, which applies without a restart.NIGHTGATE_GRANT_ADMIN_RATE_LIMITisNIGHTGATE_ADMIN_RATE_LIMIT. maxJobsPerHouron agent grants next tomaxJobsPerDay;NIGHTGATE_GRANT_DEFAULT_JOBS_PER_HOURand_PER_DAYfill a budget the creation leaves out.- Every 429 names its limit and carries
Retry-After; answers under a limit carryRateLimit-PolicyandRateLimit;getMetrics()countsrate_limited_total{limit}. getGrantUsagereturnslimits(budgets withusedandresetsAt, rate classes withremaining); a token may leavegrantIdempty.@odatano/nightgate-tx0.13.0:NightgateApiError.retryAfterSeconds.- Unbound sponsoring keeps a dust backing reserved until the sponsor wallet lists the spend (
NIGHTGATE_NOTE_SPENT_WAIT_MS, default 30 s): no second spend of the same note under parallel load (1010/196, rebuild). - A submit that died on the client's closing socket is resent as a transport failure; a copy the node refuses is looked up on the indexer, never rebuilt. Resend, refusal and dust-race log lines carry the identifier.
Full Changelog: v0.33.3...v0.34.0