Publicly verifiable receipts for AI agent actions, anchored to Bitcoin

Jul 23, 2026 · 4:10 AM UTC ·1 min read · 0 reactions · 0 comments · 14 views

An agent's self-reported log proves nothing. A Bitcoin-anchored receipt proves the record existed, unmodified, at a point in time — and anyone can check it without trusting the operator.

About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 3,312 of its stories.

All Hacker News (AI / LLM) coverage →

Original article

Orphograph

Read full at Orphograph →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Orphograph
Canonical URL	https://orphograph.com/lp/agent-receipts
Publication time	Thu, 23 Jul 2026 04:10:35 +0000
Retrieval time	2026-07-23T04:57:25.848Z
Last seen	2026-07-23T04:57:25.848Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	None yet
Summary source text	contentText
Citation coverage	No WeSearch summary has been generated for this story yet.
Cluster	FkiG_G5HwAGC
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

Your AI agent did something. Prove exactly what, and when. For operators running autonomous agents that take consequential actions — and for the clients, counterparties, and reviewers who have to accept that work.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Orphograph.

Anonymous · no account needed

Discussion

0 comments