Skip to main content
server.CustodyWorkers The worker processes a component executes its custody work through. A component that keeps derived data in retained custody and runs that work outside the engine (the computations component’s workers) registers each worker’s bearer credential here by its SHA-256 digest. A request presenting a live registered credential runs with no identity, and its calls into this component and its response are decided as this component’s custody work: a protected read reaches the worker only when every source’s disclose rule permits { kind: "custody", component } naming this component, the consent its scheduled work already needs, decided again at each response. The holder is always the calling component.

Methods

registerWorker

▸ registerWorker(digest, options): Promise<void> Register the worker whose bearer credential hashes (SHA-256, lowercase hex) to digest until until (Unix milliseconds, at most 30 days ahead). Requires a deployment administrator with export authority in the calling transaction. A digest is registered once; rotate with a new credential. A component keeps at most 256 live workers.

Parameters

Returns

Promise<void>

revokeWorker

▸ revokeWorker(digest): Promise<boolean> End this component’s registration of digest, if it has one, in this commit: no later response reaches that worker. Returns whether one ended.

Parameters

Returns

Promise<boolean>