Merge branch 'master' into snax

content/sccp/sccp-2133.md

@@ -3,7 +3,7 @@ sccp: 2133
 network: Ethereum & Optimism
 title: Facilitate sUSD Transfers from L2 to L1 - Peg Rebalancing
 author: Kaleb (@kaleb-keny)
-status: Vote_Pending
+status: Approved
 proposal: >-
   https://snapshot.org/#/snxgov.eth/proposal/0x16fcd1f7bd12a5695a4464412e059960c1c75e1d56c564e6546decdfcf9ba230
 created: 2024-08-05

content/sccp/sccp-2134.md

@@ -3,8 +3,10 @@ sccp: 2134
 network: Ethereum & Optimism
 title: LegacyMarket V3 Migration Preparations
 author: Kaleb (@kaleb-keny)
-status: Vote_Pending
+status: Draft
 created: 2024-08-06
+proposal: >-
+  https://snapshot.org/#/snxgov.eth/proposal/0x76837e764e96af7a0852e051776b50bbaccdd734b7fd552fe153261eb28d3312
 type: Governance
 ---
 

content/sccp/sccp-2135.md

@@ -0,0 +1,39 @@
+---
+sccp: 2135
+network: Optimism
+title: Update Perps V2 Parameters
+author: Kaleb (@kaleb-keny)
+status: Draft
+created: 2024-08-13
+type: Governance
+---
+
+# Simple Summary
+
+This SCCP proposes to update the parameters of the CRV Perp market as per the below:
+
+## Skew Scale:
+
+| **Current Scale** | **Proposed Scale** | **Current Slippage** | **Proposed Slippage** | **Cex Slippage** |
+|:-----------------:|:------------------:|:--------------------:|:---------------------:|:----------------:|
+|     37,500,000    |     46,875,000     |          47          |           38          |        13        |
+
+** Slippage figures in the table above are with respect to a trade size of USD 500 thousand **
+
+## Max Market Value
+Increase the maxMarketValue from 1,851,900 CRV tokens to 6m CRV tokens (roughly 2m$)
+
+# Abstract
+Below is a description of the parameter changes proposed in the SCCP:
+- `skewScale` is the scaling factor of the relevant market in the underlying currency for computing PD and Funding Rates.
+- `maxMarketValue` is the parameter that helps calibrate 
+
+# Motivation
+
+The proposed parameter update aims at improving the execution pricing on the CRV market and increasing the maximum possible open interest given it's utilization.
+
+# Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
+
+

content/sccp/sccp-345.md

@@ -2,7 +2,7 @@
 sccp: 345
 title: Reconfigure Arbitrum Collateral Issuance Parameters 
 network: Arbitrum
-status: Draft
+status: Approved
 type: Governance
 author: Matt
 created: 2024-07-31

content/sccp/sccp-347.md

@@ -4,6 +4,8 @@ title: Deploy Multicollateral Perps Arbitrum
 network: Arbitrum
 status: Draft
 type: Governance
+proposal: >-
+  https://snapshot.org/#/snxgov.eth/proposal/0x2e2528343ec51eb6385a2922f6f7ec08a804bec0afdafff7c97d606ec539e44f
 created: 2024-08-06
 author: Kaleb
 ---
@@ -59,12 +61,12 @@ Accounts would be set to allow for 3 collaterals and 10 simultaneous positions
 |      profitRatio      |    30%    |
 | maxKeeperScalingRatio |    3 bp   |
 |       maxReward       |     30    |
-|      l1SettleGas      |   30,000  |
-|      l2SettleGas      |    2.5M   |
-|       l1FlagGas       |   31,000  |
-|       l2FalgGas       |   1.16M   |
+|      l1SettleGas      |   30k     |
+|      l2SettleGas      |    2M     |
+|       l1FlagGas       |   5,500   |
+|       l2FlagGas       |   850k    |
 |     l1LiquidateGas    |   5,500   |
-|     l2LiquidateGas    |  600,000  |
+|     l2LiquidateGas    |  550k     |
 
 ## Wrappers:
 
@@ -73,9 +75,10 @@ The below wrappers would be setup with no fees, in order to allow traders to acq
 | **Token** |  **Cap**   |
 |:---------:|:----------:|
 |    wETH   |   1,000    |
-|    wBTC   |     75     |
+|    BTC*   |     75     |
 |    USDC   | 10,000,000 |
 
+* The specification of the representative BTC token (wBTC or tBTC) which would be used in wrapping will be decided upon in a different vote. 
 
 # Abstract
 

content/sccp/sccp-348.md

@@ -0,0 +1,28 @@
+---
+sccp: 348
+title: Update RNDR Feed
+network: Arbitrum
+status: Draft
+type: Governance
+created: 2024-08-12
+proposal: >-
+  https://snapshot.org/#/snxgov.eth/proposal/0xac627121160fecf00f5751b694e3ac9804c53a9fa7cd7d997cb5756351d86b23
+author: Kaleb
+---
+
+# Simple Summary
+
+This SCCP proposes to update the RNDR feed with the latest feedId `0x3d4a2bd9535be6ce8059d75eadeba507b043257321aa544717c56fa19b49e35d` 
+
+# Abstract
+
+The previously configured feedId had been deprecated following the RNDR token migration. This resulted in issues with the Perps V3 System given the abscence of a price update at the system level. The short-term solution was to replace the feed with the new feedId available from pyth which points to the new RENDER token.
+
+
+# Motivation
+
+The emergency action was executed last week and this sccp ratifies that action. Future iterations of Peprs V3 aims at tackling that risk by updating the feed to constant price feed that resolves the last available price.
+
+
+# Copyright
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).

