Liquidity and Rails
Liquidity and Rails shows how long your desk can keep paying out, per asset and per merchant channel, at today's pace, and suggests top-ups before anything runs dry.
Updated 08 Nov 20261 min read
Required permissions: Manage liquidity (LIQUIDITY_MANAGE).
#Liquidity by asset
Each asset card shows its runway now and with reserves, the on-chain reserves that could still be committed. An asset is graded by its worst pocket, so one dry channel shows even when the total looks healthy.
#Channel runway
| Column | Meaning |
|---|---|
| Merchant | Who the channel pays |
| Channel | The channel |
| We hold | Your side of the pocket |
| Pays out / h | The pocket's payout rate |
| Lasts | Time until it runs dry at that rate |
| Grade | Critical · Warning · Within target · Idle · Not measured |
#How runway is worked out
- Only channels labelled Merchant count. Each asset in a channel is its own pocket, and pockets are never added together across channels or assets.
- The payout rate is how fast your side of the pocket falls over its unbroken run, across a trailing four-hour window. With less than five minutes of history the rate is Not measured, never Idle.
- Payouts already reserved for open payments are subtracted first.
- The grades follow the workspace's runway target: warning below 10 hours and critical below 6 hours by default. A pocket below target raises a Runway low alert.
Channels that are not labelled yet are left out; assign them in Hub settings.
Read Channels and pockets and Top-ups.
Was this page helpful?