ATIP

ATLETA Improvement Proposals and Token Standards

ATIP - ATLETA Improvement Proposal

ATIP's, or ATLETA Improvement Proposals, are design documents used by the developer communities to inform network participants on subject matters relating to technical infrastructural upgrades. Everything from the virtual machine to API call frameworks, client specifications and the such; ATIPs play a pivotal role in guiding the evolution of ATLETA's core tech stack.

ATIP Lifecycle

Given the severity of impact that an ATIP can have on the overall system and the decision making process requiring specialized technical, economic, and game theory knowledge; ATIPs have a separate track and voting modality then the general purpose proposals in the governance module.

Depending on the complexity around the implementation, coordination of community, and potential impacts, the time lifecycle of an ATIP can vary widely. Regardless of the duration it takes for an ATIP to get passed, ATLETA segments ATIP's lifecycle into five (5) stages:

1. Creation: The initiator must draft, with great attention to detail and structural compliance, the improvements they are proposing; after creation, the document is shared with the ATLETA community.

2. Discussion: Using as many applicable communication channels as possible, including developer forums, social media platforms, virtual conferences, and (when necessary) physical meetings; the drafted document goes through a scrupulous review by the community.

3. Consensus building: Once the supermajority of participants have become aware of the ATIP (or a sufficient amount of time has elapsed), the community enters a period of consideration where proponents and deniers of the ATIP must garner support from the supermajority of technical participants for their decision.

4. Implementation/Denial In the event that the community achieves sufficient consensus on the topic, the ATIP is pushed into an "implementation" phase, where a core group of developers that will handle the realization of the ATIP get to work. Even in the implementation phase, an ATIP can always be halted through an emergency voting. In the event that an ATIP does not attract enough support, it is denied. In order to try resubmitting the same ATIP, the initiator will have to wait for a cooldown to expire.

5. Activation: After an implementation successfully passes operations in Testnet; the ATIP is pushed into ACTIVE phase and deployed to mainnet.

In order to revert or upgrade an active ATIP, users must submit another ATIP addressing the existing ATIP they wish to alter.

ATIP Status

ATLETA Improvement Proposals have six* different states; not including the preliminary idea phase.

Idea Pre-draft, existing only in the authors context; not tracked in repository

Draft Taking place after an ATIP author signals their intentions by merging their ATIP into the repository; this is technically the first status that become trackable. When in draft, ATIPs have no weight on the system and do not gather any feedback.

Review Once an author is satisfied with their proposal, they make sure formatting is correct, and submit it to the community for review.

Consolidation Consolidation is a short transitionary period with a duration between 7-30 days; the "pre-final" state, right before an ATIP is pushed into implementation. When in the Consolidation, the proposal becomes subject to input from the broader community (Governance Members now have a meaningful of input). If during Consolidation some updates/clarifications are deemed necessary by the community, then the proposal will fall back into "review" state until the necessary adjustments are made.

Final An ATIP that has made it past the Consolidation phase is considered to have garnered enough support (or not enough opposition) and transitions into "Final". Here, ATIP's enter implementation and can no longer have any structural adjustments.

Stale In this state, ATIP's are considered to be no longer of importance or have been abandoned. In the event that an ATIP fails to gather any traction in the Draft or Review states and remain inactive for inactive for at least 6 months, it becomes Stale. ATIPs remain stale until the original author triggers an edit, in which case the status reverts to Draft.

Withdrawn ATIPs that have been recalled by the issuing authors. If an ATIP is tagged as "Withdrawn", it can never be submitted through the same ATIP track number and will need to be recreated from the initial draft phase under a new number.