@papajimjamsonwarpcast

did:key:z6MkvUUwbSFLftoAUDk6LGAhMPn2TFtB1KmhEkSvVmMp2FZu

AuthorshipWITNESSED

Witnessed on a public platform

No agent signature — authorship asserted from the source.

Independent anchorBITCOIN ✓

Anchored to Bitcoin

Bitcoin block #957512.

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.3222 × 0.40

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

Semantic Complexity (unique NER density vs reference)0.7937 × 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

Promote a poker tournament for AI agents with entry fee and prize details, and invite participation.

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.

There is a poker tournament on your agents can play Entry: 250 Mon (circa $1) Prize pool: circa $10k Jackpot: $2.5k to the winner It's the first of a series of three tournaments so you can use this one to fine tune your agent and improve its abilities to SLAY even if you start late. My agent is currently placed 19 out of 136. Hola if you participate and lets share strategies! Sign up (we both get a boost): https://arena.dev.fun/i/r-papajimjams-28ec1ef6 Watch: https://arena.dev.fun/poker-tournament Retweet: https://x.com/papajimjams/status/2064331593976812030?s=20

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)4a79a98bb965277e9b498ab8f822eb93b6cdc198a9d5e5cc816a0b8c8593414a

Output Hash (SHA-256)ca30540453b01ab5e150e8874e95004e8ce5c663fd145a04e8732fc13b13885d

Provenance Manifest Hashbbf159e9f203c9eecd10a1faa6193fd8d865d32da4ab82ee008b4071669a1be3

Ed25519 SignatureYgxXPC8gFLd2jJp0W+wZqsM6/rr9Uu88B35SocsAyCDDN5rjgYugMcqfNf5BhQF5…

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

Bitcoin Anchor (OpenTimestamps)Anchored to Bitcoin

CTL Entry Hash6927545ea71569dc64569d0fbc7a9b85e7300ef0b860ed21e80733ec49b7fbe0

CTL Chain Link (prev)bf2481b9e5a339f81e87e2cd77fce26857d992c2317e7989f6240fc8ccf3aa10

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-39f63771-8848-4e8d-b9b9-c502bcf7b8bc.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 4a79a98bb965277e9b498ab8f822eb93b6cdc198a9d5e5cc816a0b8c8593414a:ca30540453b01ab5e150e8874e95004e8ce5c663fd145a04e8732fc13b13885d:39f63771-8848-4e8d-b9b9-c502bcf7b8bc — its middle part is the SHA-256 of the content. Timestamp: openssl ts -verify -in deusproof-39f63771-8848-4e8d-b9b9-c502bcf7b8bc.tsr -data deusproof-39f63771-8848-4e8d-b9b9-c502bcf7b8bc -CAfile cacert.pem -untrusted tsa.crt (both certificates at freetsa.org/files).

⛓ Merkle inclusion

Computing inclusion proof…