ION Improvement Plan - IIP-WildOnION-Node-Responsibility
The design of this proposal will be documented in the ION wallet Program Design Specification (PDS) document maintained by the ION Core Team. Implementation of this ION wallet upgrade correctly will require commitment and a significant number of Man-hours from Ionomy LTD DEVs, the ION Core Team and ionomy community.
To support the ION Core Team rapid development schedule, "Ionomy lTD Assets Contracts" design can be implemented as first smart contract on the ION blockchain proving the test of concept and document the real bandwidth usage.
The funding of this new functionality could be obtained from crowd sale of ionomy new deflationary asset Dark Matter. Utilizing the code created and tested by the ION Core Team effort. Phase 1 should have system designer Adam Matlack to implement it (refer to IIP 0002). Phase 2 of this design will bring forth "PWR-GRID Assets" and other Smart Contracts to the ionomy. This IIP should use a life-cycle development process that
encourages sound system principles and a healthy ION network as ionomy ecosystem grows in the future.
ION Improvement White Paper revised 1 July 2018
*
ION Core Team IIPs ReferencedI
IP_0001 - IIP Purpose and GuidelinesIIP_0002 - Secondary tokens
IIP_0003 - Revised block reward scheduleIIP_0004 - Timelock-based block reward distribution
IIP_0005 - Masternode collateral halving
IIP Accountability
Draft ionomy IIP Name: IIP-WildOnION-Node-Responsibility
Type: Informational
Status: Draft - in process of getting ACCEPT/REJECT or ACTIVECreated: July 4 2018
More details of ION Improvement Proposal
https://ion.community/topic/2787/ion-improvement-proposal-wildonion-node-responsibilityionomy Ecosystem White Paper in BITCOINTALK ION Thread:
https://bitcointalk.org/index.php?topic=1443633.8920https://github.com/ionomy/iips/blob/master/ION_IIP.pdf"
If the IIP editor approves, he will assign the IIP a number, label it as Standards Track, Informational, or Process, give it status "Draft", and add it to git.
The IIP editor will not unreasonably deny an IIP. Reasons for denying IIP status 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 ION philosophy.
For an IIP to be accepted it must meet certain minimum criteria.
It must be a clear and complete description of the proposed implementation, if applicable, must be solid and must not complicate the protocol unduly."