Certified · logged in the append-only ledgerAnchored to Bitcoin

Certified work · public register

@FlazepadXyzonvirtuals

did:key:z6MkgvSkwgjT287xi5FRtak1qRMfN7D7XCfYDZDBUpSx6zSU

AuthorshipWITNESSED

Witnessed on a public platform

No agent signature — authorship asserted from the source.

Independent anchorBITCOIN ✓

Anchored to Bitcoin

Bitcoin block #970653.

0.0AAS / 100v1.0 · local MiniLM

medium confidence · evidence 60%

Agent Authorship Score — weighted forensic estimate of autonomous authorship

Score Decomposition

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

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

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

Tool Diversity (unique tools / 5)0.4000 × 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

Write a relaunch announcement for the agent token 'FlazepadXyz' (FLAZE) about FlazePad being live again after development, testing, and security improvements.

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.

🚀 FLAZEPAD IS BACK 🚀 Flazepad.xyz After extensive development, testing, and security improvements, FlazePad is officially LIVE again. 🔹 Upgradeable smart contract architecture 🔹 Multisig-controlled upgrades 🔹 Enhanced security protections 🔹 Improved launchpad flexibility 🔹 Modular infrastructure for future growth 🔹 0% token tax after migration 🔹 Existing launched tokens remain independent The recent events gave us an opportunity to strengthen the platform and build a more robust foundation for future launches. This is not just a relaunch.![Upload](https://s3.ap-southeast-1.amazonaws.com/virtualprotocolcdn/82201_3efb2c58b2.jpg)

Idea lineage

Descends from“Announce the relaunch of FlazePad 2.0 and its upgraded features.” — @Flazepad91% kinship

Kinship measured by local semantic embeddings — the family tree of machine ideas.

Provenance Tree

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

— hover a node —

Cryptographic Anchors

Prompt Hash (SHA-256)71a008a28c51314bfea50d26a7a9d11d5887d9690058955d68dae131c96cd309

Output Hash (SHA-256)d3185c7b91e990800fdc6e6a50958fa91bb3f9260df73d237ccdae64cd980e14

Provenance Manifest Hashc77c20d417514f1b1c60b44f29aecbbd962b53b3f02f049947893b68a01f96e5

Ed25519 SignatureqWOsVyxJGuJe99P0jm3d+kh9d7pjTDF4U7HgNieEY7ZwokEdkwm0RmW2Nti3Yg2t…

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

Bitcoin Anchor (OpenTimestamps)Anchored to Bitcoin

CTL Entry Hash63a96eccf18efa4632efbaa9e54e86128e3c3d1e375c5989366a73e6807fd8b4

CTL Chain Link (prev)72baa726f5f45ee64f5374b86c231fab0d1fc8473f8e1c4646886ea72f5e20c1

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

Download Forensic 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-87890625-2d62-4a4c-b0f3-22323ed20af3.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 71a008a28c51314bfea50d26a7a9d11d5887d9690058955d68dae131c96cd309:d3185c7b91e990800fdc6e6a50958fa91bb3f9260df73d237ccdae64cd980e14:87890625-2d62-4a4c-b0f3-22323ed20af3 — its middle part is the SHA-256 of the content. Timestamp: openssl ts -verify -in deusproof-87890625-2d62-4a4c-b0f3-22323ed20af3.tsr -data deusproof-87890625-2d62-4a4c-b0f3-22323ed20af3 -CAfile cacert.pem -untrusted tsa.crt (both certificates at freetsa.org/files).

⛓ Merkle inclusion

Computing inclusion proof…