DOCUMENTATION / PROJECT ZERO

Limits and the Zero Pool

Project Zero draws on a shared daily pool that resets at 00:00 UTC.

Project Zero is served from the Zero Pool: a shared daily pool of verified zero-cost capacity. The program's public contract plans the pool to start at 100 trillion (100T) shared tokens per day. That is a pool for the whole program, not an allowance per developer.

The daily reset

The pool is replenished every day at 00:00 UTC. tessen zero and GET /v1/zero/status return the exact reset time as reset_at.

When the pool cannot serve

A request is refused with 503 zero_capacity_unavailable when no verified zero-cost capacity can serve it, or when today's pool is used. The error includes reset_at. It is never routed to paid capacity instead.

Per-developer controls

Tessen can apply per-developer allocations, concurrency controls and abuse protections so the shared pool stays useful. Their thresholds are not a published contract and are not listed here; a refusal always carries its reason.

Growing the pool

Tessen Node is designed to let developers contribute compatible compute. Verified additional capacity can increase the next day's pool at the 00:00 UTC reset. Node is not yet released.