Digital product passports on the BSV blockchain
A digital product passport links a product to a signed record of its history. On the BSV blockchain, each change to the record is a transaction, so anyone can check the history without trusting the application that shows it. This fits an application that must prove who signed each record and in what order. In this guide you learn how the pieces fit, check a test passport on your own machine and read its verification report.
Before you begin
You need Node.js 22 or newer, npm and git. This guide needs no wallet, no testnet coins and no transaction.
The DPP standard is a working draft before version 1.0, so its packages and details can change. This guide explains the model and links to the DPP docs for each detail. The commands were tested with the DPP source at commit 243c060.
How it works
A passport keeps two separate chains of transactions, called rails. The passport rail holds the passport’s own states, and each new state spends the one before it, so the history has one order. The claim rail holds anchors for claims, such as a repair or a recycling, which a party signs away from the chain and commits to with a small transaction:
Signs each state with a wallet. A new state spends the one before it.
Admits the state and finds it again by the passport identifier.
Signs a claim about the product, such as a repair, away from the chain.
Keeps the claim, and an anchor transaction commits to the claim's exact bytes.
Gets the states and the claims, then checks signatures, links and proofs itself.
A source the reader chooses. Nothing is believed because a service said so.
What a reader checks
The index and the registry only find and keep records. A reader checks the signatures, the links between states and the proof that each transaction is in a block, using block headers from a source it chooses. The index is an overlay serviceBuilt from topic managers, which decide what is admitted, and lookup services, which query what was admitted., as in Track transactions with overlays. The proofs work like the ones in BEEFBackground Evaluation Extended Format, the binary format that sends a transaction together with its proof (BRC-62), and identity keys work as in Authenticate users with their wallet.
Address and product data
A passport is named by a web address, commonly https://HOST/01/GTIN/21/SERIAL, where GTIN is the GTINGlobal Trade Item Number of the product and SERIAL identifies the item.
The record carries product data, and a profile chooses its fields. The standard has a general profile and profiles for batteries and textiles.
What a signature proves
A valid signature is narrower evidence than it looks. Two limits matter when you show a passport to a user.
Identity
A valid signature shows which key signed a state or a claim. It does not show who holds the key, that the signer may make the statement, or that the product is genuine. Today the application that registers a signer is the only party vouching for who the signer is, which the DPP docs call Ring 0. Show a brand or issuer name as that application’s statement, not as a checked fact.
Regulation
The standard also does not claim conformity with any regulation. Its battery and textile profiles map fields to the EU Batteries Regulation and the Ecodesign for Sustainable Products Regulation, and those mappings have not been assessed.
Check a test passport
The DPP repository includes a five state test passport. In these steps you check it offline, from its raw transactions.
Get the code
Clone the DPP repository and build it:
git clone https://github.com/bsv-blockchain/dpp.git
cd dpp
npm ci
npm run buildRun the check
Run the check from the root of the dpp folder. It verifies the passport from its raw transactions:
node examples/verify-passport.mjs --fixture --version=2 --reportThe first lines name the five states and the result, with long lines shortened here:
Fixture chain (record version 2): 5 states, verified from raw transaction hex, ...
Operations, genesis to tip: ISSUE -> UPDATE -> TRANSFER -> UPDATE -> RETIRE.
State 1 (ISSUE, a39a87ffca41): user signature verifies; linkage holds; inclusion pending.
...
The chain as a whole is valid.
Inclusion across the chain: pending (a proof the verifier could not evaluate ...)The output goes on with the refusal cases and the report cases of the test passport, and the command ends with exit status 0.
Read the result
Each state shows that its signature verifies and that it links to the state before it. Inclusion is pending because the test transactions are not on the chain, so there is no proof to check. That is missing evidence, not a failed check.
The ok: lines for refusals are checks that held: the verifier refused a deliberately broken input, as it should. A line that starts with FAIL: or FAILS: means something is wrong, and the command then exits with a non-zero status.
Read the verification report
A verification report has sixteen checks and no single yes or no. Each check answers with one of four statuses:
pass: the check ran on the evidence and heldfail: the check ran and did not holdunknown: the evidence, source or policy needed to finish the check was missing, and the reason code says whichnot-applicable: the profile or policy says the check does not apply
Decide what to trust by naming the checks your use needs, and show each finding instead of one badge. Read the verification report explains every check.
See it in a browser
The DPP team runs a hosted demonstration with a sample passport and a verifier, where you can check a passport by its identifier.
The demonstration uses sample data only. Its three open sample brands write nothing to the blockchain. A signed-in user who creates a brand writes real Mainnet transactions that cost satoshisThe smallest unit of BitcoinSV (BSV). 100,000,000 satoshis make 1 BSV, and a blockchain transaction cannot be reversed, so do not create a brand just to try the page.
Troubleshooting
Cannot find module #
The build did not finish. Run npm run build again in the dpp folder and read the first error it prints.
Next steps
With the model and the report clear, continue in the DPP docs:
- Verify your first passport
- Build or integrate
- Product data profiles
- Plan your platform
- Known limitations and open questions