You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
ArcBlock accounts, wallets and DID
Separate signing tools, ledger records and identifiers.
ArcBlock's blockchain documentation distinguishes a wallet used for signing from an account stored in the ledger. It identifies accounts with DID addresses and describes accounts holding tokens or NFTs.
One word can hide several objects
A wallet application can manage keys and present more than one account. The account is a chain record; the application is the interface through which a person operates it. The DID identifies an entity according to its method. These objects should not be collapsed into one “login.”
When reading an account page, ask which network holds the record and which key or delegated authority can act for it. When reading DID material, ask how that method creates and resolves identifiers. The W3C concept of DID does not require every method to use a blockchain.
ArcBlock's account documentation also describes migration. An integration needs the specific migration procedure and network support, rather than assuming changing a displayed address moves every asset or application record. Follow ArcWallet for the user-facing wallet role.
Sources and further reading
Check your understanding
Is a wallet application the same thing as an on-chain account?
No. The application operates keys and accounts; the account is a ledger record.
Continue along a learning path
Referenced here
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.