CRYPTO price, saved and checkable

Provenance for every timeline entry

• EXECUTED BY ZAMBOZambo ran the tool call itself.
• OBSERVED VIA GATEWAYA Zambo gateway observed request and response bytes from the named external executor. Zambo did not run that external action.
• LOGGED BY AGENTAn agent or local hook reported the action. Zambo attests that the record is unchanged since logging, not that the action happened as described.

Private agent reasoning, built-in client actions, and direct calls to unrelated MCP servers are not included unless an agent or gateway reports them.

What is this receipt?

This is a verifiable receipt for a journal entry. It confirms receipt, redaction, timestamping, and chaining. It does not attest to execution.

What is this?

Zambo's receipt store reports a journal entry from an agent or local hook. The SHA-256 commitment covers the receipt bytes. The provenance label is only a claim, not proof of issuer identity or that the reported action happened.

Verification checks

• SHA-256 commitment: Checked independently against the exact decoded bytes
• Provenance binding: PASS; The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.
• Metadata binding: PASS; metadata_hash matches the canonical metadata block.
• Issuer authentication: NOT CHECKED; no pinned signing key or trusted issuer was supplied
• Signature: NOT CHECKED; no Ed25519 signature or pinned key is supplied
• Chain: NOT CHECKED; no append-only chain proof is validated
• Stored timestamp: 2026-11-11T01:23:07.777Z; external immutability is not checked

Committed provenance claim

LOGGED BY AGENT

The metadata claim is consistent with the verified receipt bytes; issuer is not authenticated.

Receipt ID

9b4968a0-3566-4990-9554-92a3bd5b2b58

SHA-256 output hash

sha256:37783e62bc0c1789c85c7e2847e5726865ccfc5229c80c3fd67e472bfb6804ef

Canonical bytes

eyJjYWxsZXIiOnsiaWQiOiJzaGEyNTY6MzUxM2JkMGZlZTQyZTk0MGU1MDlhNTI2ODc3MjM0YTYwZjg3ZjI4NTg1N2ExY2VjMmFmNWMwN2NlYmVkZDEzZSIsInR5cGUiOiJzZXNzaW9uIn0sImlzc3Vlcl9jbGFpbXMiOnsicHJvdmVuYW5jZV9jbGFzcyI6IkxPR0dFRCBCWSBBR0VOVCJ9LCJvdXRwdXQiOnsib3V0cHV0IjoiQlRDIMK3ICQ3Myw0MzQuNDAgVVNEXG7ilrwgMi4wNyUgKDI0aCkgwrcgTWFya2V0IGNhcDogJDE0NzUuODhCXG5cbkxpdmUgcHJpY2Ugc25hcHNob3QgdmlhIENvaW5iYXNlIMK3IGZldGNoZWQgV2VkLCAxMSBOb3YgMjAyNiAwMToyMzowMSBHTVQgwrcgY2FjaGUgYWdlIDNzIiwicmVkYWN0ZWRfcHJvamVjdGlvbiI6dHJ1ZSwic291cmNlX2NvbW1pdG1lbnRfY2hlY2tlZCI6dHJ1ZSwic291cmNlX291dHB1dF9oYXNoIjoic2hhMjU2Ojk1ZWMzNjk2N2Y4MDQ4MzE5OTY2NTMxYzRhN2RkNGZhNzVmYzJkN2ZhOGZlZjE3ZTU1NjczZGM2ZjhjODc4OWMiLCJzb3VyY2VfcmVjZWlwdF9pZCI6IjcyZmVjNjQ1LTQyYzctNDA3My05NDFjLTllMzVjMmQ5M2YzYiJ9LCJyZWNlaXB0X3NjaGVtYV92ZXJzaW9uIjoiMC40Iiwic2lkZV9lZmZlY3RzIjp7ImRlY2xhcmF0aW9uX2hhc2giOiJzaGEyNTY6NDVhYWQzOGYzYWE5ODJiOWFhZmU5MmVjYjQxNmViZTk4NzkxZWRkYmFmOGFiNmRmMGJkMDg2MDViN2MxYmZlZSIsImRlY2xhcmVkIjpbIm5vbmUiXSwic2NoZW1hX3ZlcnNpb24iOiJ6YW1iby1zaWRlLWVmZmVjdHMvMSJ9LCJ0b29sIjp7Im5hbWUiOiJsaXZlX3ByaWNlIiwic2NvcGUiOiJwdWJsaWMiLCJ2ZXJzaW9uIjoiNC4xLjAifX0=

Timestamp

2026-11-11T01:23:07.777Z

Bound call context

Receipt schema

0.4

Tool name

live_price

Tool version

4.1.0

Permission scope

public

Caller type

session

Caller ID

sha256:3513bd0fee42e940e509a526877234a60f87f285857a1cec2af5c07cebedd13e

Declared side effects

none

Side-effects schema

zambo-side-effects/1

Declaration hash

sha256:45aad38f3aa982b9aafe92ecb416ebe98791eddbaf8ab6df0bd08605b7c1bfee

This records what the server-side tool contract declared at call time. It does not independently verify that a downstream side effect happened.

Bound upstream evidence

Status

empty

Evidence SHA-256

unavailable

Byte length

unavailable

Neutral Nostr anchor

Event ID

5e4e86c8d718e037c98cb6f7f371b6454d806ab69dcd812616edc7bdf3158191

Anchor status

published

Public key

e13475107d30c918ec664adf2ab1141024a22fb35190f82c9e933704fa49af41

Relay hints: wss://relay.primal.net

Schema: zambo-receipt-anchor/1

Anchor envelope bytes:

{"anchored_at":"2026-11-11T01:23:07.777Z","evidence_byte_length":null,"evidence_sha256":null,"evidence_url":null,"output_sha256":"sha256:37783e62bc0c1789c85c7e2847e5726865ccfc5229c80c3fd67e472bfb6804ef","receipt_uuid":"9b4968a0-3566-4990-9554-92a3bd5b2b58","schema_version":"zambo-receipt-anchor/1"}

Anchor status "published": Published to all configured relay targets.

Relay publication is separate from receipt integrity. When the original signed event is available, Zambo retries pending, partial, or failed anchors about once a minute. Relay acknowledgements are external, so there is no guaranteed completion time; the receipt remains checkable from its saved bytes and verification link.

Check this hash yourself

Receipt commitment: commitment matched; issuer, signature and chain not checked. This checks the saved bytes, not whether the answer was correct. Recompute the SHA-256 commitment in your browser. Open the API v2 JSON response to inspect the machine-readable checks. See the Nostr anchor event on a public viewer. The fingerprint is timestamped outside Zambo too.