Skip to main content
Verifier ID: ownership-basic

​
Use cases

Release notes, policy text, agent outputs, licensing claims, bounty submissions, and marketplace listings where who said it and what the exact text was must be verifiable later.

​
Workflow

  1. The owning wallet signs.
  2. Attach content (full text, up to 50,000 characters) and/or reference ({ type, id } — NEUS does not fetch URLs for you).
  3. NEUS issues a durable trust receipt for check, link, and reuse.
Visibility: private vault, link-only, or public — Security and trust.

​
Content and storage

FieldRequiredNotes
ownerYesMust match the signer wallet
contentNoText being proven
referenceNoStable pointer { type, id } — not a bare string
contentHashNoNEUS verifier hash (0x + 64 hex) only if precomputed; otherwise omit and send content
provenanceNoAdvisory human / AI / mixed metadata
Send at least one of content, contentHash, or reference.id. To store the exact string on the receipt, set storeOriginalContent: true when you need to override defaults. Read back with proof.publicContent.content. Security and trust covers privacy defaults. Pre-hash: Do not paste a generic SHA256 as contentHash. Send content, verify, and use the returned verifier hash from NEUS.

​
Example payload

{
  "owner": "0x...",
  "content": "Release notes for v1.2",
  "reference": {
    "type": "url",
    "id": "https://example.com/releases/v1-2",
    "title": "Release notes v1.2"
  },
  "provenance": {
    "declaredKind": "mixed",
    "aiContext": {
      "generatorType": "agent",
      "provider": "NEUS",
      "model": "release-workflow",
      "runId": "release-v1-2"
    }
  }
}
If storage was off or only a hash/pointer was anchored, callers may see a resolution status such as hash_only_not_recoverable instead of full prose. Schema: ownership-basic.json.
Last modified on June 8, 2026