The first ten get the author's ear. And this page, permanently.
Every standard has a moment when adopting it stops being brave. Until then, the organizations that move
first deserve more than a thank-you — they get the author's advisory attention and a permanent,
dated place in the history of the standard.
The deal
Who: the first ten pilot issuers (organizations publishing verification
endpoints for documents they stand behind) and the first ten SaaS integrations (products
that emit verifiable documents for their customers).
You get: free advisory support from the standard's author, by email — design
review of your canonical text templates, normalization fixtures, endpoint setup, and revocation
workflow, up to a sensible advice limit: think a handful of focused exchanges that get your team
unstuck, not embedded consulting.
The boundary, stated plainly: this is a personal open-source project run in
evenings-and-weekends capacity — expect responses within a few days, not hours. If your
deployment needs sustained, hands-on implementation work, that's beyond the free scope; I'll say
so when we reach it and can refer you to commercial integration partners.
We get: permission to name you here and in talks/posts about the standard, and
your feedback folded into the spec while it's still cheap to change.
Exit anytime: it's an open standard on your own domain. If you stop, you delete
files — there is no contract, dependency, or fee at any point.
Founding issuers
Paul Hammant — peer reference on paulhammant.com
— the first real-world deployment: a professional reference whose hash is published on the
referee's own website, verified end-to-end on real phones
(iPhone, 0:51 ·
Android, 0:18).
The standard's author, eating the dog food.
Open — could be your registrar's office, licensing board, or certification body.