Skip to main content
Verifier ID: ownership-basic Instant proof: SDK, API, or VerifyGate with a wallet. Visibility: Security and trust.

​
Best for

  • Content and file provenance
  • Authorship and licensing claims
  • Portable verification IDs (listings, bounties, submissions)

​
Payload

FieldRequiredNotes
ownerYesMust match signer
contentNoInclude to persist text in proof.publicContent (same object on standardize + submit; max 50k chars). Omit only if you want hash/reference-only.
contentHashNoPre-hashed body; verifier can integrity-check against content if both sent
referenceNoPointer (URL, IPFS, tx, file id, …). Server does not fetch it. Send content if you need bytes stored.
provenanceNoHuman / AI / mixed (advisory)

​
Persisting text (publicContent)

  • If you send content, NEUS can store it with the proof.
  • Most builders should keep the default private visibility and only change storage behavior for advanced cases.
  • Public proof behavior depends on the visibility options you choose. Start with Security and trust.

​
Example

{
  "owner": "0x...",
  "content": "Release notes for v1.2",
  "reference": {
    "type": "url",
    "id": "https://example.com/releases/v1-2"
  }
}

​
Retrieval

For proofs that expose content, responses can return stored publicContent.content or rely on a stable reference. Responses may include contentResolutionStatus: resolved or hash_only_not_recoverable.