All releases
Mohith / 3 min read
OperationsAvailable
More reliable serverless verifier startup
The engine fixed cold-start initialization failures and pinned the release runtime used to initialize the proof verifier consistently.
Mohith / 3 min readWhat changed
Verifier initialization was made deterministic for the serverless startup path, and the release runtime was pinned so deployment did not silently select a different Node version.
The verifier now enters the request path only after its required runtime and artifacts have initialized, preventing a partially constructed verifier from serving authentication work.
Operational boundary
This fix targets initialization reliability, not the latency of every cold invocation. Deployment regions, platform scheduling, artifact caches, and database startup can still affect cold response time.
Current deployments
The pinned runtime records the environment used by this release. Current deployment configuration and evidence are authoritative after later framework and runtime upgrades.