Vision
Redtail is built around a simple idea: records for physical objects should be clear, portable, and independently reviewable without turning Redtail into the authority behind every claim.
Counterfeits and disputed provenance thrive when records are fragmented. Redtail is designed for organisations that need a structured way to publish record data for physical objects, while keeping the responsibility for the record with the organisation that issues it.
Redtail does not replace the role of the issuer. The organisation using the account creates the record, publishes the information, and remains responsible for the claims attached to that record. Redtail provides the infrastructure for publishing and verifying that record data; it does not itself certify authenticity, ownership, condition, custody, value, legality, or provenance.
From ownership claims to clear provenance records
Trust breaks when documentation is scattered. A provenance record should be a clear, shareable description of what an item or document is, who created the record, what evidence supports it, and where it can be reviewed.
The information in a record is provided by the issuing organisation through its Redtail account. The organisation remains responsible for the claims it publishes.
Provenance that grows over time
A provenance record should not be a single static PDF that disappears in an inbox. Over time, it can carry a sequence of events the issuer chooses to publish — issuance, appraisal, restoration, transfer, and other events that add context as an object moves between people, institutions, and systems.
Starting where provenance matters most
Redtail starts with object categories where provenance directly affects trust, review, and price: artworks, limited editions, luxury objects, and documents of record. The organisations using Redtail to publish records about these objects include galleries, brands, auction houses, and institutions.
These are workflows where information needs to be fast to review, consistent across organisations, and portable enough to move with the object rather than stay locked inside a private folder.
Simple to create. Easy to review.
A record should be simple for an organisation to create and clear for someone else to verify. The public verification page exposes the record data and the anchor metadata — record ID, anchor timestamp, block number, transaction hash, chain identifier — needed to review the record independently.
The goal is not to add ceremony. The goal is to make the record easier to inspect than a screenshot, PDF attachment, or private spreadsheet.
A note on proof
Redtail helps create and share provenance records and supporting materials. An on-chain transaction hash can confirm that a transaction executed at a point in time, but it does not replace expert authentication, appraisal, regulatory certification, or legal proof of ownership.
Verification means that the published record and its recorded metadata can be reviewed against a public anchor. It does not mean Redtail has independently authenticated the physical object, confirmed who owns it, or assessed its condition, custody, value, legality, or regulatory compliance. The organisation that issues the record is responsible for those underlying claims.
Built for portability
Records should travel with the asset. Over time, we want records to move easily across galleries, auction houses, resellers, insurers, and marketplaces. Redtail is designed around stable IDs, structured data, public verification pages, and a record model that remains useful outside a single private workflow.
Driven by utility
The product is built around practical outcomes: fewer disputes through clearer records, less fragmented documentation, and faster review when objects move between people, institutions, and systems.
Physical value deserves durable provenance.
Last updated: 06 May 2026