Where the canonical contract addresses live, and what being in the registry does and does not mean.
The single source
The canonical address registry is src/addresses.ts in the SDK repository:
git.aere.network/aere-network/sdk-js
It is deliberately one file in one repository. If an address in a blog post, a diagram or an older page disagrees with it, the registry is right and the other place is stale.
This page does not restate the addresses. A list retyped into a web page is a list that goes out of date silently, and there is no reason to have two.
What the registry is
A mapping from a contract name to the address it is deployed at on chain 2800, used by the SDK so that applications do not hand-copy addresses.
What being in it does not mean
It does not mean the source has been verified against the deployed bytecode. That is a separate, smaller list.
The registry answers "where is this contract". Verification answers "is the code at that address the code we published". Only the second is a claim about trustworthiness, and the published verification table states its own coverage: how many contracts hold live runtime code, how many of those were checked, and how many are known not to reproduce from the public repository.
Read Verifying a contract for what a match proves, and Verified contracts for the current table with its coverage statement.
Checking an address yourself
Everything needed is public and needs no permission from us:
curl -s -X POST -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"eth_getCode","params":["0xADDRESS","latest"]}' \
https://rpc.aere.networkAn empty result (0x) means there is no contract at that address. Anything else is the deployed runtime bytecode, which is what a verification compares against.
The precompiles are not in this registry
The five post-quantum precompiles live at fixed protocol addresses, not deployed contracts. They are listed on Precompile ABI.