Skip to content

Commit

Permalink
Create sccp-346 (#2059)
Browse files Browse the repository at this point in the history
* Create sccp-346

* Update sccp-346

* Rename sccp-346 to sccp-346.md

---------

Co-authored-by: kaleb <[email protected]>
  • Loading branch information
cavalier-eth and kaleb-keny authored Aug 5, 2024
1 parent bc0da96 commit 0806f66
Showing 1 changed file with 31 additions and 0 deletions.
31 changes: 31 additions & 0 deletions content/sccp/sccp-346.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
---
sccp: 346
network: Ethereum
title: Update Liquidation Ratio
author: Cavalier
status: Draft
created: 2024-08-05
type: Governance
---

## Simple Summary

<!--"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the SCCP.-->

This SCCP proposes to decrease the SNX `liquidationRatio` from 120% to 105% on the ethereum network.

## Abstract

<!--A short (~200 word) description of the variable change proposed.-->

Since the implementation of [SIP-306](https://sips.synthetix.io/sips/sip-306/) on the ethereum network, accounts that are below the `liquidationRatio` ratio, are immediately liquidated with the snx and debt socialized among stakers on v3. The only staker on v3 is the Treasury Council, who is comfortable with the change.

## Motivation

<!--The motivation is critical for SCCPs that want to update variables within Synthetix. It should clearly explain why the existing variable is not incentive aligned. SCCP submissions without sufficient motivation may be rejected outright.-->

Treasury is the sole staker on v3 connected to v2x at the moment, and they have the ability to absorb the liquidated snx with a significantly lower penalty. Hence, this SCCP proposes to lower the liquidation penalty in order to improve the system health by allowing for gradual liquidations to materialize.

## Copyright

Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

0 comments on commit 0806f66

Please sign in to comment.