| 124 | 124 | | - `PauseLP`#: Pauses the ability for LPs to add/remove liquidity |
| 125 | 125 | | - `PauseLP<chain>`#: Pauses the ability for LPs to add/remove liquidity, per chain |
| 126 | 126 | | - `MaximumLiquidityRune`#: Maximum RUNE capped on the pools known as the ‘soft cap’ |
| 127 | 127 | | - `LiquidityLockUpBlocks`: The number of blocks an LP must wait before they can withdraw their liquidity |
| 128 | 128 | | - `PendingLiquidityAgeLimit`: The number of blocks the network waits before initiating pending liquidity cleanup. Cleanup of all pools lasts for the same duration. |
| 129 | 129 | | - `PauseAsymWithdrawal-<Chain>`#: Forces dual-address liquidity providers to withdraw symmetrically rather than asymmetrically. |
| 130 | 130 | | - `PauseLPDeposit-<Asset>`#: pauses the ability to add liquidity into that pool. E.g. `PAUSELPDEPOSIT-BTC-BTC=1` suspends deposits for the BTC pool |
| 131 | 131 | | - `LUVIOverhangGuard`\*: When above `0` (the default is `1`), rejects liquidity adds, from users and from POL, into a pool in synth overhang (synth supply at least twice the pool's asset depth). POL skips such pools, and aged pending liquidity in them stays pending (and withdrawable) instead of being committed. Withdrawals are unaffected. `0` turns the guard off |
| 132 | | − | - `LUVIGuard`\*: When above `0` (the default is `1`), checks every handler run dispatched through the internal handler (including the swap queue and the messages that observed txs and deposits dispatch) and the wrapped EndBlock steps for drops in the hedged LP equity G of the pools it wrote (see `x/thorchain/types/type_luvi.go`). A user value flow (swap, add or withdraw liquidity, donate, trade/secured asset, RUNEPool and TCY messages) that lowers a pool's G beyond the computed allowance for gas, slashes, LP-flow rounding and synth mints is rejected and refunded. Other handlers, the same messages when the protocol sends them itself (POL, ragnarok, saver ejects, pending liquidity commits), and EndBlock steps only report. Messages handled directly by the external msg server (for example `MsgErrataTx` and errata quorum), BeginBlock, and the EndBlock steps that are not wrapped (observation tallies, volume, dynamic fees, scheduled migrations) are outside the guard: their pool changes reach only the accumulator, with no `luvi_loss` event. Within the guard, every drop beyond the allowance, and every LP-unit change without matching add/withdraw events, emits a `luvi_loss` event naming the pool, the scope and the inbound tx; covered drops are only recorded by the accumulator. With a virtual synth depth above 1x (`VirtualMultSynthsBasisPoints` above 10000, as on mocknet), pools whose synth supply moved are skipped. `0` turns the guard and the events off; the per-pool G accumulator on the pool endpoints always runs |
| 132 | + | - `LUVIGuard`\*: When above `0` (the default is `1`), checks every handler run dispatched through the internal handler (including the swap queue and the messages that observed txs and deposits dispatch) and the wrapped EndBlock steps for drops in the hedged LP equity G of the pools it wrote (see `x/thorchain/types/type_luvi.go`). A user value flow (swap, add or withdraw liquidity, donate, trade/secured asset, RUNEPool and TCY messages) that lowers a pool's G beyond the computed allowance for gas, slashes, LP-flow rounding and synth mints is rejected and refunded. Other handlers, the same messages when the protocol sends them itself (POL, ragnarok, saver ejects, pending liquidity commits), and EndBlock steps only report. Messages handled directly by the external msg server (for example `MsgErrataTx` and errata quorum), BeginBlock, and the EndBlock steps that are not wrapped (observation tallies, volume, dynamic fees, scheduled migrations) are outside the guard: their pool changes reach only the accumulator, with no `luvi_loss` event. Within the guard, every drop beyond the allowance, and every LP-unit change without matching add/withdraw events, emits a `luvi_loss` event naming the pool, the scope and the inbound tx; covered drops are only recorded by the accumulator. With a virtual synth depth above 1x (`VirtualMultSynthsBasisPoints` above 10000, as on mocknet), pools whose synth supply moved are skipped. The same Mimir gates a report-only check around the pool reward payout: for each rewarded pool it compares the change in G with the expected LP share of the reward, and checks that the pool rewards add up to the rewards event and to the RUNE Asgard received. It emits a `luvi_reward` event for every failure, plus one per rewarded pool every 600 blocks as a sample. `0` turns the guards, the reward check and their events off; the per-pool G accumulator on the pool endpoints always runs |
| 133 | 133 | | |
| 134 | 134 | | ## RunePool |
| 135 | 135 | | |
| 136 | 136 | | - `RUNEPoolEnabled`: Enable/disable RUNE Pool |
| 137 | 137 | | - `RUNEPoolDepositMaturityBlocks`: Minimum number of blocks from last RUNEPool deposit when a withdraw is allowed. |
| 138 | 138 | | - `RUNEPoolMaxReserveBackstop`: Max amount of RUNE above the `POLMaxNetworkDeposit` that the reserve can enter RunePool before withdrawals are disabled. |
| 139 | 139 | | |
| 140 | 140 | | ## Chain Management |
| 141 | 141 | | |
| 142 | 142 | | - `HaltChainGlobal`#: Pause observations on all chains (chain clients) |
| 143 | 143 | | - `HaltTrading`: Stops swaps and additions, if done, will result in refunds. Observations still occur. |
| 144 | 144 | | - `Halt<chain>Chain`#: Pause a specific blockchain |
| 145 | 145 | | - `SolvencyHalt<Chain>`# Halts a chain if the solvency checker for that chain fails. |