DIP: 1
Title: DIP process
Author: GTO90 <gto90@protonmail.com>
Comments-Summary: No comments yet.
Comments-URI: https://github.com/DigiByte-Core/dips/wiki/Comments:DIP-0001
Status: Active
Type: Process
Created: 2021-12-22
License: BSD-2-Clause
OPL
A DigiByte Improvement Proposal (DIP) is a design document providing information to the DigiByte community, or describing a new feature for DigiByte or its processes or environment. The DIP should provide a concise technical specification of the feature and a rationale for the feature.
We intend DIPs to be the primary mechanisms for proposing new features, for collecting community input on an issue, and for documenting the design decisions that have gone into DigiByte. The DIP author is responsible for building consensus within the community and documenting dissenting opinions.
Because the DIPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.
This DIP is dual-licensed under the Open Publication License and BSD 2-clause license.
The DIP process begins with a new idea for DigiByte. Each potential DIP must have a champion -- someone who writes the DIP using the style and format described below, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The DIP champion (a.k.a. Author) should first attempt to ascertain whether the idea is DIP-able. Small enhancements or patches to a particular piece of software often don't require standardisation between multiple projects; these don't need a DIP and should be injected into the relevant project-specific development workflow with a patch submission to the applicable issue tracker. Additionally, many ideas have been brought forward for changing DigiByte that have been rejected for various reasons. The first step should be to search past discussions to see if an idea has been considered before, and if so, what issues arose in its progression. After investigating past work, the best way to proceed is by posting about the new idea to the DigiByte-Core/DIPS Gitter channel.
Vetting an idea publicly before going as far as writing a DIP is meant to save both the potential author and the wider community time. Asking the DigiByte community first if an idea is original helps prevent too much time being spent on something that is guaranteed to be rejected based on prior discussions (searching the internet does not always do the trick). It also helps to make sure the idea is applicable to the entire community and not just the author. Just because an idea sounds good to the author does not mean it will work for most people in most areas where DigiByte is used.
Once the champion has asked the DigiByte community as to whether an idea has any chance of acceptance, a draft DIP should be presented to the DigiByte-Core/DIPS Gitter channel. This gives the author a chance to flesh out the draft DIP to make it properly formatted, of high quality, and to address additional concerns about the proposal. Following a discussion, the proposal should be submitted to the DIPs git repository as a pull request. This draft must be written in DIP style as described below, and named with an alias such as "dip-johndoe-newfeature" until an editor has assigned it a DIP number (authors MUST NOT self-assign DIP numbers).
DIP authors are responsible for collecting community feedback on both the initial idea and the DIP before submitting it for review. However, wherever possible, long open-ended discussions on public gitter channels should be avoided. Strategies to keep the discussions efficient include: setting up a separate communications channels for the topic, having the DIP author accept private comments in the early design phases, setting up a wiki page or git repository, etc. DIP authors should use their discretion here.
It is highly recommended that a single DIP contain a single key proposal or new idea. The more focused the DIP, the more successful it tends to be. If in doubt, split your DIP into several well-focused ones.
When the DIP draft is complete, a DIP editor will assign the DIP a number, label it as Standards Track, Informational, or Process, and merge the pull request to the DIPs git repository. The DIP editors will not unreasonably reject a DIP. Reasons for rejecting DIPs include duplication of effort, disregard for formatting rules, being too unfocused or too broad, being technically unsound, not providing proper motivation or addressing backwards compatibility, or not in keeping with the DigiByte philosophy. For a DIP to be accepted it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the protocol unduly.
The DIP author may update the draft as necessary in the git repository. Updates to drafts should also be submitted by the author as pull requests.
It occasionally becomes necessary to transfer ownership of DIPs to a new champion. In general, we'd like to retain the original author as a co-author of the transferred DIP, but that's really up to the original author. A good reason to transfer ownership is because the original author no longer has the time or interest in updating it or following through with the DIP process, or has fallen off the face of the 'net (i.e. is unreachable or not responding to email). A bad reason to transfer ownership is because you don't agree with the direction of the DIP. We try to build consensus around a DIP, but if that's not possible, you can always submit a competing DIP.
If you are interested in assuming ownership of a DIP, send a message asking to take over, addressed to both the original author and the DIP editors. If the original author doesn't respond to email in a timely manner, the DIP editors will make a unilateral decision (it's not like such decisions can't be reversed :).
The current DIP editors are:
- GTO90 (gto90@protonmail.com)
- Jared Tate (jaredtate@protonmail.com)
- Yoshi (Yoshi@digibyte.org)
- Barry (baz@tiltpool.com)
- Ammar (mrnygma@digibyte.io)
- Gary (gary@lifehash.com)
- John (john@dgballiance.org)
The DIP editors subscribe to the DigiByte-Core/DIPS Gitter channel. Off-channel DIP-related correspondence should be sent (or CC'd) to the DIP editors.
For each new DIP that comes in an editor does the following:
- Read the DIP to check if it is ready: sound and complete. The ideas must make technical sense, even if they don't seem likely to be accepted.
- The title should accurately describe the content.
- The DIP draft must have been sent to the DigiByte-Core/DIPS Gitter channel for discussion.
- Motivation and backward compatibility (when applicable) must be addressed.
- Licensing terms must be acceptable for DIPs.
Once the DIP is ready for the repository it should be submitted as a "pull request" to the DIPs git repository where it may get further feedback.
The DIP editor will:
- Assign a DIP number in the pull request.
- Merge the pull request when it is ready.
- List the DIP in README.mediawiki
DIPs should be written in mediawiki format.
Each DIP should have the following parts:
- Preamble -- Headers containing metadata about the DIP (see below).
- Abstract -- A short (~200 word) description of the technical issue being addressed.
- Copyright -- The DIP must be explicitly licensed under acceptable copyright terms (see below).
- Specification -- The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing, interoperable implementations for any of the current DigiByte platforms.
- Motivation -- The motivation is critical for DIPs that want to change the DigiByte protocol. It should clearly explain why the existing protocol is inadequate to address the problem that the DIP solves.
- Rationale -- The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work. The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion.
- Backwards compatibility -- All DIPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The DIP must explain how the author proposes to deal with these incompatibilities.
- Reference implementation -- The reference implementation must be completed before any DIP is given status "Final", but it need not be completed before the DIP is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation must include test code and documentation appropriate for the DigiByte protocol.
Each DIP must begin with an RFC 822 style header preamble. The headers must appear in the following order. Headers marked with "*" are optional and are described below. All other headers are required.
DIP: <DIP number, or "?" before being assigned>
Title: <DIP title; maximum 44 characters>
Author: <list of authors' real names and email addrs>
* Discussions-To: <email address>
* Comments-Summary: <summary tone>
Comments-URI: <links to wiki page for comments>
Status: <Draft | Active | Proposed | Deferred | Rejected |
Withdrawn | Final | Replaced | Obsolete>
Type: <Standards Track | Informational | Process>
Created: <date created on, in ISO 8601 (yyyy-mm-dd) format>
License: <abbreviation for approved license(s)>
* License-Code: <abbreviation for code under different approved license(s)>
* Post-History: <dates of postings to DigiByte gitter channel, or link to thread in channel archive>
* Requires: <DIP number(s)>
* Replaces: <DIP number>
* Superseded-By: <DIP number>
The Author header lists the names and email addresses of all the authors/owners of the DIP. The format of the Author header value must be
Random J. User <address@dom.ain>
If there are multiple authors, each should be on a separate line following RFC 2822 continuation line conventions.
While a DIP is in private discussions (usually during the initial Draft phase), a Discussions-To header will indicate the mailing list or URL where the DIP is being discussed. No Discussions-To header is necessary if the DIP is being discussed privately with the author, or on the DigiByte gitter channel.
The Type header specifies the type of DIP: Standards Track, Informational, or Process.
The Created header records the date that the DIP was assigned a number, while Post-History is used to record when new versions of the DIP are posted to DigiByte gitter channel. Dates should be in yyyy-mm-dd format, e.g. 2001-08-14. Post-History is permitted to be a link to a specific thread in a mailing list archive.
DIPs may have a Requires header, indicating the DIP numbers that this DIP depends on.
DIPs may also have a Superseded-By header indicating that a DIP has been rendered obsolete by a later document; the value is the number of the DIP that replaces the current document. The newer DIP must have a Replaces header containing the number of the DIP that it rendered obsolete.
DIPs may include auxiliary files such as diagrams. Auxiliary files should be included in a subdirectory for that DIP, or must be named DIP-XXXX-Y.ext, where "XXXX" is the DIP number, "Y" is a serial number (starting at 1), and "ext" is replaced by the actual file extension (e.g. "png").
There are three kinds of DIP:
- A Standards Track DIP describes any change that affects most or all DigiByte implementations, such as a change to the network protocol, a change in block or transaction validity rules, or any change or addition that affects the interoperability of applications using DigiByte. Standards Track DIPs consist of two parts, a design document and a reference implementation.
- An Informational DIP describes a DigiByte design issue, or provides general guidelines or information to the DigiByte community, but does not propose a new feature. Informational DIPs do not necessarily represent a DigiByte community consensus or recommendation, so users and implementors are free to ignore Informational DIPs or follow their advice.
- A Process DIP describes a process surrounding DigiByte, or proposes a change to (or an event in) a process. Process DIPs are like Standards Track DIPs but apply to areas other than the DigiByte protocol itself. They may propose an implementation, but not to DigiByte's codebase; they often require community consensus; unlike Informational DIPs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in DigiByte development. Any meta-DIP is also considered a Process DIP.
The typical paths of the status of DIPs are as follows:
Champions of a DIP may decide on their own to change the status between Draft, Deferred, or Withdrawn. A DIP editor may also change the status to Deferred when no progress is being made on the DIP.
A DIP may only change status from Draft (or Rejected) to Proposed, when the author deems it is complete, has a working implementation (where applicable), and has community plans to progress it to the Final status.
DIPs should be changed from Draft or Proposed status, to Rejected status, upon request by any person, if they have not made progress in three years. Such a DIP may be changed to Draft status if the champion provides revisions that meaningfully address public criticism of the proposal, or to Proposed status if it meets the criteria required as described in the previous paragraph.
A Proposed DIP may progress to Final only when specific criteria reflecting real-world adoption has occurred. This is different for each DIP depending on the nature of its proposed changes, which will be expanded on below. Evaluation of this status change should be objectively verifiable, and/or be discussed on the development mailing list.
When a Final DIP is no longer relevant, its status may be changed to Replaced or Obsolete (which is equivalent to Replaced). This change must also be objectively verifiable and/or discussed.
A process DIP may change status from Draft to Active when it achieves rough consensus on the mailing list. Such a proposal is said to have rough consensus if it has been open to discussion on the development mailing list for at least one month, and no person maintains any unaddressed substantiated objections to it. Addressed or obstructive objections may be ignored/overruled by general agreement that they have been sufficiently addressed, but clear reasoning must be given in such circumstances.
A soft-fork DIP strictly requires a clear miner majority expressed by blockchain voting (eg, using DIP 9). In addition, if the economy seems willing to make a "no confidence" hard-fork (such as a change in proof-of-work algorithm), the soft-fork does not become Final for as long as such a hard-fork might have majority support, or at most three months. Soft-fork DIPs may also set additional requirements for their adoption. Because of the possibility of changes to miner dynamics, especially in light of delegated voting (mining pools), it is highly recommended that a supermajority vote around 95% be required by the DIP itself, unless rationale is given for a lower threshold.
A hard-fork DIP requires adoption from the entire DigiByte economy, particularly including those selling desirable goods and services in exchange for DigiByte payments, as well as DigiByte holders who wish to spend or would spend their DigiBytes (including selling for other currencies) differently in the event of such a hard-fork. Adoption must be expressed by de facto usage of the hard-fork in practice (ie, not merely expressing public support, although that is a good step to establish agreement before adoption of the DIP). This economic adoption cannot be established merely by a super-majority, except by literally forcing the minority to accept the hard-fork (whether this is viable or not is outside the scope of this document).
Peer services DIPs should be observed to be adopted by at least 1% of public listening nodes for one month.
API/RPC and application layer DIPs must be implemented by at least two independent and compatible software applications.
Software authors are encouraged to publish summaries of what DIPs their software supports to aid in verification of status changes. Good examples of this at the time of writing this DIP, can be observed in DigiByte Core's doc/bips.md file.
These criteria are considered objective ways to observe the de facto adoption of the DIP, and are not to be used as reasons to oppose or reject a DIP. Should a DIP become actually and unambiguously adopted despite not meeting the criteria outlined here, it should still be updated to Final status.
Why is this necessary at all?
- DIP 1 defines an ambiguous criteria for the Status field of DIPs, which is often a source of confusion. As a result, many DIPs with significant real-world use have been left as Draft or Proposed status longer than appropriate. By giving objective criteria to judge the progression of DIPs, this proposal aims to help keep the Status accurate and up-to-date.
- For DigiByte to function as a currency, it must be accepted as payment. DigiBytes have no value if you cannot acquire anything in exchange for them. If everyone accepting such payments requires a particular set of consensus rules, "DigiBytes" are de facto defined by that set of rules - this is already the case today. If those consensus rules are expected to broaden (as with a hard-fork), those merchants need to accept payments made under the new set of rules, or they will reject "DigiBytes" as invalid. Holders are relevant to the degree in that they choose the merchants they wish to spend their DigiBytes with, and could also as a whole decide to sell under one set of consensus rules or the other, thus flooding the market with DigiBytes and crashing the price.
- Some entities may, to some degree, also be involved in offering goods and/or services in exchange for DigiBytes, thus in that capacity (but not their capacity as <x></x>) be involved in the economy.
- Miners are not included in the economy, because they merely *rely on* others to sell/spend their otherwise-worthless mined produce. Therefore, they must accept everyone else's direction in deciding the consensus rules.
- Exchanges are not included in the economy, because they merely provide services of connecting the merchants and users who wish to trade. Even if all exchanges were to defect from DigiByte, those merchants and users can always trade directly and/or establish their own exchanges.
- Developers are not included in the economy, since they merely write code, and it is up to others to decide to use that code or not.
- This DIP does not aim to address what "should" be the basis of decisions. Such a statement, no matter how perfect in its justification, would be futile without some way to force others to use it. The DIP process does not aim to be a kind of forceful "governance" of DigiByte, merely to provide a collaborative repository for proposing and providing information on standards, which people may voluntarily adopt or not. It can only hope to achieve accuracy in regard to the "Status" field by striving to reflect the reality of *how things actually are*, rather than *how they should be*.
- This DIP addresses only the progression of the DIP Status field, not the deployment of the hard-fork (or any other change) itself.
- Regardless, one shop cannot operate in a vacuum: if they are indeed alone, they will soon find themselves no longer selling in exchange for DigiByte payments, as nobody else would exist willing to use the previous blockchain to pay them. If they are no longer selling, they cease to meet the criteria herein which enables their veto.
- In this scenario, it would seem the previous DigiByte is alive and working, and that the hard-fork has failed. How to resolve such a split is outside the scope of this DIP.
- The group of miners is determined by the consensus rules for the dynamic-membership multi-party signature (for DigiByte, the proof-of-work algorithm), which can be modified with a hard-fork. Thus, if the same conditions required to modify this group are met in opposition to a soft-fork, the miner majority supporting the soft-fork is effectively void because the economy can decide to replace them with another group of would-be miners who do not support the soft-fork.
- The controversial soft-fork, in this circumstance, changes from Final to Replaced status to reflect the nature of the hard-fork replacing the previous (final) soft-fork.
- This is unknown, and set rather arbitrarily at this time. For a random selection of peers to have at least one other peer implementing the extension, 13% or more would be necessary, but nodes could continue to scan the network for such peers with perhaps some reasonable success. Furthermore, service bits exist to help identification upfront.
- If there is only one implementation of a specification, there is no other program for which a standard interface is used with or needed.
- Even if there are only two projects rather than more, some standard coordination between them exists.
- The DIP process exists for standardisation between independent projects. If something only affects one project, it should be done through that project's own internal processes, and never be proposed as a DIP in the first place.
Each DIP should, in its preamble, link to a public wiki page with a summary tone of the comments on that page. Reviewers of the DIP who consider themselves qualified, should post their own comments on this wiki page. The comments page should generally only be used to post final comments for a completed DIP. If a DIP is not yet completed, reviewers should instead post on the applicable development mailing list thread to allow the DIP author(s) to address any concerns or problems pointed out by the review.
Some DIPs receive exposure outside the development community prior to completion, and other DIPs might not be completed at all. To avoid a situation where critical DIP reviews may go unnoticed during this period, reviewers may, at their option, still post their review on the comments page, provided they first post it to the mailing list and plan to later remove or revise it as applicable based on the completed version. Such revisions should be made by editing the previous review and updating the timestamp. Reviews made prior to the complete version may be removed if they are no longer applicable and have not been updated in a timely manner (eg, within one month).
Pages must be named after the full DIP number (eg, "DIP 0001") and placed in the "Comments" namespace. For example, the link for DIP 1 will be https://github.com/DigiByte-Core/dips/wiki/Comments:DIP-0001 .
Comments posted to this wiki should use the following format:
<Your opinion> --<Your name>, <Date of posting, as YYYY-MM-DD>
DIPs may also choose to list a second forum for DIP comments, in addition to the DIPs wiki. In this case, the second forum's URI should be listed below the primary wiki's URI.
After some time, the DIP itself may be updated with a summary tone of the comments. Summary tones may be chosen from the following, but this DIP does not intend to cover all possible nuances and other summaries may be used as needed:
- No comments yet.
- Unanimously Recommended for implementation
- Unanimously Discourage for implementation
- Mostly Recommended for implementation, with some Discouragement
- Mostly Discouraged for implementation, with some Recommendation
Comments-Summary: No comments yet.
Comments-URI: https://github.com/DigiByte-Core/dips/wiki/Comments:DIP-0001
https://some-other-wiki.org/DIP_1_Comments
These fields must follow the "Discussions-To" header defined in DIP 1 (if that header is not present, it should follow the position where it would be present; generally this is immediately above the Status header).
To avoid doubt: comments and status are unrelated metrics to judge a DIP, and neither should be directly influencing the other.
What is the purpose of DIP comments?
- Various DIPs have been adopted (the criteria required for "Final" Status) despite being considered generally inadvisable. Some presently regard DIPs as a "good idea" simply by virtue of them being assigned a DIP number. Due to the low barrier of entry for submission of new DIPs, it seems advisable for a way for reviewers to express their opinions on them in a way that is consumable to the public without needing to review the entire development discussion.
- Participants should freely refrain from commenting outside of their area of knowledge or expertise. However, comments should not be censored, and participation should be open to the public.
New DIPs may be accepted with the following licenses. Each new DIP must identify at least one acceptable license in its preamble. The License header in the preamble must be placed after the Created header. Each license must be referenced by their respective abbreviation given below.
For example, a preamble might include the following License header:
License: BSD-2-Clause
GNU-All-Permissive
In this case, the DIP text is fully licensed under both the OSI-approved BSD 2-clause license as well as the GNU All-Permissive License, and anyone may modify and redistribute the text provided they comply with the terms of *either* license. In other words, the license list is an "OR choice", not an "AND also" requirement.
It is also possible to license source code differently from the DIP text. An optional License-Code header is placed after the License header. Again, each license must be referenced by their respective abbreviation given below.
For example, a preamble specifying the optional License-Code header might look like:
License: BSD-2-Clause
GNU-All-Permissive
License-Code: GPL-2.0+
In this case, the code in the DIP is not available under the BSD or All-Permissive licenses, but only under the terms of the GNU General Public License (GPL), version 2 or newer. If the code were to be available under *only* version 2 exactly, the "+" symbol should be removed from the license abbreviation. For a later version (eg, GPL 3.0), you would increase the version number (and retain or remove the "+" depending on intent).
License-Code: GPL-2.0 # This refers to GPL v2.0 *only*, no later license versions are acceptable.
License-Code: GPL-2.0+ # This refers to GPL v2.0 *or later*.
License-Code: GPL-3.0 # This refers to GPL v3.0 *only*, no later license versions are acceptable.
License-Code: GPL-3.0+ # This refers to GPL v3.0 *or later*.
In the event that the licensing for the text or code is too complicated to express with a simple list of alternatives, the list should instead be replaced with the single term "Complex". In all cases, details of the licensing terms must be provided in the Copyright section of the DIP.
DIPs are not required to be *exclusively* licensed under approved terms, and may also be licensed under unacceptable licenses *in addition to* at least one acceptable license. In this case, only the acceptable license(s) should be listed in the License and License-Code headers.
- BSD-2-Clause: OSI-approved BSD 2-clause license
- BSD-3-Clause: OSI-approved BSD 3-clause license
- CC0-1.0: Creative Commons CC0 1.0 Universal
- GNU-All-Permissive: GNU All-Permissive License
- Apache-2.0: Apache License, version 2.0
- BSL-1.0: Boost Software License, version 1.0
- CC-BY-4.0: Creative Commons Attribution 4.0 International
- CC-BY-SA-4.0: Creative Commons Attribution-ShareAlike 4.0 International
- MIT: Expat/MIT/X11 license
- AGPL-3.0+: GNU Affero General Public License (AGPL), version 3 or newer
- FDL-1.3: GNU Free Documentation License, version 1.3
- GPL-2.0+: GNU General Public License (GPL), version 2 or newer
- LGPL-2.1+: GNU Lesser General Public License (LGPL), version 2.1 or newer
All licenses not explicitly included in the above lists are not acceptable terms for a DigiByte Improvement Proposal unless a later DIP extends this one to add them. However, DIPs predating the acceptance of this DIP were allowed under other terms, and should use these abbreviation when no other license is granted:
- OPL: Open Publication License, version 1.0
- PD: Released into the public domain
DIP 1 allowed the Open Publication License or releasing into the public domain; was this insufficient?
- The OPL is generally regarded as obsolete, and not a license suitable for new publications.
- Many are unfamiliar with the OPL terms, and may just prefer to use the public domain rather than license under uncertain terms.
- The OPL license terms allowed for the author to prevent publication and derived works, which was widely considered inappropriate for DigiByte standards.
- Public domain is not universally recognised as a legitimate action, thus it is inadvisable.
- Some DIPs, especially consensus layer, may include literal code in the DIP itself which may not be available under the exact license terms of the DIP.
- Despite this, not all software licenses would be acceptable for content included in DIPs.
- In some jurisdictions, public domain is not recognised as a legitimate legal action, leaving the DIP simply copyrighted with no redistribution or modification allowed at all.