Definition
Delegated signing is a wallet design in which an owner authorizes another signer to request specified actions without handing over the wallet's main credential.
How the delegation works
The wallet owner first grants consent for an additional signer. The delegated signer can then request transactions on the owner's behalf. A policy may restrict which assets, contracts or actions are allowed, how much value can move and how long the permission remains valid.
The signing service checks the request and the delegation before producing a signature. The main key does not need to be copied into the agent, which reduces the damage caused by exposing an unrestricted credential.
Scope matters more than the label
Delegation can be broad or narrow. It can be revocable or long lived. It may be enforced by wallet software, a server, a smart account or a venue. A reader should verify the actual policy rather than assume that every delegated signer has the same controls.
What it does not mean
Delegated signing does not transfer ownership by itself, but it can still grant meaningful power. It is not proof of self-custody or proof that every action needs human confirmation.
Where this term fits
Questions about delegated signing
- Does delegated signing reveal the main private key?
- It is designed to avoid giving the delegated actor the main credential. The exact key and signing architecture still depends on the wallet provider.
- Can delegated signing be revoked?
- Many implementations support revocation, but the mechanism and the time it takes to become effective vary. Check the product documentation before relying on it.
- Does every delegated transaction need approval?
- No. Some delegations allow actions inside a standing policy without a new approval. Others pause selected actions for a person to approve.
See these concepts in context
Review the Fensory MCP connection, tools and account controls.