Verifiable credibility · Midnight Buildathon
Credibility
you can prove.
Vero is a verifiable credibility layer for people and organisations publishing online. Prove a relevant credential or accountability claim — and choose what you reveal.
The source chooses what to reveal. Identity can stay private — only the credential-backed fact becomes public.
01 — the problem
Publishing is easy.
Credibility is harder to prove.
Anyone can publish. Not every source can prove what qualifies them to speak with authority.
Prove platform approval.
A checkmark tells you that a platform approved an account. It doesn't prove professional credentials or expertise.
Prove where content came from.
Provenance systems can show how content was created or changed. They don't necessarily prove the credentials of the source behind it.
Prove qualifications.
Professional credentials already exist — but they are rarely portable, cryptographically verifiable trust signals on the open web.
Vero connects these worlds by turning credentials into verifiable trust signals.
02 — mechanism
Verifiable credibility,
by design.
Vero turns existing credentials into cryptographic proofs. The source decides how much of the underlying information to reveal.
Holds a credential
A professional licence, organisational credential, or accountability claim — issued by a recognised body. It stays on the source's side.
Compact circuit
Proves the credential is one of those in the issuer registry, and that it has not expired. The credential itself is never submitted — and the proof does not reveal which registered credential it is.
Choose what to reveal
The source discloses only what it chooses. Identity can be public, associated with an organisation, or private.
Reader sees it
The frontend reads the ledger and shows the verified signal next to the source or post.
Identity and credibility don't have to be the same thing.
03 — scope
What Vero verifies —
and what it doesn't.
Verifies
- ✓ Valid professional credentials — accredited journalist, licensed doctor, registered accountant, licensed engineer, other recognised professionals
- ✓ Recognised organisations — news outlets, research organisations, companies, crypto/Web3 organisations
- ✓ Credential validity — the credential is registered by a recognised issuer, and is not expired
- ✓ Accountability claims — an organisation can prove it is a recognised entity willing to stand behind what it publishes
Doesn't verify yet
- × Whether a specific claim is true
- × Whether an opinion is correct
- × Whether content is scientifically accurate
- × Whether a publisher is politically or editorially trustworthy
Vero verifies the source. It doesn't decide what you should believe.
04 — source types
Credibility isn't
one-size-fits-all.
- Journalists
- Doctors
- Accountants
- Engineers
- Researchers
- Other credentialed professionals
- News outlets
- Research organisations
- Companies
- NGOs
- Crypto / Web3 organisations
A source can prove relevant credentials without necessarily revealing a legal identity.
05 — competitive landscape
Different trust problems
need different proofs.
| Approach | What it proves | Main limitation |
|---|---|---|
| Platform verification | Platform approval of an account | Controlled by the platform |
| Community Notes | Community consensus about a claim | Slow and platform-dependent |
| Fact-checking | Editorial judgement about a claim | Requires an intermediary |
| C2PA / Content Credentials | Content provenance and history | Doesn't primarily establish source credentials |
| Professional credentials | A person's or organisation's qualification | Usually not portable/verifiable where content is published |
| Vero | Verifiable credentials / accountability of the source | Early-stage ecosystem and issuer registry |
"What happened to this content?"
"What can this source prove about itself?"
Vero doesn't replace fact-checking, Community Notes or content provenance. It addresses a different, upstream problem: giving sources a portable way to prove what they are qualified or authorised to claim.
06 — who it's for
Three sides of the
trust problem.
Can I trust this source?
Readers need a simple signal that tells them what a source can actually prove about itself.
Can I prove my credibility?
Professionals should be able to demonstrate relevant credentials without being forced to expose information they don't want to share.
Can we stand behind what we publish?
Organisations should be able to establish accountability and credibility around the content they publish.
07 — crypto / web3 use case
Credibility matters most
when identity is complicated.
Crypto and Web3 already operate with pseudonyms, DAOs, collectives and globally distributed organisations. Vero can separate a source's credibility from the requirement to expose a legal identity.
A particularly strong early use case — accountability and pseudonymity often coexist in Web3.
08 — who moves first
Two problems,
not one.
A registry with no issuers is worthless, and issuers with nowhere to show the signal are too. Whoever displays a Vero badge and whoever issues the credential behind it are different parties, with different reasons to move.
Web3-native publishing, first
Mirror, Farcaster, Lens and wallet-based social already assume a wallet, already understand proofs, and already publish under pseudonyms. The education cost is close to zero, and the case Vero makes — prove the credential, keep the identity — is the case those communities already argue for themselves.
Then: individual publications and newsletters, where one editor can say yes. Then the platforms — Substack, Ghost — which move last and only on evidence.
Bodies that already credential
Journalists' associations, medical councils, engineering orders. They already decide who is accredited and already maintain that list — Vero does not ask them to make a new judgement, only to publish one they already make.
Slow to adopt, which is why they follow the first group rather than lead it. But they are the only entities that can make the signal mean anything.
Why anyone bothers before the ecosystem exists
A credentialed journalist who cannot safely publish under their own name has a personal reason to want this, with or without a platform. That is demand, not adoption strategy.
Generated content is now indistinguishable from written content at a glance. "A credentialed human stands behind this" is a signal no platform checkmark can give, and the need for it arrived recently and suddenly.
The Digital Services Act and the AI Act push platforms towards provenance and accountability obligations. Verification built early is cheaper than verification retrofitted under a deadline.
Who operates the registry
Today: one registrar, run by the project, and labelled as a demo rather than dressed up as governance.
The destination is not a decentralised registrar but one registrar per issuer — the body that grants a credential is the only one that can say whether it still holds. That is why supporting multiple registrars is the next piece of contract work rather than a later refinement.
Vero does not need an ecosystem to be useful to its first source. It needs one source who cannot publish under their own name, and one reader who wants to know whether to listen.
09 — roadmap
Three waves, one foundation.
Prove
Credential → ZK proof → Verified. Core mechanism proven end-to-end, with a Merkle registry of issuers and on-chain expiry.
Publish
Close the DApp Connector gap so a source can prove from inside the browser, and deploy off the local devnet onto a public Midnight network.
Harden
Per-credential revocation, so one accreditation can be withdrawn without disturbing the rest — and governance by quorum rather than by a single key.
Infrastructure
Multiple credential types and verification policies. Browser overlay, platform integrations, verification API, broader credential ecosystem.
10 — current status
Where Wave 1 stands.
Done
- ✓ Product concept, mechanism and naming finalized
- ✓ Competitive landscape, personas and risk notes documented
- ✓ Local Midnight dev stack — node, indexer, proof server
- ✓ Compact contract — Merkle issuer registry, expiry enforcement
- ✓ End-to-end proof flow on the local devnet
- ✓ Automated checks — end-to-end and proof-forgery regression
- ✓ Reader view — verified badge rendered from live ledger state
- ✓ Contract test suite — 30 tests, under a second, no devnet needed
- ✓ Multiple registrars — one per issuer type, appointed by governance
- ✓ Demo video — three minutes, with the proof shown running
- ✓ Wave 1 submitted
Now
- Judging — September 16 to 27
Next
- Wallet bridge — prove from the browser
- Public-network deployment
Wave 1 is about proving the mechanism — not building the entire product.
Wave 1 submitted · September 9, 2026
Read the full build log →
A trust layer
for the open web.
Vero starts with verifiable professional and organisational credentials — and a simple idea: sources should be able to prove what they are qualified to claim.