No description
Find a file
Nathan Marley aa804d2e23 Fix rendering of code block and use fenced blocks (#50)
The fences aren't actually necessary, but make it easier (IMO) to delineate the
code block and not worry about number of leading spaces.
2019-05-28 08:38:11 -04:00
dip-0001 add dip-0001 content 2017-07-12 22:16:50 -07:00
dip-0006 Describe new algo for quorum connections (#40) 2019-02-19 17:04:24 +03:00
dip-0009 Add DIP9 - Feature derivation paths (#48) 2019-05-21 12:12:29 -04:00
dip-0001.md fix broken image path in dip-001 (#33) 2018-12-03 08:02:24 -05:00
dip-0002-special-transactions.md DIP2 - Update state of implemented special txs (#45) 2019-05-08 10:12:27 -04:00
dip-0002.md Status update (#46) 2019-05-08 18:23:03 -04:00
dip-0003-masternode-types.md Add DIP3 2018-04-30 16:51:36 -04:00
dip-0003.md Status update (#46) 2019-05-08 18:23:03 -04:00
dip-0004.md Status update (#46) 2019-05-08 18:23:03 -04:00
dip-0005.md DIP5 - Correct markdown table layout (#38) 2019-01-09 15:50:31 -05:00
dip-0006.md Typo (#47) 2019-05-17 09:14:40 -04:00
dip-0007.md Status update (#46) 2019-05-08 18:23:03 -04:00
dip-0008.md Multiple updates to DIP8 (#44) 2019-05-21 12:09:31 -04:00
dip-0009.md Add DIP9 - Feature derivation paths (#48) 2019-05-21 12:12:29 -04:00
dip-0010.md Fix rendering of code block and use fenced blocks (#50) 2019-05-28 08:38:11 -04:00
LICENSE add LICENSE 2017-07-12 21:53:49 -07:00
README.md Add DIP9 - Feature derivation paths (#48) 2019-05-21 12:12:29 -04:00

Dash Improvement Proposals (DIPs)

DIP stands for Dash Improvement Proposal. Similar to Bitcoin's BIPs, a DIP is a design document providing information to the Dash community, or describing a new feature for Dash or its processes or environment. The DIP should provide a concise technical specification of the feature and a rationale for the feature.

Because Dash is forked from the Bitcoin codebase, many of the BIPs can be applied to Dash as well (a list of the BIPs updated to include Dash-specific details can be found here). The purpose of the DIPs is not to duplicate those which exist as BIPs, but to introduce protocol upgrades or feature specifications which are unique to Dash.

Contributions

We use the same general guidelines for introducing a new DIP as specified in BIP 2, with a few differences. Specifically:

  • Instead of the BIP editor, initiate contact with the Dash Core development team and your request should be routed to the DIP editor(s). The DIP workflow mimics the BIP workflow.
  • Recommended licenses include the MIT license
  • Markdown format is the preferred format for DIPs
  • Following a discussion, the proposal should be submitted to the DIPs git repository as a pull request. This draft must be written in BIP/DIP style as described in BIP 2, and named with an alias such as "dip-johndoe-infinitedash" until the editor has assigned it a DIP number (authors MUST NOT self-assign DIP numbers).

Dash Improvement Proposal Summary

Number Layer Title Owner Type Status
1 Consensus Initial Scaling of the Network Darren Tapp Standard Final
2 Consensus Special Transactions Samuel Westrich, Alexander Block, Andy Freer Standard Final
3 Consensus Deterministic Masternode Lists Samuel Westrich, Alexander Block, Andy Freer, Darren Tapp, Timothy Flynn, Udjinm6, Will Wray Standard Final
4 Consensus Simplified Verification of Deterministic Masternode Lists Alexander Block, Samuel Westrich, UdjinM6, Andy Freer Standard Final
5 Consensus Blockchain Users Alexander Block, Cofresi, Andy Freer, Nathan Marley, Anton Suprunchuk, Darren Tapp, Thephez, Udjinm6, Alex Werner, Samuel Westrich Standard Proposed
6 Consensus Long-Living Masternode Quorums Alexander Block Standard Active
7 Consensus LLMQ Signing Requests / Sessions Alexander Block Standard Active
8 Consensus ChainLocks Alexander Block Standard Active
9 Applications Feature Derivation Paths Samuel Westrich Informational Proposed
10 Consensus LLMQ InstantSend Alexander Block Standard Proposed

License

Unless otherwise specified, Dash Improvement Proposals (DIPs) are released under the terms of the MIT license. See LICENSE for more information or see https://opensource.org/licenses/MIT.