c880f6efc9
This change proposes to remove non-alphanumeric characters for the first mainnet release of DIP 0005 Blockchain Users, with the option to add them in later. The reasoning is based on securing future compatibility when integrating with global name based systems outside of the Dash protocol: - Periods (.) are compatible with email but will complicate DNS records using BU names, for example user evan.duffield.xyz.tld requires 2 subdomains for a single BU, whereas evanduffield.xyz.tld requires 1 subdomain per BU - Underscores (_) are not compatible with DNS. They could be translated to hyphens (-) but this would complicate the implementation and is not a clean solution - We could implement hyphens (-) but this would break email compatibility - Adding these non-alphanumeric characters at mainnet release is making assumptions for the benefit of aesthetics (more choice of characters for users) - but I do not believe this outways the benefits to securing future compatibility with global name based systems we probably want to integrate with in future - It is a lot easier to not launch with these special characters and play safe, and add them in later (via HF) if required. Obviously, BU names are digital assets with a value themselves, so we cannot remove characters later (which would invalidate existing names and essentially seize/liquidate that property) |
||
|---|---|---|
| dip-0001 | ||
| dip-0006 | ||
| dip-0001.md | ||
| dip-0002-special-transactions.md | ||
| dip-0002.md | ||
| dip-0003-masternode-types.md | ||
| dip-0003.md | ||
| dip-0004.md | ||
| dip-0005.md | ||
| dip-0006.md | ||
| dip-0007.md | ||
| LICENSE | ||
| README.md | ||
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 | Proposed |
| 3 | Consensus | Deterministic Masternode Lists | Samuel Westrich, Alexander Block, Andy Freer, Darren Tapp, Timothy Flynn, Udjinm6, Will Wray | Standard | Proposed |
| 4 | Consensus | Simplified Verification of Deterministic Masternode Lists | Alexander Block, Samuel Westrich, UdjinM6, Andy Freer | Standard | Proposed |
| 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 | Proposed |
| 7 | Consensus | LLMQ Signing Requests / Sessions | 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.