From b75db07e58f8ca3c39744d23afc44942bebe1841 Mon Sep 17 00:00:00 2001 From: Charlie Date: Tue, 17 Sep 2024 11:07:13 +0100 Subject: [PATCH] Revert "feat: add liquidity SLA reward metric (#2309)" This reverts commit a84e7a3ce4353d0ef604a5c88574843575057f3f. --- protocol/0057-TRAN-transfers.md | 8 ++------ protocol/0096-LIQM-liquidity_mechanisms.md | 4 +--- 2 files changed, 3 insertions(+), 9 deletions(-) diff --git a/protocol/0057-TRAN-transfers.md b/protocol/0057-TRAN-transfers.md index 5b5d8c21b..4a83ea363 100644 --- a/protocol/0057-TRAN-transfers.md +++ b/protocol/0057-TRAN-transfers.md @@ -42,12 +42,8 @@ In order to prevent the abuse of user-initiated transfers as spam attack there w ## Minimum transfer amount -Transfers are subject to a minimum transfer amount (expressed in quantum). - -- transfers to a reward pool are controlled by `transfer.minRewardTransferQuantumMultiple`. -- all other transfers are controlled by `transfer.minTransferQuantumMultiple`. - -These network parameters are quantum specified for the relevant [asset](0040-ASSF-asset_framework.md) and the minimum transfer amount is the product of the relevant network parameter and the assets quantum. +This is controlled by the `transfer.minTransferQuantumMultiple` and quantum specified for the [asset](0040-ASSF-asset_framework.md). +The minimum transfer amount is `transfer.minTransferQuantumMultiple x quantum`. If a user is transferring funds from a vested account, if their balance (expressed in quantum) is less than the minimum amount, they should be able to transfer the full balance (note, transferring less than the full balance is not permitted). diff --git a/protocol/0096-LIQM-liquidity_mechanisms.md b/protocol/0096-LIQM-liquidity_mechanisms.md index 5ce2638a7..27e64c073 100644 --- a/protocol/0096-LIQM-liquidity_mechanisms.md +++ b/protocol/0096-LIQM-liquidity_mechanisms.md @@ -73,13 +73,11 @@ The range and required proportion of the epoch are controlled though market conf - `lp_price_range`: a number in the range $[0, 100]$ which defines the range in which an LPs orders will contribute towards their volume of notional, refer to section [instantaneous volume-of-notional](#instantaneous volume of notional) for more details. - `minimum_time_fraction`: a number in the range $[0, 1]$ which defines the minimum proportion of an epoch an LP must have provided an amount of volume for in order for that amount to be set as their volume of notional, refer to section [calculating the volume of notional](#calculating-the-volume-of-notional) for more details. + ### Instantaneous Volume of Notional To calculate each LPs volume of notional, throughout the epoch, the network must sample and store the current volume of notional supplied by each LP at that point. Call this the instantaneous volume of notional. For now this is done once a block but could be sampled randomly to reduce the amount of data stored. ->[!NOTE] -> Whilst the SLA parameters are uniquely configurable per market, they can also be specified for a liquidity SLA reward metric. As such, for each LP, the network must also track the instantaneous volume of notional provided within each unique price range specified by a reward. - Calculating the notional volume supplied at any given point in time is done as follows: Whilst in continuous trading: