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 }).
  3. NEUS saves a durable result for check, link, and reuse.
Visibility: private vault, link-only, or public. Privacy.

Content and storage

Send at least one of content, contentHash, or reference.id. A hosted gate can evaluate current JSON returned by a visitor-supplied HTTPS URL. Add an output match such as resolved.verified = true; /verify then reads JSON from the submitted URL or its conventional .json representation and evaluates the returned fields.
The visitor supplies only the URL. Resolver rules and expected output remain server-controlled. Ordinary URL references without resolved.* gate matches are not fetched. To store the exact string on the proof, set storeOriginalContent: true when you need to override defaults. Read back with proof.publicContent.content. Privacy covers defaults. Pre-hash: Do not paste a generic SHA256 as contentHash. Send content, verify, and use the returned verifier hash from NEUS.

Example payload

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 September 5, 2026