Skip to main content
Verifier ID: ownership-basic Start here: direct-sign receipt (SDK, API, or VerifyGate with a connected wallet). Not an interactive hosted-only flow. Visibility: Security and trust. Use this capability when you need the foundational NEUS proof: a wallet signs a claim and binds it to content, a file, a reference, or a proof-backed action. This is the simplest way to turn authorship, provenance, context, and ownership into a reusable proof receipt.

​
Best For

  • publishing digital ownership
  • content and file provenance
  • source attribution and authorship
  • referenced artifacts and linked context
  • licensing and usage terms
  • bounty and submission receipts
  • marketplace or listing integrity
  • reusable proof-backed identity actions

​
Flow Type

Instant. The signer creates the proof directly after signing the standardized request.

​
What You Configure

FieldRequiredNotes
ownerYesMust match the signer wallet
contentNoHuman-readable content or claim
contentHashNoPrecomputed hash for large or external content
referenceNoURL, IPFS, contract, transaction, or other stable pointer
provenanceNoContext about human, AI, or mixed origin

​
Common Patterns

PatternHow teams use it today
Publish an article or media itemBind the work to a wallet and share the proof page as the portable receipt
Prove a file or artifact existedSign a content hash or stable reference instead of storing large payloads inline
Add provenance to AI or mixed-origin contentPair the proof with provenance metadata and optional safety or human checks
Submit work to a bounty or grantAttach a reusable receipt to the submission instead of re-verifying later
Add trust to a listing or public claimUse the receipt as the integrity layer for the claim being shown
Anchor a proof-backed identity actionReuse the same receipt across profile, app, and marketplace surfaces

​
What You Get Back

You get a proof receipt ID that can be reused for proof pages, product trust, access checks, and downstream policy.

​
Example

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

​
Working With Content, Hashes, and References

  • Use content when the claim is small and human-readable.
  • Use contentHash when the source is large, sensitive, or stored elsewhere.
  • Use reference when the real artifact lives at a URL, IPFS CID, contract, transaction, or another stable pointer.
  • Use provenance fields when downstream readers should understand whether the output is human-authored, AI-generated, or mixed.

​
Content Retrieval

Core Principle: Content retrieval requires either:
  1. Stored original content: The proof was created with content storage enabled in publicContent.content
  2. Stable reference: The proof references external content via reference.type + reference.id
When the same user is signed in, private content can resolve without extra query parameters. Returns contentResolutionStatus: resolved or hash_only_not_recoverable.