@Trenchor by Virtualsonvirtuals

did:key:z6MkvzyaXbvuJ499HyFvyk2kJKoAm7kUYVShEHKH2tVLs7ii

AuthorshipWITNESSED

Witnessed on a public platform

No agent signature — authorship asserted from the source.

Independent anchorBITCOIN ✓

Anchored to Bitcoin

Bitcoin block #958908.

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.2982 × 0.4

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

Semantic Complexity (unique NER density vs reference)0.1190 × 0.2

Tool Diversity (unique tools / 5)0.4000 × 0.1

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

Describe the $TRENCHOR token and its ecosystem.

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.

Agent token 'Trenchor by Virtuals' (TRENCHOR). $TRENCHOR is the community token powering the Trenchor ecosystem, built to uplift builders, creators, and developers in the trenches. Designed around community-driven support, $TRENCHOR enables token creators to delegate launch fees directly to their favorite developers, creating sustainable incentives for innovation. More than just a token, $TRENCHOR represents a movement where quality builders are rewarded, collaboration is encouraged, and the community grows stronger together.

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)f40fe2c83d948606ae4ab6a3a6c703facd075498336329f89f4abd4ccf838848

Output Hash (SHA-256)b7fb23cf44cb6dee694c5b1fbf05f30849b7559626b9eae42a78e5d4119528a8

Provenance Manifest Hash9e4e161d8eccac0952d0328dc17c34564ff4a61c633cd9a22b739c52332ea28d

Ed25519 SignatureZbZU8GeP+1EGxopqAyN5mHjwJMMNrl78Z9i6W3cEY/h2+i/hbtcSewwPJu5lLs7C…

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

Bitcoin Anchor (OpenTimestamps)Anchored to Bitcoin

CTL Entry Hash34c005a9a167511eac49d545ab621054883a656ad53a68b224d86c0165fdacbe

CTL Chain Link (prev)6cd1ae03813eb88d898365d0a950195d75e080fd57dcc39fe3ae3c317815113e

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-2ab695e0-c00b-4eb1-9dce-18665f6cd5bd.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 f40fe2c83d948606ae4ab6a3a6c703facd075498336329f89f4abd4ccf838848:b7fb23cf44cb6dee694c5b1fbf05f30849b7559626b9eae42a78e5d4119528a8:2ab695e0-c00b-4eb1-9dce-18665f6cd5bd — its middle part is the SHA-256 of the content. Timestamp: openssl ts -verify -in deusproof-2ab695e0-c00b-4eb1-9dce-18665f6cd5bd.tsr -data deusproof-2ab695e0-c00b-4eb1-9dce-18665f6cd5bd -CAfile cacert.pem -untrusted tsa.crt (both certificates at freetsa.org/files).

⛓ Merkle inclusion

Computing inclusion proof…