A recurring proposal in the research-integrity literature argues that ORCID and the CRediT taxonomy, useful as they are, still leave gaps: nothing technically stops a co-author from being added without consent, a contributor’s role from being overstated, or a conflict of interest from going undisclosed at the point authorship is assigned. Since roughly 2019, a series of academic papers has proposed closing those gaps with blockchain and self-sovereign identity (SSI) technology — decentralized identifiers, verifiable credentials, and tamper-evident ledgers, borrowed from the broader digital-identity world. This guide separates what has actually been proposed in the literature from what has seen real, verifiable use in scholarly publishing, which as of 2026 is very little.
What problem are these proposals are trying to solve
The stated targets are specific, recurring authorship-integrity failures: author identity ambiguity that ORCID reduces but does not eliminate, “gift” or “guest” authorship where someone is credited without meeting contribution criteria, ghost authorship where a real contributor is omitted, and conflicts of interest that surface only after peer review rather than at submission. A 2025 preprint from researchers at the College of Banking and Financial Studies, posted to arXiv, frames this explicitly: it argues that “existing infrastructures like ORCID effectively disambiguate researcher identities” but “fall short in enforcing explicit authorship consent, accurately verifying contributor roles, and robustly detecting conflicts of interest during peer review” (arXiv:2508.01913). That framing — ORCID as a solid identity layer with a consent-and-verification gap above it — is the starting point for most of the blockchain/SSI proposals in this space.
The building blocks these proposals borrow from digital identity
None of the technology itself is authorship-specific. It is drawn wholesale from the broader self-sovereign identity movement, standardized primarily through the W3C:
Decentralized Identifiers (DIDs)
A DID is a globally unique identifier that a person or organization controls directly, without depending on a central registry to issue or revoke it. DID Core reached W3C Recommendation status in July 2022. In an authorship-verification proposal, a researcher’s DID would sit alongside (not replace) their ORCID iD.
Verifiable Credentials (VCs)
A VC is a cryptographically signed, machine-verifiable claim — for example, “this DID performed formal analysis on manuscript X” — issued by an authority (a co-author, an institution, an editor) and independently checkable by anyone without contacting the issuer. Proposals typically map VC claims directly onto CRediT’s fourteen contributor roles, since CRediT already gives the taxonomy of “who did what” that a VC needs to encode.
Blockchain as an immutable trust registry
The blockchain component is usually a permissioned or public ledger recording that a specific consent, role-claim, or timestamp was issued and has not been altered since — functioning as a tamper-evident audit log for authorship decisions and, in provenance-focused proposals, for when a piece of work first existed. Some proposals add zero-knowledge proofs so a conflict of interest can be checked (e.g., “does this reviewer have an undisclosed financial tie to this author?”) without exposing the underlying financial or affiliation data itself.
What has actually been proposed in the literature
Several distinct strands of proposal exist, aimed at overlapping but not identical problems:
- Authorship consent and role-verification frameworks. The 2025 arXiv proposal cited above combines DIDs, VCs, and a blockchain trust registry specifically to record authorship consent and contributor-role claims, with a stakeholder survey of researchers, editors, and reviewers reporting that participants found the approach improved confidence in attribution — a survey-based signal of perceived usefulness, not evidence of operational deployment.
- Blockchain-based peer-review and publishing platforms. A 2019 Frontiers in Blockchain paper proposed a shared-governance model for blockchain-based scientific publishing more broadly, covering review workflows and incentive structures rather than authorship verification alone. Similar peer-review-focused blockchain system designs have continued to appear in the literature since, generally as architecture proposals and small prototypes rather than production services.
- Research provenance and timestamping. A separate strand focuses narrowly on proving when a piece of work (a dataset, a preprint, a lab notebook entry) first existed, rather than on verifying who should be credited as an author — see the next section.
It is worth being precise about scope here: this is a live area of publishing-technology and digital-identity research, with a steady stream of conference papers and preprints, but it is not the same as an ICMJE-, COPE-, or NISO-endorsed standard. None of the major standards bodies covering authorship (ICMJE’s authorship criteria, NISO’s stewardship of CRediT) has adopted DIDs, VCs, or blockchain as part of their published guidance as of 2026.
Research provenance is the more mature (but still narrow) adjacent use case
Blockchain’s most concrete academic use case has not been authorship verification itself but provenance timestamping — proving a piece of research existed at a given time, independent of formal publication. ARTiFACTS was an early, frequently cited example: a blockchain-based service that let researchers timestamp and cite otherwise-unpublished research objects (datasets, code, notebook entries) via integrations with repositories such as GitHub and Figshare. Coverage of the space also names smaller platforms — Orvium, Pluto, and ScienceMatters/EUREKA among them — exploring blockchain for research workflows, incentives, or new publishing models. Public reporting on ARTiFACTS specifically indicates it is no longer actively pursuing new user adoption, which is a useful data point on how far even the most-cited example of this technology got: real usage among early adopters, not mainstream infrastructure. Treat provenance-timestamping and authorship-consent-verification as related but distinct problems — a page or vendor addressing one is not necessarily addressing the other.
What has actually been adopted, honestly
As of 2026, no blockchain- or self-sovereign-identity-based system for verifying research authorship has been adopted at meaningful, verifiable scale in mainstream scholarly publishing. Specifically:
- ORCID remains the dominant researcher-identity infrastructure, and it is a centralized, federated registry — not blockchain-based, not built on DIDs. ORCID’s own trust model relies on institution-asserted affiliations and verified email domains, not a distributed ledger.
- No major publisher, university consortium, or funder has announced production use of a DID/VC-based authorship-consent system tied to submission workflows, as distinct from a research prototype or pilot described in a paper.
- Early, real-world blockchain research-provenance services that did see genuine early adoption (ARTiFACTS being the most documented) have not scaled into ongoing new-user growth, based on available public reporting.
- Zero-knowledge-proof-based conflict-of-interest checking, discussed in several proposals, remains at the design/prototype stage in the literature reviewed for this guide — no operational deployment was identified.
This is a genuinely early-stage, mostly academic-discourse space rather than an emerging standard research administrators need to prepare their institutions for adopting in the near term. That could change — W3C DIDs and Verifiable Credentials are seeing real production adoption in adjacent domains such as digital diplomas and professional licensure — but authorship verification specifically has not followed.
Why adoption has stalled
The barriers named across this literature and in broader blockchain-adoption research are structural, not merely technical:
- Coordination problem. Authorship verification only has value if publishers, funders, institutions, and existing registries (ORCID, Crossref) all recognize the same credential — a classic multi-sided-market problem that a single research prototype cannot solve on its own.
- Incumbent network effects. ORCID already has tens of millions of registered iDs and is embedded in submission systems, grant platforms, and CRIS software; a parallel identity layer has to justify real additional value over extending what already works, not just technical novelty.
- Governance questions. Who operates the trust registry, who can issue a “consent” credential, and how disputes or revocations are handled are governance problems blockchain does not resolve on its own — and none of the papers in this space have a governance model backed by a standards body.
- Unclear marginal benefit. Much of the stated problem — role transparency — is already addressed, for the majority of journals that have adopted it, by CRediT itself combined with ICMJE’s authorship criteria and editorial policy (requiring corresponding-author sign-off, contributor statements, and disclosed COI forms). The blockchain layer adds cryptographic tamper-evidence on top of that, which is a real property, but has not yet been shown to be worth the added workflow complexity for most journals and institutions.
How this relates to CASRAI’s other authorship and identity content
This guide is specifically about proposals to use blockchain/SSI technology for authorship verification — not about ORCID, CRediT, or persistent identifiers generally, which CASRAI covers in depth elsewhere:
- CRediT taxonomy overview and the fourteen contributor roles — the role vocabulary most blockchain/SSI proposals map their credentials onto.
- ORCID trust markers — how ORCID’s existing, non-blockchain trust model actually works today.
- Author name disambiguation — the identity-collision problem ORCID and CRIS systems already address.
- ISNI vs. ORCID and ARK identifiers — the wider persistent-identifier landscape.
- Blockchain in intellectual property — a parallel look at blockchain’s real use cases and limits in the IP/tech-transfer context, useful for comparing how far blockchain adoption has gotten in a related but separate research-administration domain.
Frequently asked questions
Is blockchain-based authorship verification a real standard yet?
No. It is an active area of academic proposal and prototyping, not a standard endorsed by ICMJE, COPE, or NISO (the current steward of CRediT). Treat any vendor or paper claiming “the” blockchain authorship standard with caution.
Does ORCID use blockchain or self-sovereign identity?
No. ORCID is a centralized, non-profit-operated federated registry. It is not built on distributed-ledger technology or W3C DIDs, though its trust model shares some conceptual goals (verifiable, portable researcher identity) with the SSI movement.
What is the difference between authorship verification and research provenance timestamping?
Authorship verification is about proving who should be credited and with what role. Provenance timestamping is about proving when a piece of research first existed. Blockchain proposals address both, but they are separate problems with separate (and separately immature) adoption histories — see the sections above.
Should a journal or institution adopt one of these systems now?
Based on the evidence available as of 2026, there is no production-grade, widely interoperable system to adopt — the field consists of research proposals, prototypes, and a small number of platforms with limited, non-scaling early adoption. Institutions with authorship-integrity concerns today are better served by rigorously applying existing tools — ICMJE’s authorship criteria, CRediT contributor statements, and disclosed conflict-of-interest policies — than by waiting on or piloting an unproven blockchain layer.
Are decentralized identifiers (DIDs) used anywhere in research infrastructure today?
DIDs and Verifiable Credentials, as a W3C-standardized technology, have real production use in adjacent fields such as digital diploma and professional-license verification. Their application specifically to research authorship verification remains at the proposal/prototype stage.
