Policies, limits and whitelist
Policies set the thresholds the desk works to, limits cap how much may move per asset in each cycle, and the withdrawal whitelist decides where funds may leave the hub.
Required permissions: Manage policies (POLICY_MANAGE).
#Policies
| Policy | What it sets | Default |
|---|---|---|
| Runway target | When runway grades warning and critical | Warning under 10 h, critical under 6 h |
| Inbound headroom | When inbound capacity is too low | 20% / 5% |
| Top-up trigger | When a pocket is suggested for top-up | 20% / 5% of capacity |
| Top-up target | What a top-up refills to | 40% |
| Approval quorum | Approvals each operation needs | 2 |
| Hold expiry | When a held payment refunds, and when waiting operations alert | 24 hours |
| Reconcile window | When a carried-out operation is flagged | 2 hours |
A policy set for one asset overrides the value for all assets.
#Limits
The most that may move in each cycle, per asset, for on-chain withdrawals, channel pushes and conversions. By default each is 1 BTC a day, except channel pushes at 0.5 BTC a day. Cycles are Daily (reset at 00:00 UTC), Weekly (Monday) or Monthly (the 1st). The tab shows usage against each limit.
Pending and approved operations count against a limit until they finish. An asset with no limit set refuses operations rather than allowing them.
#Withdrawal whitelist
The on-chain addresses funds may be withdrawn to. Select Add address and enter the asset, a label and the address. Removing an address cancels any unclaimed operations that would have used it.