-
Notifications
You must be signed in to change notification settings - Fork 17
/
index.html
68 lines (64 loc) · 2.38 KB
/
index.html
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
---
layout: default
title: Lidos Improvement Proposals
---
<h1 class="page-heading">
Lidos Improvement Proposals
</h1>
<p>
Lidos Improvement Proposals (LIPs) describe standards for the Lidos
platform, including core protocol specifications, client APIs, and contract
standards.
</p>
<h2>Contributing</h2>
<ol>
<li>Review <a href="https://github.com/depools/lido-improvement-proposals/blob/develop/LIPS/lip-0.md">LIP-0</a>.</li>
<li>Fork the repository by clicking "Fork" in the top right.</li>
<li>
Add your LIP to your fork of the repository. There is a
<a href="https://github.com/depools/lido-improvement-proposals/blob/develop/lip-X.md"
>template LIP here</a
>.
</li>
<li>
Submit a Pull Request to Lido's
<a href="https://github.com/depools/lido-improvement-proposals">LIPs repository</a>.
</li>
</ol>
<p>
Your first PR should be a first draft of the final LIP. 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 LIP 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 LIP as a whole.
</p>
<p>
If your LIP requires images, the image files should be included in a
subdirectory of the `assets` folder for that LIP as follow:
<code>assets/lip-X</code> (for lip <b>X</b>). When linking to an image in the
LIP, use relative links such as <code>../assets/lip-X/image.png</code>.
</p>
<p>
When you believe your LIP is mature and ready to progress past the WIP phase,
you should ask to have your issue added to the next governance call where it
can be discussed for inclusion in a future platform upgrade. If the community
agrees to include it, the LIP editors will update the state of your LIP to
<code>Approved</code>.
</p>
<h2>LIP status terms</h2>
<ul>
<li><strong>WIP</strong> - a LIP that is still being developed.</li>
<li>
<strong>Proposed</strong> - a LIP that is ready to be reviewed in a
governance call.
</li>
<li>
<strong>Approved</strong> - a LIP that has been accepted for implementation
by the Lido community.
</li>
<li>
<strong>Implemented</strong> - a LIP that has been released to mainnet.
</li>
<li><strong>Rejected</strong> - a LIP that has been rejected.</li>
</ul>