Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
  • Loading branch information
fulldecent authored Jul 5, 2019
1 parent ad5f557 commit 8546e17
Showing 1 changed file with 1 addition and 47 deletions.
48 changes: 1 addition & 47 deletions AIP#00.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,53 +33,7 @@ AIP’s serve as the formal process for the Aion community to suggest, debate, c

## AIP Content Template

### Header
* Title
* Author(s)
* Type
* Status
* Created Date
* Contact Information

### Summary
* One sentence summary of the proposal

### Value Proposition
* Brief summary of what value this improvement provides to the overall Aion community.

### Motivation
* Explain the motivation for submitting this proposal. Who does it benefit and why is it needed? Provide any relevant data or research.

### Non-Goals
* Provide a brief explanation of what is out-of-scope for this proposal and what it is not designed to achieve.

### Success Metrics
* If applicable, what metrics and benchmarks can be tracked to evaluate the success of this proposal.

### Description
* Summary of the context and proposed improvement.

### Specification
* Technical specification of the proposed improvement containing the appropriate syntax and semantics. Should cover the various active implementations of Aion.

### Logic
* Walk-through of the design and specification considerations, choices and approach. Provide practical examples of similar implementations, feedback from the community and perspectives on possible concerns.

### Risks & Assumptions
* Breakdown potential risks introduced by this proposal. How does it affect compatibility? Are there any internal or external events that could threaten the effectiveness of this proposal? Provide mitigation strategies for all listed risks and identify any assumptions.

### Test Cases
* Provide test cases for the improvements implementation. Test cases are essential in “Core” improvement proposals.

### Implementations
* Proposed code to be implemented. This section must be complete and adopted for the AIP to be set to “Final”. Implementations must cover the majority of active Aion clients.

### Dependencies
* Identify any other AIP's, modules, libraries, or API's that are dependencies for this AIP to be implemented or achieve its value proposition.

### Copyright
* All AIP’s are public domain. Copyright waiver to be linked
to https://creativecommons.org/publicdomain/zero/1.0/
See [the example template](./AIP Example.md).

## Process Flow

Expand Down

0 comments on commit 8546e17

Please sign in to comment.