Technical DIP Template
Preamble
DIP#: to be assigned by DIP Editor
Title: DIP title
Author(s): Name of the DGC Member submitting the DIP
Domain: Network & Protocol | Governance | Money Markets | Metaverse | Products & Services
Type: template
Status: Assigned by DIP Facilitator
Date Proposed: yyyy-mm-dd
Date Ratified: yyyy-mm-dd
Dependencies: List of any existing dependent DIPs
Replaces: List of DIP it is replacing if any
License: to be added by DIP Author
Notes: ---
References
- A list of supporting materials referenced by this DIP.
Sentence Summary
- A description of what the Dijets Improvement Proposal (DIP) is focused on. Suggest 30 words max.
Paragraph Summary
- A description of what the Dijets Improvement Proposal (DIP) is focused on. Suggest 100 words max.
Component Summary
- A description of the purpose of each component in the DIP. Suggest 30 words max per component.
Motivation
- A short description of the motivation behind the proposed technical solution.
Specification
The details of the proposed technical solution. The specification should be detailed enough to allow an implementation team to begin development as well as testing. The specification for technical DIPs must include the following components:
Proposed Code
- The final code that can be used directly in the mandate vote to accept or reject the DIP.
Test Cases
- For the implementation or testing of the proposed code
Security Considerations
- The purpose of this section is to proactively document any security-relevant design information, decisions, potential failure modes, implementation details, and the relevant discussions related to the proposed change(s). This section helps to optimise the DIP process by providing proactive guidance on security considerations when proposing a change that will affect the Dijets Protocol.
- Backwards compatibility
Licensing
- Recommended licenses for developed code:
- MIT: Expat/MIT/X11 license
- 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
Security specific implications/considerations include security-relevant design decisions, concerns, implementation-specific guidance and pitfalls, drawbacks, an outline of threats and risks and how they are being addressed, etc.