Verifiable credentials and decentralized identity
Letting a submitter prove who they are, what they're qualified for, or what authority they hold, using a portable credential an agency can check. An agency gets a claim it can check at intake, without collecting identity documents it then has to protect.
The impact of agents
Tools that let a user hold portable, machine-verifiable credentials and have an agent present them are now widely available. As agent-presented credentials become routine, an agency meets more claims relayed by software than handed over by the person they describe. No settled way exists to tell whether the credential still reflects what its holder authorized.
What must be verified
Government needs confidence that a claim about a submitter (their identity, qualification, or authority to act for others) holds to a sufficient level. That confidence must not force the submitter to disclose more than the purpose requires, and the credential's issuing authority must stand behind the claim as its accountable holder.
Protecting access
A credential wallet assumes a personal smartphone and the digital skill to run it, so people on shared or basic devices are denied the verified path outright. The EU's own 80% adoption target concedes that a fifth of users won't hold the wallet. Wallets are issued to adults acting in their own name, so minors, people under guardianship, and people with fluctuating capacity often can't hold the credential, even when they're entitled to the outcome it would ease. Biometric or document verification deters people with a well-founded reluctance to undergo it, and anonymous or pseudonymous participation disappears if identity becomes the price of being heard. Unverified input can be discounted next to credentialed input without the submitter ever seeing the penalty.
Keeping the path open
- Hold verified identity to an optional signal: the anonymous channel stays open, and a submission without a credential is a full submission.
- Publish any weight the credential adds, rather than applying it as a silent discount.
- Make the CredentialConsent step operable by keyboard and assistive technology, announcing non-visually which claim is verified and which is self-asserted.
Response surface
An independently attested identity sits beside a preparation-method declaration the submitter makes themselves, so a reader can tell which claim is vouched for.
Strengthen your submission
Both parts below are optional. You can prove who you are, and tell us how you prepared this. Your submission is accepted either way.
From your digital wallet. Only what this consultation needs is shared.
Bound to your verified identity, but not separately checked. It is accepted as stated.
Verified input and self-declared input are shown as two labeled signals. Anonymous input is never discounted without the user being told.
Maturity
- Established
For identity verification: verifying who someone is to a credential is a settled response (W3C Recommendation, eIDAS mandate).
- Frontier Headline
For using the same credentials to attest how a submission was prepared: binding a preparation-method claim to that verified identity has not been built.
Precedents
W3C Verifiable Credentials Data Model v2.0. The full family of VC specifications reached W3C Recommendation status, establishing a web standard for expressing credentials such as driver's licenses, degrees, and professional registrations in a cryptographically secure, privacy-respecting, and machine-verifiable form. The model supports selective disclosure, so a submitter can prove one attribute without disclosing the rest of the credential.
EU eIDAS 2.0 and Qualified Electronic Attestations of Attributes. Regulation (EU) 2024/1183 requires every Member State to provide at least one European Digital Identity Wallet within 24 months of the implementing acts, and certain private relying parties to accept them within 36 months of the same trigger, so both deadlines run from those acts and not from a date the Regulation itself fixes. A QEAA is a verifiable credential issued by a Qualified Trust Service Provider, interoperable across borders. Its issuer is accredited and the attestation carries legal effect, neither of which follows from a credential format alone.
Australian Government Digital ID System, under the Digital ID Act 2024. The Digital ID Act 2024 established a legislated accreditation scheme, superseding a Trusted Digital Identity Framework that had run as a pilot, and the system most recognizable as myGovID opens to the private sector at the end of 2026 under rule reforms that added a redress framework. Accreditation is legislated and the accredited credential is one private relying parties will be able to accept. It verifies identity, and does not record content provenance or how a submission was prepared.
Aadhaar Verifiable Credentials in Google Wallet (India). Google added Aadhaar-based verifiable credentials to Google Wallet in India, using the W3C Digital Credentials API and ISO/IEC 18013-5. It is government-scale VC issuance running inside consumer wallet infrastructure.
What carries over to agent use
High transferability for identity verification; low transferability for content provenance. Verifiable Credentials solve the "who is submitting" problem well. They do not solve the "how was this submission prepared" problem at all. A user presenting a verified credential proves their identity but says nothing about whether their submission was personally drafted, AI-generated, or copied from a campaign template.
VCs could be extended with custom claim types, such as a "submission process attestation" claim where the holder declares the preparation method. The claim would be self-attested but cryptographically bound to identity, creating accountability for false declarations. No such credential type has been built, so it is an unbuilt response rather than an adaptation of an existing one.
The gap is concrete wherever a national digital identity scheme already exists. A government authentication wallet typically handles sign-in to public services but offers no mechanism for attaching provenance claims to the submissions a user lodges through it. An accreditation framework could in principle support attribute assertions about preparation methods, but where no such use case has been contemplated in the legislation, rules, or technical architecture, closing the gap depends on amending the scheme's rules rather than on the technology alone.
Where things go wrong
Identity binding governs who is submitting, not how an agency reaches a decision, so it does not by itself stop a bad automated decision. It prevents a system issuing consequential demands with no named author to answer for them. Binding each automated determination to an accountable decision-maker creates the chain of responsibility that is otherwise missing.
Sources
9 references
The instrument, the operating deployment, or the official record itself.
Writing about the subject rather than the framework itself, including vendor commentary.