From ef0689ffb369d25d5661aca3ba54409e45dd4855 Mon Sep 17 00:00:00 2001
From: kaleb <kalebkeny@gmail.com>
Date: Thu, 28 Mar 2024 11:58:32 +0100
Subject: [PATCH] delete 2057

---
 content/sips/sip-2057.md | 88 ----------------------------------------
 1 file changed, 88 deletions(-)
 delete mode 100644 content/sips/sip-2057.md

diff --git a/content/sips/sip-2057.md b/content/sips/sip-2057.md
deleted file mode 100644
index f264bcbd8..000000000
--- a/content/sips/sip-2057.md
+++ /dev/null
@@ -1,88 +0,0 @@
----
-sip: 2057
-title: List STX on Synthetix Perps
-network: Optimism
-status: Approved
-type: Governance
-author: Noam (@noam99)
-proposal: >-
-  https://snapshot.org/#/snxgov.eth/proposal/0x64a03fba35f9e01732d8fe61857b18095b33708db35a84011f30c21d657c8177
-created: 2024-02-26
----
-
-<!--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 STX on Synthetix Perps.
-
-## 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 STX Futures/Perpetuals 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!-->
-
-STX is the native token of Stacks, the leading Bitcoin L2. STX is currently the 37th largest coin in terms of Market cap and is already integrated into the most important CEXs. 
-STX can attract new traders who seek exposure or hedge their portfolios through Bitcoin-related assets.
-
-## 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
--->
-
-Binance Perp STX/USDT Volume from Coingecko at 2024-02-26: 73,678,232
-
-STX DEX/CEX Spot Data From CoinGecko at 2024-02-26:
-
-| Exchange |  Pair  |  Price  |  Spread  |  24h Volume  |
-|-----|---------------|------------|------------|--------| 
-| Binance | STX/USDT | $2.49 | 0.01% | $20,618,749 |
-| OKX | STX/USDT | $2.49 | 0.03% | $5,666,433 |
-| Coinbase Exchange | STX/USD | $2.49 | 0.07% | $7,207,145 |
-| KuCoin | STX/USDT | $2.49 | 0.04% | $2,684,529 |
-| Gate.io  | STX/USD | $2.49 | 0.02% | $3,243,373 |
-| Bybit  | STX/USDT | $2.49 | 0.04% | $3,526,653 |
-| BitGet | STX/USDT | $2.49 | 0.02% | $1,210,412 |
-
-
-You can find further data here: https://www.coingecko.com/en/coins/stacks
-
-
-### 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.-->
-
-To remain competitive, Synthetix should list a highly-traded cryptocurrency for traders like STX. Additionally, STX represents the token of the leading Bitcoin Layer 2.
-
-### 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.-->
-
-The market will be deployed with Chainlink and Pyth price feed.
-
-### 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 configurable values follows other Perps V2 market and will be update on separate SCCP.
-
-## Copyright
-
-Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).