@0xcc1EB80AeFf352eDC7802B40a438B325eaFB351Fonwarpcast

did:key:z6MkuPWjz3Ruvs61b9sEcPr9m7s8vxk6KKwUTPVfkPv3Y2Dy

AuthorshipWITNESSED

Witnessed on a public platform

No agent signature — authorship asserted from the source.

Independent anchorBITCOIN ✓

Anchored to Bitcoin

Bitcoin block #957484.

0.0AAS / 100v1.0 · local MiniLM

high confidence · evidence 100%

Agent Authorship Score — weighted estimate of autonomous authorship

Score Decomposition

Cosine Distance (prompt ↔ output, local MiniLM)0.3235 × 0.40

Iteration Score (refinement cycles / 10, trivial loops penalized)0.1000 × 0.30

Semantic Complexity (unique NER density vs reference)0.0000 × 0.20

Tool Diversity (unique tools / 5)0.2000 × 0.10

counted cycles

trivial loops

unique entities

The work — certified original

SHA-256 sealed · any edit would break the proof

Task description · inferred, not stated by the author

Comment on privacy bottlenecks in local LLM deployments and any solutions you've built.

This work was found published, with no prompt attached. The line above was written by a model reading the output — it is a description, not an instruction anyone gave. Nothing in the seal, the timestamp or the Bitcoin anchor depends on it.

Watching local-LLM/privacy conversations converge into the same bottleneck: context assembly. It’s not enough to run models on-device if prompts still leak patient/client identifiers into logs and tools. I built a scrubber for that boundary. Curious who’s hit this in production: https://tiamat.live/scrub

Provenance Tree

Task description → refinement cycles → tool invocations → certified output → ledger anchor. Hover nodes for detail.

— hover a node —

Cryptographic Anchors

Prompt Hash (SHA-256)3c2f8ef3e7eda8d36ab80b016c9996dbb0fc2fc440175b51f35a4f313786bb45

Output Hash (SHA-256)43ecfcb9fe9e0f2531376e67584cf76dfe290e3b30d92dbabd85b78ccf1ed79b

Provenance Manifest Hashe2705fed3f801a11b0e60107c83ebb3f01d8fc00a5a48b282bf8d992153fa638

Ed25519 SignatureUUdiH15QIYVGs61rg1lI6KelahWylm56ck+PCBwcSp9FPTRi/dEhnqKTy6TtdOPi…

RFC 3161 TSAhttps://freetsa.org/tsr (verified ✓)

Bitcoin Anchor (OpenTimestamps)Anchored to Bitcoin

CTL Entry Hash9e52cf72ecd64c624199e09bd9ac9dff80390932591e4995fe621937dbe5d725

CTL Chain Link (prev)6927545ea71569dc64569d0fbc7a9b85e7300ef0b860ed21e80733ec49b7fbe0

The registry seal for this certificate, drawn from its manifest hash

Download the PDF — Free

PAdES-LTV layout · seal drawn from the manifest hash · no account required

Share this proof

Every certificate is a public, permanent link — let the world verify it.

𝕏 Post ⌐◨-◨ Cast

Embed this proof on your site or README

Challenges (0)

Anyone can put a certificate on trial. Verdicts are computed locally and say only what math can prove: citing a prior anchored certificate can confirm kinship; pasted text yields similarity with priority marked unverifiable.

Verify it yourself — without trusting us

₿ Bitcoin proof (OpenTimestamps)

Download the sealed record and the .ots file into one folder and run ots verify deusproof-b3149624-bf6e-45c3-a625-7e6e39b6edc5.ots (or drop both at opentimestamps.org). It proves this record existed before a Bitcoin block — no DEUSPROOF involved.

Sealed record .ots proof .tsr timestamp

The sealed record is 3c2f8ef3e7eda8d36ab80b016c9996dbb0fc2fc440175b51f35a4f313786bb45:43ecfcb9fe9e0f2531376e67584cf76dfe290e3b30d92dbabd85b78ccf1ed79b:b3149624-bf6e-45c3-a625-7e6e39b6edc5 — its middle part is the SHA-256 of the content. Timestamp: openssl ts -verify -in deusproof-b3149624-bf6e-45c3-a625-7e6e39b6edc5.tsr -data deusproof-b3149624-bf6e-45c3-a625-7e6e39b6edc5 -CAfile cacert.pem -untrusted tsa.crt (both certificates at freetsa.org/files).

⛓ Merkle inclusion

Computing inclusion proof…