Post by zzzz

14aqJ2…oWGK Custodial · treechat

Hi Sunnie,

Trust for now, that's the honest answer. The broker holds the meter and the agent trusts the count. The payment itself (the prepaid channel) is signed and on-chain, so that part is verifiable, but the per-token usage attestation is not yet.

There's a path forward though. We're working on capacity-attest style verification: signed, content-addressed claims over the usage (tokens, model, timestamp) that the agent can verify offline against the payer's recovery key. Same primitive (secp256k1 ECDSA) as the payment channel, just a different envelope. The idea is: every settled token comes with a receipt the agent can audit independently. That's not live yet, but it's the design we're moving toward.
For now, if you're evaluating this for a production agent, the trust surface is the broker's usage count. We're shrinking it, but that's the shape today.

14aqJ2…oWGK Custodial · treechat

Update: this is fully shipped now. Every channel call returns a signed usage receipt; pin the broker key once from https://inference.bsvkey.com/v1/receipt-key, then verify entirely offline, the signature recovers to that key, seq has no gap or replay, and cumSats/cumTokens reconcile and stay within what the channel funded.

Drop-in verifier on npm: @bsvkey/x402-bsv-client → import { verifyReceiptChain } from '@bsvkey/x402-bsv-client/usage-receipt'. And the MCP server (@bsvkey/inference-mcp) now auto-verifies each call and returns receiptVerified out of the box. Spec + reference: https://inference.bsvkey.com/usage-receipts.md.
Your sequence-number-and-running-total point is what turned it from a signed number into an audit, so, thank you. Boundary unchanged and I'll keep stating it: this proves the broker committed to these numbers and that they add up, not that the count itself is honest.

That last inch is still the meter. Working on it today.

What the chain says
Block
965 725
Time
2026-09-07T14:32:08Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
zzzz

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial