Who operates chain 2800 today, and where the path from here is written down.
Who operates the validator set
The AERE Foundation operates the validator set today. Nine validators, quorum six of nine.
The Foundation stewards the protocol, maintains the open-source codebase and funds contributors through a public grants program. What it does, how it is funded and how to engage with it is on the Foundation page.
What that means for a verification you run
Every check offered through rpc.aere.network is, in the end, performed against a machine the Foundation operates. That is true of every chain's public endpoint, and it is the reason the node package, the genesis file and the exact follower options are published: so that a check can be run somewhere else.
If a result matters to you, run it against your own node. See Run a node.
Audit status
The network has not completed a third-party security audit. The proofs, conformance tests and verification tools published by the project are its own work, offered so that anyone can re-run them rather than take them on trust.
Client diversity
Mainnet blocks are produced by the AERE client, which is Hyperledger Besu with the published patches. A second, independently derived client exists and produces blocks on a public test network, including post-quantum seals. Moving a second client into mainnet production is a validator-set decision rather than a code question.
Where the path is published
The decentralization path is set out in the project roadmap and in the whitepaper, both of which are linked from the About page. This documentation covers how the chain works; the roadmap covers where it is going.