> For the complete documentation index, see [llms.txt](https://docs.pinto.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinto.money/pinto-improvements/pi-12.md).

# PI-12: Decrease Excessively Low L2SR Threshold

Executed on September 8, 2025 at 08:48 UTC.

## Summary <a href="#c2ae4019-aad5-82f2-aa34-81e7ee0ff218" id="c2ae4019-aad5-82f2-aa34-81e7ee0ff218"></a>

Decrease the Excessively Low [L2SR](https://docs.pinto.money/resources/glossary#liquidity-to-supply-ratio-l2sr) Threshold from 12% to 5% in order to incentivize [Converts](https://docs.pinto.money/resources/glossary#convert) Up.

## Links <a href="#da5e4019-aad5-82c4-86ac-016812e0121d" id="da5e4019-aad5-82c4-86ac-016812e0121d"></a>

* [Safe Multisig](https://app.safe.global/transactions/queue?safe=base:0x2cf82605402912c6a79078a9bbfccf061cbfd507)
* [Execution Transaction](https://basescan.org/tx/0x07d8b545c63e5d6af2ab8546d8b564ba7105db9de1f000f344d07f33e72e7d17)

## Problem <a href="#id-51ee4019-aad5-8250-bf75-01aa2ebb86d2" id="id-51ee4019-aad5-8250-bf75-01aa2ebb86d2"></a>

The [Pinto](https://docs.pinto.money/resources/glossary#pinto) price was below the value target, which was largely attributed to downward price volatility in the crypto market. During this time, there had been minimal value [Withdrawn](https://docs.pinto.money/resources/glossary#withdraw) from the protocol, indicating that even if there were Converts that increased the price to the value target, it was unlikely to decrease the amount of liquidity in the protocol.

Given this information, it was likely suboptimal for the protocol to so heavily disincentivize Upward Converts.

The Excessively Low L2SR Threshold (RWLower) enables the protocol to prioritize preserving liquidity during periods of excessively low liquidity. Accordingly, when this threshold is met (*i.e.*, the liquidity level is below the threshold), the protocol decreases the [Crop Scalar](https://docs.pinto.money/responding-to-state/crop-ratio-changes) (Xt​) by up to 50 percentage points per [Season](https://docs.pinto.money/resources/glossary#season) toward its zero floor, moving toward a state in which value held in the LP token with the highest [Seed](https://docs.pinto.money/resources/glossary#seeds) rate is rewarded with the highest relative number of Seeds permitted by the lower bound of the [Crop Ratio](https://docs.pinto.money/resources/glossary#crop-ratio).

With the [Convert Down Penalty](https://docs.pinto.money/resources/glossary#dynamic-convert-down-penalty) adjusted in [PI-11](https://github.com/pinto-org/protocol/pull/136), during positive-[TWAΔP](https://docs.pinto.money/resources/glossary#deltap) Seasons while mints tracked toward the active threshold remain below it, there is a 100% [Mown](https://docs.pinto.money/resources/glossary#mow) [Stalk](https://docs.pinto.money/resources/glossary#stalk) Penalty (subject to the non-[Germinating](https://docs.pinto.money/resources/glossary#germination) minimum) on the portion of a Pinto-to-LP Convert below $1.005 (the then-current Convert Penalty price). The combination of the low Crop Ratio and additional friction to Convert Down had created conditions where there was an extremely high disincentive to Convert Up.

## Solution <a href="#ae8e4019-aad5-8303-92d3-018f4ed1a463" id="ae8e4019-aad5-8303-92d3-018f4ed1a463"></a>

Decreasing RWLower to 5% moves the L2SR of 8.5% from the excessively low range into the reasonably low range. In the newly reclassified L2SR range, the Crop Scalar increases by up to 1 percentage point per Season when the TWAΔP is nonpositive, [Pod Rate](https://docs.pinto.money/resources/glossary#pod-rate) is at least 15%, and required liquidity oracles succeed. A higher Crop Scalar raises the Crop Ratio, increasing Pinto’s Seed rate relative to the LP token with the highest Seed rate. This reduces the Seed advantage of holding LP tokens and can make Converting LP to Pinto (Converting Up) more attractive.

## Rationale <a href="#id-6e9e4019-aad5-8210-bc23-8106c652fb63" id="id-6e9e4019-aad5-8210-bc23-8106c652fb63"></a>

While the ideal solution would be to design a system that dynamically adjusts the L2SR thresholds as a function of the historical lookback of value Withdrawn from the protocol, implementing a multi-Season lookback to support such a target maintenance feature is a major development undertaking. A lower friction, short term solution is to lower RWLower from 12% to 5%.

## Contract Changes <a href="#id-77ce4019-aad5-8385-ac89-81f5a6b4f302" id="id-77ce4019-aad5-8385-ac89-81f5a6b4f302"></a>

### Other Contract / Parameter Changes <a href="#id-624e4019-aad5-8313-abe0-816e2697801e" id="id-624e4019-aad5-8313-abe0-816e2697801e"></a>

Updated `s.sys.evaluationParameters.lpToSupplyRatioLowerBound` from `0.12e18` (12%) to `0.05e18` (5%). All other `EvaluationParameters` fields were unchanged. The threshold is expressed with 18-decimal precision and the excessively low classification uses a strict less-than comparison. L2SR values from 5% inclusive to 12% exclusive therefore move from excessively low to reasonably low. The call did not reset the Crop Scalar or change the Crop Ratio bounds. It also left the Convert Down Penalty Gauge value and data unchanged at execution.

### Function Changes <a href="#b17e4019-aad5-839e-a5fb-814a4046c08d" id="b17e4019-aad5-839e-a5fb-814a4046c08d"></a>

* No contract deployments or facet replacements were needed to decrease RWLower. No initializer was called and no library implementation was deployed or replaced. The threshold was updated by calling `updateSeedGaugeSettings(EvaluationParameters)` on the Pinto Diamond. Execution transaction: <https://basescan.org/tx/0x07d8b545c63e5d6af2ab8546d8b564ba7105db9de1f000f344d07f33e72e7d17>. No function code or ABI changed. The existing owner-or-contract-only function stored the full `EvaluationParameters` struct and returned no value.
* The unchanged `convertDownPenaltyGauge(bytes,bytes,bytes)` also reads this threshold. On a successful Season engagement that reaches its time-and-liquidity calculation with nonzero L2SR, it multiplies the remaining time factor by the lesser of L2SR divided by the threshold and 100%, using 18-decimal fixed-point arithmetic. For example, at 8.5% L2SR, that liquidity factor rises from approximately 70.83% to 100%, holding the time factor fixed. The positive-TWAΔP mint-threshold branch returns before this calculation, including when the threshold is cleared. Zero L2SR retains the prior penalty ratio, and a failed gauge call retains the prior value and data.

### Event Changes <a href="#ab1e4019-aad5-8277-a195-81dd9ded8110" id="ab1e4019-aad5-8277-a195-81dd9ded8110"></a>

* Emitted the existing `UpdatedEvaluationParameters(EvaluationParameters)` event with the full updated struct. No event signature changed.
