agorise
/
bsips
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[BSIPs-0-8] Improved wording, replaces .org with .eu address (fabian)

oxarbitrage-patch-1
Fabian Schuh 2015-12-17 13:24:20 +01:00
parent a0240945ca
commit c947718973
8 changed files with 19 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
bsip-0001.md
View File

@ -1,16 +1,18 @@
BSIP: 0000 BSIP: 0001
Title: BSIP Purpose and Guidelines Title: BSIP Purpose and Guidelines
Authors: Fabian Schuh <Fabian@BitShares.org> Authors: Fabian Schuh <Fabian@BitShares.eu>
Status: Draft Status: Draft
Type: [ Informational | Protocol ] Type: Informational
Created: 2015-12-16 Created: 2015-12-16
# What is a BSIP? # What is a BSIP?
BSIP stands for BitShares Improvement Proposal. A BSIP is a design document BSIP stands for BitShares Improvement Proposal but can also seen as an
providing information to the BitShares community, or describing a new feature for improvement *protocol*. A BSIP is a design document providing information to the
BitShares or its processes or environment. The BSIP should provide a concise BitShares community, or describing a new feature for BitShares or its processes
technical specification of the feature and a rationale for the feature. or environment. The BSIP should provide a concise technical specification of the
feature or the idea and a rationale for it. It may not only describe technical
improvements but also document *best-practises* and recommendations.
We intend BSIPs to be the primary mechanisms for proposing new features, for We intend BSIPs to be the primary mechanisms for proposing new features, for
collecting community input on an issue, and for documenting the design decisions collecting community input on an issue, and for documenting the design decisions
@ -29,7 +31,7 @@ There are two kinds of BSIPs:
new feature, protocol change or any other modification. Informational BSIPs do new feature, protocol change or any other modification. Informational BSIPs do
not necessarily represent a BitShares community consensus or recommendation, not necessarily represent a BitShares community consensus or recommendation,
so users and implementors are free to ignore Informational BSIPs or follow so users and implementors are free to ignore Informational BSIPs or follow
their advice. their advice. Examples would be *best-practises* or *recommendations*.
* A **Protocol** Upgrade BSIP describes any change that affects most or all * A **Protocol** Upgrade BSIP describes any change that affects most or all
BitShares implementations, such as a change to the protocol, a change in block BitShares implementations, such as a change to the protocol, a change in block
or transaction validity rules, or any change or addition that affects the or transaction validity rules, or any change or addition that affects the
@ -99,7 +101,7 @@ can replace version 1.
# What belongs in a BSIP? # What belongs in a BSIP?
Each BSIP should have the following parts: Each BSIP *should* have the following parts:
* Preamble -- RFC 822 style headers containing meta-data about the BSIP, * Preamble -- RFC 822 style headers containing meta-data about the BSIP,
including the BSIP number, a short descriptive title (limited to a maximum of including the BSIP number, a short descriptive title (limited to a maximum of
@ -145,7 +147,7 @@ preamble is provided in [this repository](BSIPs-Template.md).
The current BSIP editors are: The current BSIP editors are:
* Fabian Schuh <Fabian@BitShares.org> * Fabian Schuh <Fabian@BitShares.eu>
* Sigve Kvalsvik <sigvekvalsvik@gmail.com> * Sigve Kvalsvik <sigvekvalsvik@gmail.com>
* *cass* <Cass@BitShares.org> * *cass* <Cass@BitShares.org>
@ -188,5 +190,3 @@ Goodger, they are not responsible for its use in the BitShares Improvement
Process, and should not be bothered with technical questions specific to Process, and should not be bothered with technical questions specific to
BitShares or the BSIP process. Please direct all comments to the BSIP editors BitShares or the BSIP process. Please direct all comments to the BSIP editors
or the BitShares development mailing list. or the BitShares development mailing list.
# Changelog

2
bsip-0002.md
View File

@ -1,7 +1,7 @@
BSIP: 0002 BSIP: 0002
Title: Refund Create Order Fees on Cancel Title: Refund Create Order Fees on Cancel
Authors: Daniel Larimer <dan@cryptonomex.com> Authors: Daniel Larimer <dan@cryptonomex.com>
Fabian Schuh <Fabian@BitShares.org> Fabian Schuh <Fabian@BitShares.eu>
Status: Draft Status: Draft
Type: Protocol Type: Protocol
Created: 2015-12-16 Created: 2015-12-16

2
bsip-0003.md
View File

@ -1,7 +1,7 @@
BSIP: 0003 BSIP: 0003
Title: Maker / Taker Market Fees Flag Title: Maker / Taker Market Fees Flag
Authors: Daniel Larimer <Dan@cryptonomex.com> Authors: Daniel Larimer <Dan@cryptonomex.com>
Fabian Schuh <Fabian@BitShares.org> Fabian Schuh <Fabian@BitShares.eu>
Status: Deferred Status: Deferred
Type: Protocol Type: Protocol
Created: 2015-12-16 Created: 2015-12-16

2
bsip-0004.md
View File

@ -1,7 +1,7 @@
BSIP: 0004 BSIP: 0004
Title: Distribute Market Fees on Core Asset to Referral Program Title: Distribute Market Fees on Core Asset to Referral Program
Authors: Daniel Larimer <Dan@cryptonomex.com> Authors: Daniel Larimer <Dan@cryptonomex.com>
Fabian Schuh <Fabian@BitShares.org> Fabian Schuh <Fabian@BitShares.eu>
Status: Draft Status: Draft
Type: Protocol Type: Protocol
Created: 2015-12-16 Created: 2015-12-16

2
bsip-0005.md
View File

@ -1,7 +1,7 @@
BSIP: 0005 BSIP: 0005
Title: Expiring Votes for Witnesses Title: Expiring Votes for Witnesses
Authors: Daniel Larmier <Dan@cryptonomex.com> Authors: Daniel Larmier <Dan@cryptonomex.com>
Fabian Schuh <Fabian@BitShares.org> Fabian Schuh <Fabian@BitShares.eu>
Status: Draft Status: Draft
Type: Protocol Type: Protocol
Created: 2015-12-16 Created: 2015-12-16

2
bsip-0006.md
View File

@ -1,7 +1,7 @@
BSIP: 0006 BSIP: 0006
Title: Market Maker Incentivization Title: Market Maker Incentivization
Authors: Daniel Larimer <Dan@cryptonomex.com> Authors: Daniel Larimer <Dan@cryptonomex.com>
Fabian Schuh <Fabian@BitShares.org> Fabian Schuh <Fabian@BitShares.eu>
Status: Draft Status: Draft
Type: Protocol Type: Protocol
Created: 2015-12-16 Created: 2015-12-16

2
bsip-0007.md
View File

@ -2,7 +2,7 @@
Title: Fee Backed Assets Title: Fee Backed Assets
Authors: Danial Larimer <Dan@cryptonomex.com> Authors: Danial Larimer <Dan@cryptonomex.com>
Stan Larimer <Stan@cryptonomex.com> Stan Larimer <Stan@cryptonomex.com>
Fabian Schuh <Fabian@BitShares.org> Fabian Schuh <Fabian@BitShares.eu>
Status: Draft Status: Draft
Type: Informational Type: Informational
Created: 2015-12-16 Created: 2015-12-16

2
bsip-0008.md
View File

@ -1,7 +1,7 @@
BSIP: 0008 BSIP: 0008
Title: Privacy (STEALTH) Mode Title: Privacy (STEALTH) Mode
Authors: Daniel Larimer <Dan@cryptonomex.com> Authors: Daniel Larimer <Dan@cryptonomex.com>
Fabian Schuh <Fabian@BitShares.org> Fabian Schuh <Fabian@BitShares.eu>
Status: Draft Status: Draft
Type: Protocol Type: Protocol
Created: 2015-12-16 Created: 2015-12-16