Delegated agents
Agent-lane issuance is planned. The published Wallet SDK has no public API for it. The flow below describes its intended authorization and custody boundaries.
Delegated agents receive bounded signing lanes. The lane is tied to mandate policy, typed intent checks, budget, expiry, revocation state, and audit requirements.
Flow
mermaid
flowchart TD
Owner["Owner lane<br/>fresh user authorization"] --> Mandate["Mandate policy<br/>approved digest"]
Owner --> Reshare["Address-preserving lane creation"]
Reshare --> AgentShare["Agent holder share<br/>encrypted to agent custody"]
Reshare --> ServerShare["Server share<br/>lane-scoped admission"]
Mandate --> Admission["Delegated signing admission"]
AgentShare --> Admission
ServerShare --> Admission
Admission --> Sign["Router A/B normal signing"]Every agent signing request must pass lane status, mandate, intent digest, budget, expiry, idempotency, and replay checks.
Invariants
- Agents do not receive wallet private keys.
- Agents cannot change recovery factors.
- Agents cannot export wallet keys.
- Agents cannot sign outside their mandate.
- Agent revocation does not change the wallet address.