Skip to content
Talk to us

Products outlive companies.Their passports should too.

Scan a product and see its recorded life: what it is made of, where it came from and everything recorded since. The record is public, held on a public blockchain rather than in one company’s database, and anyone with a copy of its evidence can still check it after that company is gone.

  • Cheap
  • Scalable
  • Independent
  • Offline verifiable
  • Open to any reader

Build your own compatible application or service using the DPP standard, specifications and examples.

Yellow Jersey, 2002: a yellow cycling jersey in a studio flat lay
In retail
Checks out

Yellow Jersey, 2002

Maglia Sportiva, Textiles

Made in Como, Italy2002
Sold by Maglia Sportiva2003

Open a passport

How it works

From a tag on the label to the whole story.

01

Scan the tag

Every product carries one: a printed code on the swing tag, or a chip sewn into the seam. A phone camera is the whole reader.

02

Read its story

What it is made of, where it was made, and everything recorded since: serviced, handed on, repaired, repurposed, recycled.

Checks out
03

Check it yourself

Every entry names who it was written for and, once published, carries a reference you can follow to the public record.

See how to check one
Why it holds up

Six reasons a passport on a public blockchain holds up.

Cheap
A fraction of a cent in network fees to publish a passport. Reading and checking one costs the reader nothing.
Scalable
Built on BSV. Each unit has its own record, and the network fee is charged by size, so it does not rise with the number of units you publish.
Independent
No account and no permission from us. The check runs in your own browser, and its two key checks ask a public source we do not run.
Offline verifiable
Each record carries its own proof, so a saved copy can be checked without our services, against block headers you hold. Seeing later changes needs a connection.
Open to any reader
An open standard, GS1 identifiers and a public blockchain, so any software that follows the standard can read and check the record, not only ours.
Products outlive companies
Batteries and garments stay in use for years. The record stays readable after its issuer is gone, for as long as someone keeps a copy of its evidence.
Who it is for

One record, read four different ways.

Go further

Three arguments worth the time.

Independence

The proof has to outlive the software.

A battery lasts fifteen years and a coat lasts thirty. Both will be asked to prove what they are long after somebody’s software has been switched off, so the proof cannot live inside anybody’s software, including ours.

Why checking it does not depend on us
Verification

Five checks, and two of them we cannot influence.

Three read our own copy of the record. Two go to services we do not run, which is the difference between a result you can rely on and a company assuring you of something.

See how the check works
For publishers

Publish once, and let the product answer for itself.

What the coming obligation asks for, which fields it covers, and what it takes to put your products on an open standard rather than inside somebody else’s platform.

Read the commercial case
Who sees what

One passport. Every reader gets their own page.

Approval is decided by the application today; the standard has not yet settled how restricted details other than the owner’s are shared.
What the passport holdsAnyone with the tagThe ownerA service partner
Published to anyone
Materials and compositionSent to this readerSent to this readerSent to this reader
Maker, place and dateSent to this readerSent to this readerSent to this reader
Care, repair and end of lifeSent to this readerSent to this readerSent to this reader
Its life so far, and proof the record is intactSent to this readerSent to this readerSent to this reader
Kept for the owner
Purchase and warranty detailsNot sentSent to this readerNot sent
Sent on approval
State of health, dismantling and declarationsNot sentNot sentSent to this reader
The record behind it

A record that still holds up years from now.

01

One record per unit

Created when the maker registers the unit and named by the identifier on its tag. If two records claim the same identifier, a reader is told rather than handed one.

02

Nothing quietly rewritten

Once published, an entry cannot be edited, and removing one from the middle would show. A correction is a new entry that follows the one it changes, so both stay readable.

03

Verifiable without us

Each entry carries its own reference. Follow it to the public record and check that the entry there is the same, with no account and no permission from this platform.

Sample record, for illustration

Entry 2 of 4

Passport IDdpp.bsvb.net/01/09524182035762/21/15F6F778F0B0
Maker’s identitydid:bsv:bb97…45d8
OwnerPer-passport key
EventServiced by Nordwind
Recorded18 Mar 2022, 14:35 UTC
Reference329346…3ec2d
StatusConfirmed

On the passport, one line: Serviced by Nordwind, March 2022.

Five things anyone can check, in their own browser
  • Which key signed each entry
  • That a publisher the index names stands behind it
  • That no step is missing from the middle
  • That every entry is in a block
  • That an outside source shows the same record
Check a passport yourself
What it is built on
IdentifiersGS1 Digital LinkCredential referenceVSC draftIdentitiesdid:key, did:web and did:bsvRecordPublic BSV Blockchain
Who writes to it

Eight parties, one record, and none of them can rewrite it.

Anyone who handles a product can sign a claim about it without controlling the passport. Nobody can overwrite what somebody else put there, which is what makes the whole of it worth reading.

MakerBrandRetailerOwnerRepairerRecyclerAuditorRegulatorOne record

Publish a sample passport.

Create a brand and publish a sample passport in a couple of minutes. It is a real, public record on the BSV blockchain, marked as sample data, and anyone can check it as soon as it is written. Nothing goes out until you choose.