Verity’s Prover includes a mechanism to optimise proving times.
/proxy
endpoint triggers the setup of a new MPC connection thread in a cold start manner. This process takes 2–3 seconds per request, depending on the geographic distance between the Prover and the source server.
With thread management, the Prover can pre-prepare these connections for expected requests to the source server domain. This enables a warm start, cutting the response time for verifiable requests by 2–3 seconds.
Note: TTR increases proportionally with the size of the request/response:
/pools
API endpoint/prepare
API endpoint and T-PREPARE
header/proxy
API endpoint and T-PREPARE
headerT-PREPARE
header is ignored.