forked from Synthetixio/SIPs
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
100 lines (94 loc) · 4.1 KB
/
index.html
File metadata and controls
100 lines (94 loc) · 4.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
---
layout: default
title: Synthetix Improvement Proposals
---
<h1 class="page-heading">
Synthetix Improvement Proposals
<a href="https://discordapp.com/channels/413890591840272394/" rel="nofollow"
><img
src="https://camo.githubusercontent.com/294a3116521e16f9164255dd2d386b24767e2610/68747470733a2f2f696d672e736869656c64732e696f2f646973636f72642f3431333839303539313834303237323339342e7376673f636f6c6f723d373638414434266c6162656c3d646973636f7264266c6f676f3d6874747073253341253246253246646973636f72646170702e636f6d25324661737365747325324638633937303162393861643433373262353866313366643966363566393636652e737667"
alt="Discord"
data-canonical-src="https://img.shields.io/discord/413890591840272394.svg?color=768AD4&label=discord&logo=https%3A%2F%2Fdiscordapp.com%2Fassets%2F8c9701b98ad4372b58f13fd9f65f966e.svg"
style="max-width: 100%"
/></a>
<!-- <a href="/last-call.xml"><img src="https://img.shields.io/badge/rss-Last Calls-red.svg" alt="RSS"></a> -->
</h1>
<p>
Synthetix Improvement Proposals (SIPs) describe standards for the Synthetix
platform, including core protocol specifications, client APIs, and contract
standards.
</p>
<h2>Contributing</h2>
<ol>
<li>Review <a href="https://sips.synthetix.io/sips/sip-1">SIP-1</a>.</li>
<li>
Fork the repository by visiting the SIPs
<a href="https://github.com/Synthetixio/SIPs">repo</a> and pressing "Fork"
in the top right.
</li>
<li>
Add your SIP to your fork of the repository. There is a
<a href="https://github.com/Synthetixio/SIPs/blob/master/sip-x.md"
>template SIP here</a
>.
</li>
<li>
Submit a Pull Request to Synthetix's
<a href="https://github.com/synthetixio/SIPs">SIPs repository</a>.
</li>
</ol>
<p>
Your first PR should be a first draft of the final SIP. It must meet the
formatting criteria enforced by the build (largely, correct metadata in the
header). An editor will manually review the first PR for a new SIP and assign
it a number before merging it. Make sure you include a
<code>discussions-to</code> header with the URL to a discussion forum or open
GitHub issue where people can discuss the SIP as a whole.
</p>
<p>
If your SIP requires images, the image files should be included in a
subdirectory of the `assets` folder for that SIP as follow:
<code>sips/assets/sip-X</code> (for sip <b>X</b>). When linking to an image in
the SIP, use relative links such as <code>../assets/sip-X/image.png</code>.
</p>
<p>
When you believe your SIP is mature and ready to progress past the WIP phase,
you should reach out to a Spartan Council member on discord by searching
members with the "Spartan Council" role or finding them within the #governance
channel. The Spartan Council will schedule in a call with the SIP author to go
through the SIP in more detail.
</p>
<p>
If the Spartan Council has found that the SIP is valid, they will assign the
<code>Proposed</code> status and call the SIP to a snapshot vote within the
<code>spartancouncil.eth</code> snapshot space connected on the
<a href="https://staking.synthetix.io/"> staking </a> dApp. Once the voting
has ended, the SIP is assigned either a <code>Approved</code> or
<code>Rejected</code> status depending on whether the SIP voting has reached a
super majority.
</p>
<p>
Once the SIP has been implemented by either the protocol DAO or the SIP author
and relevant parties, the SIP is assigned the <code>Implemented</code> status.
Community members who successfully reach this stage are entitled to a reward
from the Synthetix Protocol.
</p>
<h2>SIP status terms</h2>
<ul>
<li><strong>WIP</strong> - a SIP that is still being developed.</li>
<li>
<strong>Proposed</strong> - a SIP that has been reviewed in a Spartan
Council SIP interview.
</li>
<li>
<strong>Approved</strong> - a SIP that has successfully reached a super
majority Spartan Council vote in favour.
</li>
<li>
<strong>Implemented</strong> - a SIP that has been released to main-net.
</li>
<li>
<strong>Rejected</strong> - a SIP that has failed to reach a supermajority
Spartan Council vote in favour.
</li>
</ul>