Wisdom Improvement Proposals (WIPs) describe standards for the Wisdom platform, including core protocol specifications, client APIs, and contract standards.
WIP status terms
- Draft - an WIP that is open for consideration.
- Accepted - an WIP that is planned for immediate adoption, i.e. expected to be included in the next hard fork (for Core/Consensus layer WIPs).
- WIP - an WIP that is the result of the consideration is being in the implementation.
- Final - an WIP that has been adopted in a previous hard fork (for Core/Consensus layer WIPs).
- Deferred an WIP that is not being considered for immediate adoption. May be reconsidered in the future for a subsequent hard fork.
WIPs are separated into a number of types, and each has its own list of WIPs.
Standard Track (1)
Describes any change that affects most or all Wisdom implementations, such as a change to the the network protocol, a change in block or transaction validity rules, proposed application standards/conventions, or any change or addition that affects the interoperability of applications using Wisdom. Furthermore Standard WIPs can be broken down into the following categories.
Improvements requiring a consensus fork, as well as changes that are not necessarily consensus critical but may be relevant to “core dev” discussions.
Includes improvements around devp2p and Light Wisdom Subprotocol, as well as proposed improvements to network protocol specifications of whisper and swarm.
Application-level standards and conventions, including contract standards such as token standards, name registries, URI schemes, library/package formats, and wallet formats.
Includes improvements around client API/RPC specifications and standards, and also certain language-level standards like method names and contract ABIs. The label “interface” aligns with the interfaces repo and discussion should primarily occur in that repository before an WIP is submitted to the WIPs repository.
Describes a process surrounding Wisdom or proposes a change to (or an event in) a process. Process WIPs are like Standards Track WIPs but apply to areas other than the Wisdom protocol itself. They may propose an implementation, but not to Wisdom's codebase; they often require community consensus; unlike Informational WIPs, 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 Wisdom development. Any meta-WIP is also considered a Process WIP.