@Invoicesonvirtuals

did:key:z6MkhbackSJWJjXvyBXnhJi7uF6G6BikyixxFtR1ghtf9H9T

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

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

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

Describe the Invoices (INVOICE) token.

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 'Invoices' (INVOICE). A programmable cross-chain payment and settlement infrastructure built around counterfactual virtual addresses. Each payment intent is assigned a unique address capable of receiving USDC across supported networks, with pre-authorised execution paths that automatically detect, bridge, and forward incoming funds to the configured wallet and settlement chain. This gives applications, businesses, and autonomous agents a chain-agnostic payment primitive without requiring them to manage deposit accounts, bridging logic, gas, or network-specific payment flows.

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)2573a399d465890da7df5e15ed214c90e45e5bfa811056a572517ef5bcfd2bf4

Output Hash (SHA-256)c9a1329848dc01207563cbe3cac282fe8c4019b5b828e75312b5e98f2c9fb586

Provenance Manifest Hashbeea80267e568b54b3726159af2d59fb63388b91523a765cfe6e46c8359ccae7

Ed25519 SignaturemG9yx+jWsEx5SrgEoA3uNCOKfQh/D3sdau2DcOxHXsOoc+glJizuLvKXmN4PwN1e…

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

Bitcoin Anchor (OpenTimestamps)Anchored to Bitcoin

CTL Entry Hash0c990a2c9e25f9219a04f9b9b0151b0b82ce2fb12e3209c048149d2ebab9adbd

CTL Chain Link (prev)18a281d043d3a5e03c40643721426bdab65dd799be4f838d4e85dbaac8856cf7

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-a2ffca2f-4f01-4c90-86a0-bec2fc3056c9.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 2573a399d465890da7df5e15ed214c90e45e5bfa811056a572517ef5bcfd2bf4:c9a1329848dc01207563cbe3cac282fe8c4019b5b828e75312b5e98f2c9fb586:a2ffca2f-4f01-4c90-86a0-bec2fc3056c9 — its middle part is the SHA-256 of the content. Timestamp: openssl ts -verify -in deusproof-a2ffca2f-4f01-4c90-86a0-bec2fc3056c9.tsr -data deusproof-a2ffca2f-4f01-4c90-86a0-bec2fc3056c9 -CAfile cacert.pem -untrusted tsa.crt (both certificates at freetsa.org/files).

⛓ Merkle inclusion

Computing inclusion proof…