AIP-1, AIP-2, AIP-7, the template and the index brought to the working generation: the published governance text was missing entire sections, including the rules themselves (D-377)

This commit is contained in:
Aere Network committed 2026-09-11 22:04:15 +03:00
1 parent 16ce7e8989
commit 83453d9a79
5 files changed
+461 -233

No files matched your search

+105 -106
View File
@@ -1,118 +1,117 @@
# AERE Improvement Proposals (AIPs)
# Aere Improvement Proposals (AIPs)
An AIP (AERE Improvement Proposal) is a design document that describes a change
to the AERE Network (chain ID 2800), its contracts, its consensus parameters, or
its processes. An AIP records the motivation for a change, the exact mechanism,
the rationale for the design, and, when the change is already live, the on-chain
addresses and transactions that prove it exists.
An AIP is a design document describing a change to Aere Network (chain ID 2800),
its contracts, its consensus parameters, or its processes. It records the
motivation, the exact mechanism, the rationale, and, when the change is already
live, the on-chain addresses and transactions that prove it exists.
AIPs are AERE's equivalent of Ethereum's EIP/ERC process. They exist so that any
reader, human or machine, can reconstruct why the chain works the way it does
from a single canonical, plain-text source instead of from marketing pages.
AIPs exist so that a reader, human or machine, can reconstruct why the chain
works the way it does from one canonical plain-text source instead of from
marketing pages or from someone's memory.
This directory is a local, self-contained scaffold. It is not published anywhere
and is not wired into any build or deployment. It is intended to be the seed of a
public AIP repository once the process is stable.
**Start here:**
## What belongs in an AIP
- A protocol or consensus change (block time, fee routing, precompiles).
- A new contract standard or interface that other builders are expected to
integrate against.
- A token-standard or account-standard convention (ARC).
- A process or governance change (Meta).
Things that do not belong in an AIP: bug-fix redeploys that preserve an existing
interface (those are tracked in `sdk-js/src/addresses.ts` deprecation notes),
routine parameter tuning inside an already-ratified bound, and pure documentation.
## Lifecycle
An AIP moves through a small number of statuses. The happy path is
`Draft -> Review -> Last Call -> Final`. Standards that are never "done" (for
example a registry that keeps growing) settle in `Living` instead of `Final`.
| Status | Meaning |
| --- | --- |
| Draft | The proposal is written and formatted correctly and has an author. It may still change substantially. |
| Review | The author has marked it ready for wider scrutiny. Open questions are being resolved. |
| Last Call | Final review window. A fixed review period is stated. If no blocking issue is raised, it advances. |
| Final | Accepted and, for already-shipped work, live on chain 2800. The mechanism is now stable and should not change in a breaking way. |
| Living | Accepted and expected to keep being updated (for example an index or a registry-style standard). |
| Withdrawn | The author or the editors abandoned the proposal. Terminal. |
| Stagnant | Inactive in Draft or Review for an extended period. Can be revived. |
Retro-filed AIPs (documents written after the change already shipped) enter
directly at `Final` or `Living` and carry a note that they are backfilling
history. AIP-2 through AIP-7 in this scaffold are retro-filed.
## Categories and types
Every Standards Track AIP names one category:
- **Core**: consensus, block production, fee/burn accounting, precompiles, and
anything that changes how the chain itself behaves. Requires a client or
genesis/config change.
- **Networking**: peer-to-peer protocol, sync, and node-to-node messaging.
- **Interface**: contract-level interfaces, ABIs, RPC conventions, and
verification surfaces that builders integrate against.
- **ARC (token standards)**: AERE Request for Comment. Application and token
standards, for example ERC-20/4626 receipt tokens and ERC-4337 account
conventions, as adopted on AERE.
- **Meta**: process, governance, and the AIP process itself.
Types: Standards Track (Core, Networking, Interface, ARC), Meta, and
Informational. Informational AIPs give guidance and do not mandate anything.
## Honest governance note (read this)
AERE is not yet trustlessly governed. Today the network runs seven validators
under a single operator, one client (Hyperledger Besu QBFT), no external security
audit, and thin real usage. In that reality an AIP is not ratified by an on-chain
vote of independent stakeholders. It is **Foundation-ratified**: the AERE
Foundation account (`0x0243A4f47D44b40b65D33f20329dE20D00c6f3C3`, a single-key
Foundation-controlled account, not a deployed multisig) is the final editor and
approver.
Every AIP that predates validator and client decentralization carries the label
**"Foundation-ratified (pre-decentralization)"** so no reader mistakes editorial
ratification for trustless governance. As the validator set opens up and a second
client and independent stakers come online, the process is expected to migrate to
stake-weighted or validator-weighted ratification. That migration will itself be a
Meta AIP. Until then, the honest description of AERE governance is: a Foundation
publishes proposals, ships them, and records them here for public audit.
## How to file an AIP
1. Copy `aip-template.md` to `AIP-N.md`, where N is the next free integer.
2. Fill in every required section. Do not delete a section header; if a section
does not apply, write "None" under it.
3. Cite on-chain addresses verbatim from `sdk-js/src/addresses.ts`. Never invent
an address, a transaction hash, or a gas number. If a number has not been
measured, write "to be measured" rather than guessing.
4. Add a row to the index below.
5. Open it for editorial review. Until decentralization, the editor is the
Foundation.
- **[AIP-1](./AIP-1.md)** is the process: numbering, statuses and the transitions
between them, supersession, and the rule that accepted proposals are not
silently edited.
- **[CONTRIBUTING.md](./CONTRIBUTING.md)** is how someone who is not us proposes
a change, and who actually decides.
- **[aip-template.md](./aip-template.md)** is the required template.
## Index
| AIP | Title | Type / Category | Status | Note |
Status values are defined in AIP-1 section 3. A blank Superseded-By means the
document is current.
| AIP | Title | Type / Category | Status | Superseded by |
| --- | --- | --- | --- | --- |
| [1](./AIP-1.md) | AIP Purpose and Process | Meta | Living | The process itself |
| [2](./AIP-2.md) | Coinbase Fee-Burn Routing (37.5%) | Standards Track / Core | Final | Foundation-ratified (pre-decentralization) |
| [3](./AIP-3.md) | Sub-Second Block Period (500 ms QBFT) | Standards Track / Core | Final | Foundation-ratified (pre-decentralization) |
| [4](./AIP-4.md) | On-Chain Post-Quantum Signature Verification Suite | Standards Track / Interface | Final | Foundation-ratified (pre-decentralization) |
| [5](./AIP-5.md) | sAERE Receipt Token and AereSink Immutable Flywheel | Standards Track / ARC | Final | Foundation-ratified (pre-decentralization) |
| [6](./AIP-6.md) | ERC-4337 Passkey and Gasless Onboarding Stack | Standards Track / ARC | Final | Foundation-ratified (pre-decentralization) |
| [7](./AIP-7.md) | AerePQC Hard-Fork Activation (Native PQC Precompiles and Extended EIP-2935 Lookback) | Standards Track / Core | Final | Foundation-ratified (pre-decentralization) |
| [1](./AIP-1.md) | AIP Purpose and Process | Meta | Living (rev 2, 2026-07-20) | |
| [2](./AIP-2.md) | Coinbase Fee-Burn Routing (37.5%) | Standards Track / Core | Final | |
| [3](./AIP-3.md) | Sub-Second Block Period (500 ms QBFT) | Standards Track / Core | Final | |
| [4](./AIP-4.md) | On-Chain Post-Quantum Signature Verification Suite | Standards Track / Interface | Final | |
| [5](./AIP-5.md) | sAERE Receipt Token and AereSink Immutable Flywheel | Standards Track / ARC | Final | |
| [6](./AIP-6.md) | ERC-4337 Passkey and Gasless Onboarding Stack | Standards Track / ARC | Final | |
| [7](./AIP-7.md) | AerePQC Hard-Fork Activation (PQC Precompiles and EIP-2935 Lookback) | Standards Track / Core | Final | |
| [8](./AIP-8.md) | Post-Quantum-Authorized Transaction Envelope (EIP-2718 Type 0x2A) | Standards Track / Core | **Draft, not live** | |
| [9](./AIP-9.md) | Consensus Mechanism: QBFT, not HotStuff | Informational | Final | |
| [10](./AIP-10.md) | Execution Client: Forked Besu with Nethermind Second, not Reth | Informational | Final | |
| [11](./AIP-11.md) | Interoperability: Hyperlane-Compatible plus zk Light Clients, not IBC | Informational | Final | |
| [12](./AIP-12.md) | The Virtual Machine: Extend the EVM, not a New VM | Informational | Final | |
| [13](./AIP-13.md) | Post-Quantum Signatures: Falcon and ML-DSA Together | Informational | Final | |
| [14](./AIP-14.md) | Account Abstraction: ERC-4337 with EIP-7702 Bridge, not Native AA | Informational | Final | |
| [15](./AIP-15.md) | In-Place Hybrid PQC Consensus Activation, not Re-Genesis | Standards Track / Core | **Draft, testnet R&D only** | |
| [16](./AIP-16.md) | PQ STARK-Verify Precompile (0x0AE8) | Standards Track / Core | **Draft, skeleton, verifies nothing** | |
| [17](./AIP-17.md) | One-Gwei EIP-1559 Base-Fee Floor | Standards Track / Core | Final | |
| [18](./AIP-18.md) | EIP-2935 on Chain 2800: Deviation from the Written Activation Schedule | Standards Track / Core | Final | |
| [19](./AIP-19.md) | AIP Process Hardening | Meta | **Review, not ratified** | |
Numbers are permanent and are never reused, including for withdrawn proposals
(AIP-1 section 2). Numbering is contiguous from 1 to 19 with no gaps. No AIP
numbered 20 or higher exists in any Aere repository.
## Which of these are live on chain 2800
Read this before citing anything here as a network capability.
**Live:** AIP-2 (burn routing; see its outcome record for the measured amount),
AIP-3 (500 ms target, 516.4 ms measured), AIP-4, AIP-5, AIP-6, AIP-7
(precompiles `0x0AE1`..`0x0AE5` from block 9,189,161), AIP-17 (base-fee floor from
block 10,141,734), AIP-18 (EIP-2935 from block 9,189,161). AIP-9 through AIP-14
describe the decisions behind the live system.
**Not live:** AIP-8 (needs a hard fork), AIP-15 (isolated testnet only), AIP-16
(a skeleton that verifies nothing), AIP-19 (a process change under review).
**Never claimed:** post-quantum consensus. Aere consensus is classical secp256k1
ECDSA QBFT at N = 7. Post-quantum applies to signatures, accounts and
applications only. The precompiles `0x0AE6` and `0x0AE7` are testnet-only.
## Governance, stated plainly
Aere is not yet trustlessly governed. Seven validators, all Foundation-operated,
one live client, no external security audit, thin real usage. In that reality an
AIP is not ratified by a vote of independent stakeholders. **The founder decides**,
acting through the Foundation account
`0x0243A4f47D44b40b65D33f20329dE20D00c6f3C3`, which is a single-key account and
**not a deployed multisig**. Every proposal that predates decentralization carries
the label "Foundation-ratified (pre-decentralization)" so nobody mistakes
editorial ratification for governance. See `CONTRIBUTING.md` for what that means
if you are not us, and AIP-1 section 8 for the migration path.
## Filing an AIP
See AIP-1 section 6 and `CONTRIBUTING.md`. In short: copy the template, keep
every section header, cite addresses verbatim from `sdk-js/src/addresses.ts`,
label every number **measured**, **spec** or **estimate**, write "to be measured"
rather than guessing, and add a row to this index.
## Conventions
- Files are named `AIP-N.md`.
- One AIP per change. If a change has a Core part and an application part, either
file two AIPs or state clearly which layer each section addresses.
- Files are named `AIP-N.md`. One AIP per change. If a change has a Core part and
an application part, either file two AIPs or state clearly which layer each
section addresses.
- Addresses, transaction hashes, gas figures, and block numbers must be
reproducible from the chain or from a repo fixture. Marketing numbers (for
example a design-ceiling throughput) are never presented as measured results.
</content>
</invoke>
reproducible from the chain or from a repo fixture. Design ceilings (for
example a theoretical maximum throughput) are never presented as measured
results.
- A Final AIP is not edited. Corrections go in its Errata section and outcomes go
in its Post-Acceptance Outcome Record, both dated and appended (AIP-1 section
5).
## Other locations, and one stale copy
- `aere-research-repo/aips/` holds an older AIP-1 through AIP-6 whose governance
note says "three validators" and calls the Foundation account a multisig. Both
statements are false today. **This directory is authoritative** wherever the two
disagree.
- the Aere working tree holds drafts (not published in this package) of open, externally-submittable Ethereum standards
(targeting `ethereum/EIPs`, `ethereum/ERCs`, or the RIP process). Those are not
AIPs and carry no AIP number: an AIP records why chain 2800 works the way it
does with its live addresses, while an open EIP draft is the chain-agnostic
version a third party could implement.
- `aere-docs/AERE-AIP-PROCESS-AND-INDEX.md` is the published narrative version
of this index.
## Copyright
All AIPs are released to the public domain (CC0). No rights reserved.