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 delegation: permission without sharing a key
Understand operation-scoped delegation and revocation.
ArcBlock's transaction reference defines DelegateTx and RevokeDelegateTx. A delegation identifies a delegatee and permitted operation types; operations can carry rules. This makes permission a record that can be inspected rather than an instruction to hand over the original private key.
Scope changes the meaning
The reference states that an empty rule list delegates the entire operation type. It also describes combining rules with AND: every rule must be satisfied. An application should therefore show the actual operation and restrictions before the user approves, rather than label every request simply “connect.”
As a teaching scenario, an operator might need permission for one class of actions while another remains unavailable. Whether a specific amount or time restriction is supported must be checked against the rule language and target implementation; the presence of a rules field does not prove every desired policy exists.
Revocation changes future authority; it does not undo an already completed action. These distinctions matter for agent identity: identifying an agent and authorizing its actions are separate tasks.
Sources and further reading
Check your understanding
Is an empty delegation rule list necessarily restrictive?
No. The reference delegates the entire specified operation type when its rules are empty.
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.