Help
What delegation can do
An owner signs a DelegateSet. That grants another account up to 10 permissions: a whole transaction type such as Payment, or a narrow job such as approving a trust line. The helper later sends a normal transaction with the Delegate field, signs it with their own key, and pays the fee. The owner’s sequence number is the one that advances.
What it cannot do
A helper cannot change the master key, the regular key, the signer list, or the list of helpers, and cannot delete the account. Those transactions are not delegable. There is also no way to cap an amount, a destination, or a currency. The ledger permission is all or nothing.
Why there is no amount cap
Permission values name a transaction type or a granular action. They do not carry a limit. A Payment grant can send any amount the account can pay. If you need a spending limit, use a separate funded account instead of a broad grant.
If a helper key leaks
- On the desk, revoke that helper. That is a DelegateSet with an empty permission list.
- If you are unsure who is affected, use Emergency: revoke all helpers.
- If you downloaded a pre-signed revoke, submit that file. It was signed with a Ticket, so it does not depend on the account’s current sequence.
- The ticket locked the owner reserve (0.2 XRP on current Testnet and Mainnet) until the revoke is submitted.
The ledger does not expire a grant by itself. The expiry in this app is a signed revoke waiting to be submitted. Leave the tab open, download the file, or hand the blob to the stateless relay.