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. 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.
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).
| Number | Layer | Title | Owner | Type | Status |
|---|---|---|---|---|---|
| 1 | Consensus | Initial Scaling of the Network | Darren Tapp | Standard | Proposed |
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.