The Autonomys Improvement Proposal (AIP) process is designed to foster collaboration and innovation within the Autonomys Network community. It provides a structured way for contributors to propose changes, enhancements, or new features for the network. By engaging the community and utilizing the Substrate governance pallet, AIPs ensure transparency, inclusivity, and consensus-driven decision-making.

1. Purpose of an AIP

An AIP is a formal mechanism to:

• Propose new features or technical enhancements.
• Suggest protocol changes or network upgrades.
• Introduce process improvements or governance adjustments.

All stakeholders, including developers, farmers, and community members, are encouraged to participate in the AIP process.

2. Lifecycle of an AIP

Step 1: Raise a Forum Post

The process begins with an informal discussion on the Autonomys Forum to gauge interest and solicit feedback.

• Post Requirements:
  • A clear and concise title (e.g., "AIP-1: Proposal to Increase Block Rewards").
  • A summary of the idea or change.
  • Rationale for the proposal and its potential benefits.
  • Considerations or challenges, if applicable.
  • Open questions for community feedback.
• Discussion Goals:
  • Identify potential improvements or concerns.
  • Gather support or suggestions for refinement.
• Tagging: Use the tag AIP to categorize the post.

Step 2: Draft a Formal AIP

Based on forum discussions, create a formal AIP document. The AIP should follow a standardized template to ensure clarity and consistency. Once ready for submission, a pull request with the formal AIP should be raised in the Subspace Foundation improvement-proposals GitHub repository.

AIP Template:

# AIP-[Number]: [Proposal Title]

## Author(s)
[Name or pseudonym]

## Status
Draft

## Created
[Date]

## Summary
A brief explanation of the proposal.

## Motivation
Why this proposal is necessary and the problem it aims to solve.

## Specification
Details of the technical or process changes proposed.

## Rationale
Explanation of how the proposal benefits the network and its participants.

## Risks and Considerations
Potential drawbacks or challenges.

## Implementation Plan
Steps required to implement the change, including technical details and timelines.

## References
Links to relevant discussions, documents, or research.