Writing
#receipts
Every post tagged receipts.
One purchase, three views
A wallet mandate, Anthropic's commerce blueprint, and a Treeship receipt chain. The network sees the amount. The merchant sees the tent. The chain sees the refusal.
Any judge, one receipt
Fast decision models now sit between agents and actions, and none of them leaves a record a stranger can check. Treeship 0.31.6 to 0.31.9 added the judge slot: a contract any judge can speak, a deterministic judge we own, a signed receipt for every answer, and TypeSafe's Jev as the first outside judge behind it.
Ten steps, one receipt
TypeSafe's founder published a ten-step blueprint for building a control system around an LLM with Jev as the decision layer. Step ten is the decision receipt. Here is what Treeship signs at each of the ten, and the two fields we were missing until this week.
Signed is not true
The sharpest attack on a receipt is that a signature proves nothing about the world. It is correct. Here is exactly what a Treeship receipt proves, what it does not, and the three mechanisms that turn a signed report into something you can grade.
Treeship 0.31.2: sealed packages now verify their signatures
package verify checked the Merkle tree and nothing under it. It now verifies every artifact's Ed25519 envelope, session close seals unchained work, and the MCP bridge reports failures.
Treeship 0.31: Verifiable Intent credentials, shipped
treeship vi implements the Verifiable Intent v0.1 draft, signs the Layer 3 pair with a Treeship receipt-chain attestation inside, and interoperates with the reference SDK both ways in CI.
Treeship 0.23: grants you can issue
0.22 taught the verifier to judge delegation chains and effect finality. 0.23 gives the CLI the commands to mint grants and emit the action/v2 receipts those checks apply to.
Robinhood Agentic Trading Needs Receipts
How Treeship can provide local proofs, approvals, and audit trails for agents connected to Robinhood Trading MCP.
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.9.6: the trust fabric
Three-layer file capture, tool usage checked against the agent certificate, and scoped approvals. A receipt can now say whether the agent stayed inside its bounds.
Treeship 0.9: verify a receipt anywhere it lands
treeship verify takes a URL, a package, or an id and cross-checks against an Agent Certificate. The same checks ship as WASM for Node, Deno, edge runtimes, and browsers.
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.