Writing
#hub
Every post tagged hub.
Treeship 0.25: revocation, and the wasm saga
Grant revocation works end to end and Linux arm64 binaries ship. It took four point releases to get a working verifier back onto npm, and the lesson is worth the telling.
Treeship 0.15: bridges sign with their own keys
The MCP and A2A bridges provision per-agent keys by default, A2A skills become cards, and audit proves a hub log was only appended to.
Treeship 0.14: capability cards and the agent resolver
Agents get per-agent keys, signed capability cards, and a hub-backed resolver with a transparency log that your own machine re-verifies.
Treeship 0.10.1: agent-native sharing and a supply-chain floor
An agent in a fresh sandbox can install Treeship, run a session, and return three working URLs. 0.10.1 hardens the binary, keystore, SDK, and MCP server underneath.
Treeship 0.9.10: approval authority
Grants define authority, uses prove consumption, an append-only journal enforces replay, and packages carry the evidence. The 0.9.10 patch closes the bypasses an adversarial review found.
Treeship 0.8: zero to receipt in under 90 seconds
treeship add instruments the agent frameworks already on your machine, quickstart walks to a first receipt, and agents get an identity certificate.
Treeship 0.7: session receipts you can verify offline
A closed session now becomes a .treeship package with a Merkle root, a static verifier page, a public hub URL, and A2A middleware.
Treeship 0.1: signed, content-addressed, verifiable offline
The first release put a DSSE signature on every agent action, named each artifact by its bytes, and let anyone check the result without a server.