Protect the original from silent alteration.
Verification checks the artifact’s binding and supported proof. A changed file cannot stand in for the verified original when it breaks that proof.
RECEIZ
ASSETSEAL · OFFLINE VERIFIABLE · PUBLIC VERIFIER
Origin verified. Custody appended.
For assets with long timelines, use a file that verifies itself.
AssetSeal issues a single provenance record for an asset’s origin, then records custody as append-only events — without rewriting the origin seal.
Explore the working example, or open your Receiz ID to work with your assets. Package verification needs no account.
THE ASSETSEAL WORKSPACE
The machine keeps the receipts.
Establish an asset’s origin with your Receiz ID. Record work, capture photos and video, and keep component history and evidence with the same durable asset subject. Export the sealed workspace so its carried history can be verified independently.
Identify the asset
Generate a tag, scan it in the field, and open the held asset record.
Preserve the work
Append owner-authorized lifecycle records and carry the original evidence.
Carry the proof
Export all workspace assets and attachments. Verify the exact package without an account.
Explore the labelled industrial example or open your Identity Seal. Existing origin certificates and custody records remain available through the entrances on this page.
Origin certificates and custody records
Create an origin certificate, continue your existing records, or verify an original file. Your existing certificates and verifier links remain available.
THE VALUE / Assets & Custody
Keep the origin. Carry the history.
Give the next custodian a verifiable origin record and recorded custody history that remain inspectable beyond a listing, dashboard or handoff.
The asset’s record travels. Its authority stays with the original.
Origin and recorded custody do not have to depend on the continued availability of a listing or registry view. The proof object carries the authoritative record and its verified additions.
THE SOURCE
A proof object carries its own record.
Each proof object is the append-only database for its identity and governed history. Verified additions extend that history. Servers and databases may transport, index and replicate the objects; they do not replace their proof authority.
- Hold the complete original
- Verify its enclosing proof
- Inspect its carried record
Check held proof without a live database lookup.
With the complete artifact and canonical verifier resources, offline verification establishes its proof without asking the originating service to confirm it.
Design the handoff around what is needed.
Choose the complete proof objects each authorized participant receives. A scoped workflow can reduce repeated collection and unnecessary copies without making one party custodian of everyone’s complete history.
The next custodian receives the complete proof object and checks its carried origin and history. Physical inspection and custody decisions remain grounded in the evidence and the authorized handoff.
FROM SOURCE AUTHORITY TO A DECISION YOU CAN INSPECTIntelligence you can trace.
Intelligence you can trace.
Decisions you can inspect.
A connected view helps people understand the work. Receiz keeps the evidence beneath that understanding independently checkable: the original carries proof, supported tools project its content, and the responsible person or organization decides what to do.
- PreserveKeep the exact source as a sealed proof object.
- VerifyCheck the enclosing artifact before relying on its carried content.
- UnderstandInspect selected evidence through compatible readers, Mind or AI tools.
- DecideKeep the authorized decision connected to its supporting sources.
- Carry forwardRetain the originals and verified additions for the next review.
Source, interpretation and decision retain distinct roles. A model response or operational view cannot rewrite the original evidence or manufacture its proof.
End-to-end organizational workflows require qualified source connectors, permissions, decision owners and operational actions. Installing the tools does not automatically connect every system or seal every AI response. Measure evidence preparation, repeated source requests and time to reconstruct the decision basis.
What protects the data—and what does the workflow still govern?
Integrity: sealed proof makes the original checkable. It does not by itself establish the truth of every factual claim in the content.
Confidentiality: who can read a record depends on its actual encryption, access and sharing controls. Sealing alone does not make content private, and sharing a readable original shares its carried content.
Custody: define source selection, permissions, retention and recipient responsibilities. Independent verification does not remove records you must retain or deployment-specific data obligations.
Continuity: offline verification checks the held artifact and its carried history. Discovering later additions and using connected services retain their own network and access requirements.
An asset changes hands. Photos, certificates and handoff notes live in separate places. The receiving team must establish which record belongs to the asset and what the recorded history contains.
The origin seal remains the reference. Custody events append without rewriting it. The receiving team verifies the original and inspects the carried history before accepting the handoff.
Preserve the starting point
Keep the original provenance record intact through resale, storage and later review.
Make handoffs inspectable
Give the receiving custodian the source record and recorded events supporting the handoff.
Carry proof beyond the system
Retain the original file for independent verification, including offline.
ILLUSTRATIVE WORKFLOW
One record through the next handoff.
An asset enters storage with its identifying details and supporting records. Later custody events record its movement. A receiving custodian checks the same origin and the recorded sequence.
Inspect an original in Verify →- 01Origin record and identifying details
- 02Supporting photographs and documents
- 03Recorded custody events
- 04Original proof object for independent verification
MEASURE THE DIFFERENCE
Start with one workflow. Compare the work it takes.
- Time to assemble provenance evidence
- Handoffs returned for missing records
- Time to verify an exported original
Compare the same evidence requirements before and during a scoped pilot. These are measurement targets, not claimed customer results.
Verification establishes the sealed record’s integrity and supported proof. Physical identification, inspection and the truth of an underlying asset claim require the relevant evidence and responsible assessment.
Where AssetSeal fits
One surface to verify. Three levels of depth.
Authenticated identity includes attachments • verification stays public
RECEIZ
Sealed integrity
A portable file that stays intact. Anyone can verify it. No account required.
Verification stays public and free.
ASSETSEAL
Provenance + custody
Seal origin once, then append custody events. The first seal never changes — the record only grows.
Authenticated proof + custody
AUTHENTICATED CORE
Archive + operations
Authenticated identity includes AssetSeal attachments, signing, custody, archive, and non-AI WireProof API/webhook operations.
AssetSeal and non-AI WireProof are authenticated core primitives
Collector checklist
When you’re acquiring an asset
Minimal by design • verification does the work
01
Ask for the file
Screenshots fail. Originals verify.
02
Verify directly
Drop it into Verify. You get a deterministic verdict — online or offline.
03
Confirm custody
Origin is sealed once. Custody is append-only. Missing links are visible by design.
01 · SEAL
Seal the origin
Create the source-of-truth record the moment the asset enters custody. That first seal becomes the reference.
- • Photos + identifying marks (serials, inscriptions, grading refs)
- • Optional attachments (certs, invoices, appraisals)
- • Verifier link + QR for checking
02 · CUSTODY
Append custody events
Custody doesn’t edit history. Each handoff is recorded as a new event — auditable over time.
- • Sale, consignment, loan, vault intake, insurance events
- • Optional co-sign (gallery, appraiser, vault, insurer)
- • Clear progression: origin → custody → current custodian
03 · VERIFY
One file. One verdict.
Verify independently.The file verifies itself.
- • Cryptographic integrity check (tamper = fail)
- • Custody validation (missing link = flagged)
- • Offline verification supported
WHAT IT STOPS
Paper you can’t trust
Counterfeits thrive on editable documents and unverifiable provenance. AssetSeal replaces “trust me” with a file that verifies itself.
- • Altered PDFs / swapped photos / reprinted certificates
- • “Same docs, different item” listings
- • Retroactive edits and missing custody links
WHAT YOU GET
A clean public surface
Verification stays public. When you need more detail, you can attach deeper evidence without changing the public truth.
- • A shareable verifier link + QR
- • Optional attachments for audits and disputes
- • Exportable records for vaults, insurers, and collectors
Collectors
Keep provenance intact across resale, storage, and inheritance.
Galleries & Dealers
Issue origin + custody in a form collectors can verify independently.
Vaults & Insurers
Public verification + append-only custody + exportable audits.
READY
Give the asset a history that travels.
Open your Receiz ID to create. Verify a package without an account.