content/sips/sip-2051.md

@@ -5,7 +5,7 @@ title: Deprecate Perp Markets with 0 Max Market Value
 proposal: >-
   https://snapshot.org/#/snxgov.eth/proposal/0x4b76e3cbbcc7eaee5d7387f05e75e123cfe6dc299f63d3e9976ca8e70047623b
 author: Kaleb
-status: Approved
+status: Implemented
 created: 2024-01-22
 type: Governance
 ---

content/sips/sip-385.md

@@ -5,6 +5,8 @@ network: Arbitrum
 status: Draft
 type: Governance
 author: cyberduck (@acyberduck)
+proposal: >-
+  https://snapshot.org/#/snxgov.eth/proposal/0xf2450dd68131dfc46b5da6069f9a8febf51b3a8ee7061184478f394be5633567
 ---
 
 ## Simple Summary

content/sips/sip-398.md

@@ -2,7 +2,7 @@
 sip: 398
 title: Chainlink Data Streams For Synthetix V3 on Arbitrum
 network: Ethereum, Optimism, Base & Arbitrum 
-status: Draft
+status: Approved
 type: Governance
 author: Raoul Schipper
 implementor: TBD

content/sips/sip-400.md

@@ -6,6 +6,8 @@ status: Draft
 author: Noisekit
 created: 2024-07-29
 type: Governance
+proposal: >-
+  https://snapshot.org/#/snxgov.eth/proposal/0x24305e3ac888f41e2210a7775ab44c732cc68aed6c73e3480e790bab3cb2875c
 ---
 
 ## Simple Summary

content/sips/sip-402.md

@@ -5,6 +5,8 @@ network: Ethereum, Optimism, Base & Arbitrum
 status: Draft
 type: Governance
 author: Robin (@0xrobin2192)
+proposal: >-
+  https://snapshot.org/#/snxgov.eth/proposal/0x08a4b4c1f5447d06175e5e7c827a817a3433c2f6e6d8f13a63053d945aacdbb6
 created: 2024-08-02
 ---
 

content/sips/sip-403.md

@@ -0,0 +1,72 @@
+---
+sip: 403
+title: List RENDER on Synthetix Perps
+network: Base
+status: Draft
+type: Governance
+author: GUNBOATs (@gunboatsss)
+created: 2024-14-08
+---
+
+<!--You can leave these HTML comments in your merged SIP and delete the visible duplicate text guides, they will not appear and may be helpful to refer to if you edit it again. This is the suggested template for new SIPs. Note that an SIP number will be assigned by an editor. When opening a pull request to submit your SIP, please use an abbreviated title in the filename, `sip-draft_title_abbrev.md`. The title should be 44 characters or less.-->
+
+## Simple Summary
+
+<!--"If you can't explain it simply, you don't understand it well enough." Simply describe the outcome the proposed changes intends to achieve. This should be non-technical and accessible to a casual community member.-->
+
+List RENDER Perps on Synthetix Perps Base.
+
+## Abstract
+
+<!--A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what *will* be done if the SIP is implemented, not *why* it should be done or *how* it will be done. If the SIP proposes deploying a new contract, write, "we propose to deploy a new contract that will do x".-->
+
+This is a proposal to list Render Network (RENDER) perptual futures on Synthetix Perps.
+
+## Motivation
+
+<!--This is the problem statement. This is the *why* of the SIP. It should clearly explain *why* the current state of the protocol is inadequate.  It is critical that you explain *why* the change is needed, if the SIP proposes changing how something is calculated, you must address *why* the current calculation is inaccurate or wrong. This is not the place to describe how the SIP will address the issue!-->
+
+RENDER has been listed on Synthetix Perps as RNDR before the token migration. Now the token has migrated with sufficient liquidity and price feed from Pyth, it is time to list RENDER back.
+
+## Specification
+
+<!--The specification should describe the syntax and semantics of any new feature, there are five sections
+1. Overview
+2. Rationale
+3. Technical Specification
+4. Test Cases
+5. Configurable Values
+-->
+
+### Overview
+
+<!--This is a high level overview of *how* the SIP will solve the problem. The overview should clearly describe how the new feature will be implemented.-->
+
+N/A
+
+### Rationale
+
+<!--This is where you explain the reasoning behind how you propose to solve the problem. Why did you propose to implement the change in this way, what were the considerations and trade-offs. The rationale fleshes out what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.-->
+
+N/A
+
+### Technical Specification
+
+<!--The technical specification should outline the public API of the changes proposed. That is, changes to any of the interfaces Synthetix currently exposes or the creations of new ones.-->
+
+N/A
+
+### Test Cases
+
+<!--Test cases for an implementation are mandatory for SIPs but can be included with the implementation..-->
+
+N/A
+
+### Configurable Values (Via SCCP)
+
+<!--Please list all values configurable via SCCP under this implementation.-->
+
+The configuration value follows Synthetix Perps V3 configuration and will be provided by following SCCP.
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).