xytara 3.5.0 → 3.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/RELEASE_NOTES.md +4 -5
  2. package/package.json +1 -1
package/RELEASE_NOTES.md CHANGED
@@ -1,7 +1,6 @@
1
- `xytara` 3.5.0 makes delegated authority provable at a point in time: the delegation log.
1
+ `xytara` 3.6.1 fixes the delegation log not surviving a runtime restart.
2
2
 
3
- - **Delegation log (`naxytra-delegation-log/1`)** — every agent-key mint (delegatee, key fingerprint, caps, expiry) and revoke (stated time, reason) is an append-only, hash-chained event: `event_sha256 = sha256(JCS(event))`, `chain_hash = sha256(previous chain_hash + event_sha256)`. Mint and revoke responses return the event reference (`delegation_event`).
4
- - **Public, key-less surface** — `GET /v1/delegation-log/head` (count, head hash, chain continuity), `GET /v1/delegation-log/feed?since_seq=&limit=` (seq, type, time and hashes only — never an account, a key or a label), `GET /v1/delegation-log/checkpoint` (a `naxytra-attestation/1` over the head, signed with the delivery-receipt keys; `POST /v1/delegation-log/checkpoint/verify` is a free check). The keys endpoint announces the log.
5
- - **Owner and agent views** — `GET /v1/credits/agents/log` (owner key: the account's full events; agent key: its own) and `GET /v1/credits/agents/:id/proof`: the key's events, the hash-only chain from its first event to the head, the current checkpoint and its digest, plus the verification recipe. A relying party holding a proof and a checkpoint establishes, without asking the runtime, that a key was minted with these caps before T and not revoked before a head anchored after T.
6
- - **Chronology binding on checkpoints** — `XYTARA_EXTERNAL_BINDING_JSON` (the `{scheme, system_id, tag}` object or the bare 64-hex tag, scheme `ctp/1`, system id `NAXYTRA-DELEGATION-LOG/1`) is carried inside every checkpoint's signed bytes while an anchoring session is open; `attestation_sha256` of the checkpoint is the digest an external anchor commits to.
3
+ - **Fix: delegation log restored from the durable snapshot** — the initial runtime state now declares `delegationEventLog`, so a restored snapshot carries the log over (the restore copies only collections the initial state already has; the log was being re-created empty on every restart). Events recorded on the live runtime between a restart and this fix were lost from memory; the hash chain restarts from genesis on the live log, which the public head reports honestly.
4
+ - **Fix: buyer event log restored too** — the same gap applied to the buyer event log and its per-day counters (`buyerEventLog`, `buyerEventDaily`): they were lost on every deploy, so the daily buyer-journey report only ever saw events since the last restart. Both are now declared in the initial state and carried over.
5
+ - The state-guard verifier now asserts every durable collection — provider registry, payouts, settlement ledger, delegation log, buyer event log — is declared in the initial state and survives a restore.
7
6
  - Client package (thin): unchanged.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xytara",
3
- "version": "3.5.0",
3
+ "version": "3.6.1",
4
4
  "description": "Client for the hosted naxytra runtime: discover a capability, pay per call with x402 (gasless USDC on Base) or credits, get the deliverable and a signed delivery receipt you can verify offline. The runtime is a hosted service; this package is the client.",
5
5
  "main": "client.js",
6
6
  "exports": {