Protocol / Future / Compute (Future)
plannedLayer 1 · Protocol

Compute (Future)

The planned tinycloud.compute service — execute WASM (or ZK-VM) functions over a space's data; named in the whitepaper, no implementing code.

Compute (Future)

Compute is the planned tinycloud.compute service for executing functions over a space's data — WASM (or, later, ZK-VM) functions invoked under a capability like every other service. The whitepaper gives it the abilities execute and deploy (plus list).

Why

The service set is the verb layer over a space: kv/sql/duckdb read and write data, encryption protects it. Compute would add running code against that data in place, gated by the same capability model, so an agent could be granted tinycloud.compute/execute over a space the way it is granted tinycloud.kv/get today.

Current status

Speculative / planned with no captured design. tinycloud.compute is named in the whitepaper and listed in the status matrix as not in code. There is no implementing service, no design intent beyond the spec; the "MPC stuff" once associated with compute was folded into threshold decryption. Do not assume the ability shape beyond what the whitepaper states.

See also

The live service concept is compute. Sits in Layer 1 alongside the shipped services; see the roadmap and status matrix.

Sources

  • whitepaper: README.md (tinycloud.compute; execute/deploy/list)