Guardrails exist because the dangerous moments in self-custody are rushed ones — a payment made under pressure, at 2am, to an address someone just sent you. A limit set calmly in advance is worth more than caution in the moment.
Configure guardrails
- 1
Open Settings → Security → Guardrails.
- 2
Set a per-transaction cap and a daily cap.
Set them near your normal spending rather than near your balance. A cap that never binds is not doing anything.
- 3
Add trusted recipients to the allowlist.
Allowlisted addresses can be exempted from stricter checks, which makes routine payments smooth without loosening the rest.
- 4
Set quiet hours during which larger sends are refused.
- 5
Confirm the changes.
Loosening a guardrail is itself a deliberate action, so a compromised session cannot quietly widen your limits.
Good to know
- Guardrails are enforced server-side as part of preparing the transaction, so they cannot be bypassed by a modified client.
- They apply to autopay and stream settlements too — automation does not escape the limits you set.
- For an immediate stop rather than a limit, use Freeze, which halts outbound activity entirely.
Frequently asked
The transaction is refused before signing and the app tells you which rule blocked it. Nothing is partially sent.
You change the rule, which is a deliberate, authenticated action. There is no one-tap bypass, because a bypass is exactly what an attacker would use.
No. They govern outbound value only. Receiving is always free and unrestricted.
Get SpendTheBits
A fully non-custodial wallet for 13 chains, free on iOS and Android. Your keys never leave your phone.