Three Checks Before a Security-Ratio Refund Reaches Your LP

A security-ratio refund can return a Chainflip liquidity provider’s assets when vault liquidity approaches the protocol’s security limit, shifting the response from voluntary withdrawals to a network-initiated egress. The mechanism is designed to reduce assets under validator control relative to the collateral securing them; it is not a promise that every LP can withdraw on their own timetable. Before relying on it, check the destination, which liquidity may be selected, and how the return is settled. For the integration context behind these moving parts, the fuller chainflip account is useful. A ratio-driven return also differs from simply closing an active position: selection can depend on liquidity use, not just an LP’s preference.

Is your refund address current for each asset?

It needs to be: the refund address attached to an asset is the destination the protocol can use to return that asset. LPs specify an address when activating an asset, and Chainflip’s liquidity documentation says refund addresses can be updated. Check the address for every asset you supply, including whether you still control it and whether it can receive funds on the relevant chain. A correct State Chain account does not by itself guarantee that an old external-chain destination is still suitable.

This check matters more for an automatic return than a planned withdrawal. In a normal withdrawal, the LP requests an amount and specifies a destination; in a security-ratio purge, the network may initiate the return based on its own rules. Confirm the current address in the account interface or tooling you use, and keep a record of any change. The protocol may deduct the relevant network fee from the amount sent, so reconcile the expected net return rather than assuming the full balance will arrive.

Which liquidity is most exposed to selection?

The least-used liquidity is the first place to look. Chainflip’s published security-ratio description says validators select liquidity based on use over the previous 30 days, with liquidity not deployed in pools first in line, followed by liquidity in unconcentrated ranges. That makes a free balance or lightly used position a different exposure from a concentrated range actively supporting trades. It does not mean an active position is immune if more liquidity has to be removed.

• Separate assets sitting undeployed in the LP account from funds committed to orders.
• Review how often each range has been used, not only its current size.
• Check whether deposits are restricted as the ratio approaches its limit; a blocked deposit can affect a rebalance plan.

Compared with a voluntary withdrawal, which an LP can time around market conditions, a purge prioritizes reducing system exposure. That protects the network’s security buffer but can return assets at an inconvenient point for an LP’s inventory or trading plan.

How will you confirm the refund has settled?

A refund is an egress to an external chain, so a balance change inside the LP account is not the same as confirmed receipt. Chainflip’s documented withdrawal flow has the network create and broadcast an external-chain transaction, then witness it and record it as settled. Track the pending egress, transaction identifier, destination chain and final amount. If the return is split across assets, reconcile each separately against the account balance and any deducted fee.

The broader trade-off is straightforward: the ratio rule can reduce the value exposed to a validator supermajority without waiting for every LP to act, but it gives LPs less control over which capital leaves and when. Watch the reported security ratio, deposit restrictions, any protocol decision that changes purge rules, and the status of each egress. Those signals determine whether a refund is still a contingency or has become an operational event.