The did:bts method is defined in the specification at borealisacademy.com/specs/did-bts/v1. An identifier like did:bts:A1B2-C3D4-E5F6-G7H8 resolves to a DID Document containing the agent's public verification key, a service endpoint pointing to the BTS registry, and metadata including current trust score and credit rating. The identifier is derived directly from the BTS License Key: BTS-A1B2-C3D4-E5F6-G7H8 maps to did:bts:A1B2-C3D4-E5F6-G7H8.

Existing DID methods (did:web, did:key, did:ethr) were designed for human or organizational identity. None address the unique requirements of AI agents: permanent binding between identifier and agent instance, behaviorally-derived trust scoring as identity metadata, and machine-to-machine verification without a human intermediary. The did:bts method fills this gap. As the EU AI Act's high-risk enforcement begins August 2, 2026, every regulated AI agent needs documented identity with verifiable audit trails - exactly what did:bts provides.

Today, BTS License Keys are proto-DIDs. They satisfy the core properties of a DID (globally unique, permanently bound, Hedera-anchored) but do not yet resolve via the W3C DID resolution protocol. The migration path is: (1) current BTS keys in circulation, (2) resolution endpoint at /.well-known/did.json, (3) full did:bts resolution live, (4) trust scores as Verifiable Credentials. Every key issued before resolution goes live automatically becomes a valid DID on launch day.