Cloudflare Workers¶

The relay ported to TypeScript (worker/). The Worker routes each request to its chain's Durable Object, one a chain, which keeps the queue, the batch and the funding in flight in its SQLite storage. Its alarms are the clock (clock and reads): each step an alarm.

Only what the queue and status answers need is stored, as a Durable Object's storage is bounded and a stored row costs to write: a pending submission whole, bounded by max_pending; a finished one only as its status is answered (its call and payment dropped, a few hundred bytes), kept retention_seconds; nothing for a read (a quote, an estimate, a receipt, read from its transaction when asked). A UserOp's hash rides on its submission's row, and the index from it to the submission is rebuilt in memory as the object loads. Rows from another version are read only for as long as they can still be there.

Idle costs nothing. An object with nothing queued holds no alarm, so it's evicted from memory and billed nothing; a deployment serving a quiet chain costs only its requests.

The treasury runs in the chain's object, as the Python treasury holds its relay: an hourly cron trigger calls each chain with a treasury, and its object runs it when its interval is up, keeping the snapshot in its storage. A cron rather than an alarm: nothing has to wake the object after a deploy for the treasury to start.