DID

Clear law matters, but a product must also explain what its token does, who controls it, what rules apply, and how participants reconcile the record.

The new site is live. Here is how we plan to bring ARC into the community, data spaces and everyday applications, with migrations, new products and builders taking part along the way.

AI services already use credits to meter storage, compute, and API calls. As Agents begin to act across systems, the important work is not giving those units a fashionable name. It is making the rights, authority, and usage they represent possible to verify and reconcile.

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?

AI can turn a request into software, but it does not automatically make that software, its data, or its identity belong to the user. ARC is the new architecture ArcBlock is building for that problem.

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.

A data space associated with a DID. Create a personal space, or connect an application with the permissions and data model its task requires.

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

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

Domain management built on DID and verifiable credentials. One account can host and manage many domains at once, rather than configuring each one separately.

A data space associated with a DID. Create a personal space, or connect an application with the permissions and data model its task requires.

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

ArcBlock Blockchain User Guide: Functions and Help Instructions.

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

A useful system can distinguish the person, service, or agent taking an action; the party it represents; and the permission for that action. Treating all three as one shared secret makes a later decision harder to explain.

A distributed ledger that links records cryptographically and uses shared validation and consensus rules to establish an accepted transaction history.

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.

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.

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

The position that a person should hold their own identifiers and credentials and decide each time what to disclose. It is a stance about who is in control, not a protocol; decentralized identity is how it gets built.