Account Abstraction DID (did:AA)

Account Abstraction DID (did:aa)

github: https://github.com/rpedersen3/mcp-aa-did

Core Capabilities

Agent Interoperability. Subject and Issuer identification for VC and VP communications between Agents. DIDComm-based Agent Interactions. Model Context Protocol (MCP) agent interactions.
Simplified UI leveraging Gasless (Paymaster), Batching and sponsorship on chain invocation
Simplified Delegation and Role Access leveraging Account Abstraction Delegation
Key Rotation without losing DID. DID not ties to single EOA (no update or re-publication)
Plug into ZK circuits and MPC wallets

Use Account Abstraction-based DIDs when:

You need organization wallets or multi-sig control.
You want social recovery or modular signing.
You need gasless onboarding or sponsored credentials.
You're integrating with ERC-4337, EIP-1271, or ZK workflows.

Signature and Verification Mechanics

Delegator signTypeData leverages the EOA to sign with EIP-712 structured data on behalf of a smart account
Delegator can verify signature on-chain using ERC-1271

Once the message, VC or VP is signed it can move between agents and validated on chain using ERC-1271

Subject/Issuer DID is associated with on-chain account abstraction and not tied to any single EOA.

MyOrgWallet ties all attestations to Organization and Individual Account Abstractions (abstracted away from EOA)

MyOrgWallet manages Account Abstraction DID's tied to Organizations and Individuals

Account Abstraction DID Documents are discoverable
Account Abstraction DID Documents capture delegation between Organizations and Individuals
Account Abstraction DID Documents capture services provided by Organizations

Why have we not seen more emphasis on Account Abstraction DID's

Traditional DID methods like did:ethr, did:web, did:key, and did:peer were built around EOAs (Externally Owned Accounts), public-private keypairs, and static keys.

Account Abstraction (via ERC-4337 and smart accounts) challenges this by enabling smart contracts to act as self-sovereign identities—without holding a private key.

Most DID methods assume a direct signing key, but smart contract accounts don’t have one. This breaks assumptions in current DID libraries, resolvers, and signature verification mechanisms

Extension of Veramo capabilities to support Account Abstraction (ERC-4337, ERC-1271) DID, VC and VP management.

Subject of DID:AA