Web3 identity adds DIDs, VCs, and AI agent wallets

Web3 identity is shifting to DIDs, verifiable credentials, and scoped AI agent wallets.

Web3 identity is moving beyond wallet addresses into decentralized identifiers, verifiable credentials, and non-transferable ownership records. The June 25, 2026 Blockchain Council article says the shift aims to let users, software agents, and credentials move across platforms without relying on one login provider.

What changed

The article frames Web3 identity as a stack, not a single wallet feature. It combines DIDs for control, verifiable credentials for claims, wallets for signing and storage, and soulbound-style tokens for records that should not be sold.

It also argues that AI agents need their own cryptographic identity. A bot that can buy compute, pay for data, or call smart contracts should carry a DID, credentials that define scope, and wallet rules that limit what it can do.

• DIDs are controlled by the subject, not a central platform.
• Verifiable credentials can prove age, role, certification, or KYC status.
• Wallets are becoming identity hubs, not just key stores.
• ERC-5114 and ERC-5484 are cited for non-transferable token designs.

The piece also warns against treating old wallet tutorials as current guidance. In OpenZeppelin Contracts 5.x, it notes, developers should not rely on the removed _beforeTokenTransfer hook for transfer blocking and may need to override _update instead.

Why it matters

For developers, the practical shift is toward credential-based access. Instead of storing passport scans or full profiles, apps can verify only the attribute they need, such as KYC status, age, department, or agent spending authority.

For enterprises, the article pushes Web3 identity into IAM territory. The near-term use cases are auditable AI permissions, reusable vendor checks, and portable professional credentials, but only if teams keep sensitive data offchain and design for revocation, recovery, and privacy from the start.

The biggest takeaway is that Web3 identity is becoming a policy layer for humans and agents, not a universal profile. The open question is whether teams will build scoped, revocable credentials now or keep bolting identity rules onto wallets that were never meant to carry them.