Skip to main content
Definition

did:abt

ABT DID Method

ArcBlock’s DID method, using the did:abt: namespace to identify accounts, assets and other objects. Resolution requires support for this method.

Learn more

The did: prefix identifies the URI scheme; abt selects ArcBlock’s method; the final part is the method-specific identifier. ArcBlock’s format includes role, key and hash type information. An object’s DID identifies that object; it does not mean the object owns a private key or grants permissions by itself.

The method’s encoding and supported role types are documented in Understanding DIDs. See DID at ArcBlock for the products and architecture that use it.

Implementation guides

Our term
Only means anything inside
DID
Also called
ABT DID Method
See also
DIDDID Document
Read more
did:abt →

Explore this topic

Articles

  • AI Agents Need More Than a Wallet

    Payment is the most visible connection between AI Agents and blockchains, but the more fundamental questions are: who is the Agent, who authorized it, what can it do, and how do we reconcile what happened when something goes wrong?

  • Agents Need an Identity. DID May Be the Best Place to Start

    An agent cannot exist only as a platform account and an API key. DID can provide a portable, long-lived identity anchor, but authorization, runtime proof, revocation, and audit still have to do their own jobs.

  • Decentralized Identity Made Easy

    An Introduction to decentralized identity By: Riley Chu, Data Engineer of ArcBlock“Decentralized Identity” is one of the most mysterious concepts asso

Products

  • ArcBlock Chain active

    The application-focused Layer 1 for identity, assets and agreements. ArcBlock Chain brings these operations into the protocol, with ABT as the public network’s native token.

  • ArcWallet active

    Create and manage a digital identity (DID) and its associated credentials in one app.

  • DID Connect active

    The part of the DID protocol an application uses to ask someone to sign in or present a credential, including alongside third-party accounts.

Documentation

  • Blockchain Guide legacy

    ArcBlock Blockchain User Guide: Functions and Help Instructions.

  • DID Connect Guide legacy

    The open protocol and development kit for connecting users and dapps.

  • DID Wallet Guide legacy

    DID Wallet: Supports multiple chains, integrates identity and asset management.

Terms

  • Decentralized Identity

    An approach where the identifier and the claims about it are held by the subject and checked by the verifier, instead of living inside one provider's account system. DID and verifiable credentials are the pieces that make it workable.

  • DID

    A DID is a digital identifier. It helps its holder and a verifier establish who controls an identity and who a claim relates to. It is not a wallet, and it does not replace application accounts, sign-in methods, or permission rules.

  • DID Document

    A DID document describes verification methods and services associated with a DID. W3C defines the shared data model; resolving a DID still requires support for its method. Applications decide which keys, purposes and issuers they accept.

  • Verifiable Credential

    A verifiable credential is a signed statement from an issuer about a subject. It gives a verifier something more specific to inspect than a screenshot or an assertion passed along without its source.