Slight modifications to BSIP procedure

oxarbitrage-patch-1
Fabian Schuh 2016-03-09 14:26:21 +01:00
parent c493fe68ef
commit 94165cb32c
3 changed files with 10 additions and 10 deletions

View File

@ -1,7 +1,7 @@
BSIP: <BSIP number> BSIP: <BSIP number>
Title: <BSIP title> Title: <BSIP title>
Authors: <list of authors' real names and optionally, email addrs> Authors: <list of authors' real names and optionally, email addrs>
Status: [ Draft | Accepted | Final | Withdrawn | Deferred | Rejected | Superseded ] Status: [ Draft | Accepted | Installed | Withdrawn | Deferred | Rejected | Superseded ]
Type: [ Informational | Protocol ] Type: [ Informational | Protocol ]
Created: <date created on, in ISO 8601 (yyyy-mm-dd) format> Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
Discussion: <url> Discussion: <url>

View File

@ -13,15 +13,15 @@ detailed explanation.
Number | Title | Owner | Type | Status Number | Title | Owner | Type | Status
------------------ | ---------------------------------- | -------------- | -------------- | ------- ------------------ | ---------------------------------- | -------------- | -------------- | -------
[1](bsip-0001.md) | BSIP Purpose and Guidelines | Fabian Schuh | Informational | Draft [1](bsip-0001.md) | BSIP Purpose and Guidelines | Fabian Schuh | Informational | Draft
[2](bsip-0002.md) | Refund Create Order Fees on Cancel | Daniel Larimer | Protocol | Draft [2](bsip-0002.md) | Refund Create Order Fees on Cancel | Daniel Larimer | Protocol | Accepted
[3](bsip-0003.md) | Maker / Taker Market Fees Flag | Daniel Larimer | Protocol | Deferred [3](bsip-0003.md) | Maker / Taker Market Fees Flag | Daniel Larimer | Protocol | Deferred
[4](bsip-0004.md) | Distribute Market Fees on Core Asset to Referral Program | Daniel Larimer | Protocol | Draft [4](bsip-0004.md) | Distribute Market Fees on Core Asset to Referral Program | Daniel Larimer | Protocol | Draft
[5](bsip-0005.md) | Expiring Votes for Witnesses | Daniel Larimer | Protocol | Draft [5](bsip-0005.md) | Expiring Votes for Witnesses | Daniel Larimer | Protocol | Draft
[6](bsip-0006.md) | Market Maker Incentivization | Daniel Larimer | Protocol | Draft [6](bsip-0006.md) | Market Maker Incentivization | Daniel Larimer | Protocol | Draft
[7](bsip-0007.md) | Fee Backed Assets (FBA) | Daniel Larimer | Protocol | Draft [7](bsip-0007.md) | Fee Backed Assets (FBA) | Daniel Larimer | Protocol | Installed
[8](bsip-0008.md) | Privacy (STEALTH) Mode | Daniel Larimer | Protocol | Draft [8](bsip-0008.md) | Privacy (STEALTH) Mode | Daniel Larimer | Protocol | Installed
[9](bsip-0009.md) | Benefit Society | Fabian Schuh | Protocol | Draft [9](bsip-0009.md) | Benefit Society | Fabian Schuh | Protocol | Draft
[10](bsip-0010.md) | Percentage-based transfer fee solution based on CER | Jakub Zarembinski | Protocol | Draft [10](bsip-0010.md) | Percentage-based transfer fee solution based on CER | Jakub Zarembinski | Protocol | Accepted
11 | On Demand Voting | Daniel Larmier | Protocol | Draft 11 | On Demand Voting | Daniel Larmier | Protocol | Draft
12 | Hardfork Precdure Proposal | Fabian Schuh | Informational | Draft 12 | Hardfork Procedure Proposal | Fabian Schuh | Informational | Draft
[13](bsip-0013.md) | Disable negative voting on workers | Daniel Larimer | Protocol | Draft [13](bsip-0013.md) | Disable negative voting on workers | Daniel Larimer | Protocol | Draft

View File

@ -42,13 +42,13 @@ There are two kinds of BSIPs:
People wishing to submit BSIPs first should propose their idea as github People wishing to submit BSIPs first should propose their idea as github
issue first. After discussion you will be assigned a number for the bsip issue first. After discussion you will be assigned a number for the bsip
and can send a pull request for your *draft*. Once consensus among and can send a pull request for your *draft*. Once consensus among
discussion particpants is reached, the status can be switched to discussion participants is reached, the status can be switched to
*final*. From this time on, major changes of the document will not be *accepted*. From this time on, major changes of the document will not be
permitted. permitted.
If the proposal requires a protocol upgrade, the proposal is considered If the proposal requires a protocol upgrade, the proposal is considered
*accepted* only if shareholders have approved a corresponding worker or *implemented* only if shareholders have approved a corresponding worker or
hard fork proposal. Informational BSIPs can only reach the *final* hard fork proposal. Informational BSIPs can only reach the *accepted*
state since their implementation is not enforced by the blockchain. state since their implementation is not enforced by the blockchain.
We are fairly liberal with listing BSIP drafts here since the We are fairly liberal with listing BSIP drafts here since the