People wishing to submit SIPs, first should propose their idea or document in the Community Slack. After discussion they should add the documented SIP as a pull request. After copy-editing and acceptance, it will be published here. Having a SIP here does not make it a formally accepted standard until its status becomes Active. For a SIP to become Active requires the mutual consent of the community.
| Number | Title | Owner | Type | Status |
|---|---|---|---|---|
| 0001 | SIP Purpose and Guidelines | Shawn Wilkinson | Process | Active |
| 0002 | Bounding Sybil Attacks with Identity Cost | Shawn Wilkinson | Standard | Draft |
| 0003 | Remote Notifications and Triggers | Gordon Hall | Standard | Active |
| 0004 | Contract Transfers and Renewals | Gordon Hall | Standard | Active |
| 0005 | File Encryption and Erasure Encoding Standard | Braydon Fuller | Standard | Active |
| 0006 | Farmer Load Balancing Based on Reputation | Moby von Briesen | Standard | Active |
| 0007 | Storj Bridge Directory with an Ethereum Contract | Braydon Fuller | Standard | Draft |
| 0008 | Farmer Time-locked Storage Payouts | Braydon Fuller | Standard | Draft |
| 0009 | Bandwidth Reputation and Accounting | Braydon Fuller | Standard | Draft |
| 0032 | Hierarchically Deterministic Node IDs | Braydon Fuller | Standard | Active |