Legal disclosures

Effective as of 2026-05-31 · Updated continuously · Canonical source: aere.network/legal

This page is the canonical source of AERE Foundation's regulatory and operational disclosures. It is referenced from every marketing communication and the project whitepaper §8. Material changes are timestamped above.

1. Forward-looking statements

The AERE Network website, whitepaper, blog, and other communications contain forward-looking statements regarding the network's architecture, performance targets, validator decentralisation, custody model, ecosystem partners, and product roadmap. These statements reflect current expectations and are subject to risks, uncertainties, and assumptions. Actual outcomes may differ materially. AERE Foundation undertakes no obligation to update forward-looking statements except as required by applicable law.

2. Current network state

2.1 Consensus & validators

2.2 EVM ruleset

2.3 Performance

The "273,044 TPS" figure cited in marketing communications reflects QBFT-architecture testnet benchmarks under specified conditions. Sustained mainnet throughput under real load varies and is publicly observable via the live indexer at api.aere.network and the block explorer at explorer.aere.network. Real-time block metrics are available at aere.network/network-status.html.

2.4 Verification-node geography

The "800+ verification nodes across 61 countries" figure cited in marketing is a Phase 3 target for the public RPC, observer, and archive-node program, not a current production count. The current verification-node geography is reported on aere.network/network-status.html. Verification nodes are non-consensus nodes, they relay transactions, serve RPC, and store history; they do not participate in block production.

2.5 Deployed contracts

The canonical list of deployed smart contracts on AERE chain 2800 is maintained at aere.network/docs.html#contracts and in the open-source SDK address book at git.aere.network/aere-network/sdk-js (src/addresses.ts). Every published address can be verified via the public block explorer.

3. Custody model

3.1 Chain-level

AERE Network is a non-custodial settlement layer. The chain itself does not custody user assets. AERE balances and smart-contract state are controlled exclusively by private-key holders. Foundation-controlled contracts (where they exist) are limited to administrative parameters such as oracle reporter sets, validator set rotation, and protocol fee policies; user balances are never held by the Foundation.

3.2 Application-level

Applications built on AERE are operated by independent parties under their own terms. Some applications may offer additional services, including custodial fiat services (such as IBAN accounts), through licensed third-party partners. Where applicable, custodial services are subject to the partner's own authorisations and disclosures.

Bank28. Bank28 is a non-custodial neobank application built on AERE Network. Bank28 operates an independent brand and is published at bank28.app. Bank28's crypto wallet is non-custodial, users hold their own private keys. Future Bank28 fiat services (IBAN accounts, card products) will be provided in partnership with a licensed Electronic Money Institution (BaaS provider) that holds the EMI authorisation and custody of the fiat reserve. Custody disclosures for Bank28's fiat services are published at bank28.app under Bank28's own legal terms when those services launch.

4. Regulatory status

AERE Network is a permissionless EVM Layer 1 blockchain. The AERE token is the network's native utility and gas token. Nothing on aere.network, in the AERE Network whitepaper, in AERE Foundation communications, or referenced from this Legal page constitutes investment advice, an offer to sell, or the solicitation of an offer to buy any security or financial instrument. Token holders and prospective users should independently verify the legal status of AERE in their jurisdiction before acquiring, holding, or transacting.

For European users: AERE Network communications are issued in accordance with applicable provisions of Regulation (EU) 2023/1114 (MiCA). For UK users: communications follow the FCA's Cryptoasset Financial Promotions regime where applicable. AERE Foundation does not solicit users in jurisdictions where the offering or promotion of crypto-assets is prohibited.

5. Technology & operational risks

6. Trademarks and brand

AERE, AERE Network, and the AERE marks are trademarks of AERE Foundation. Bank28 and Bank28-related marks are operated by their respective brand owners. References to Hyperledger Besu, QBFT, Ethereum, JPMorgan Onyx, ConsenSys, the Enterprise Ethereum Alliance, Apple, Google, Microsoft, YubiKey, and any other third-party trademarks are descriptive references to the underlying technology, standards, or trademark holders, and do not imply endorsement.

7. Contact & updates

Material updates to the network state, contract registry, validator set, custody model, or partnership disclosures are published on this page with the updated effective-as-of date above. Inquiries regarding regulatory status, audit reports, or partnership disclosures may be directed to AERE Foundation through git.aere.network.

This Legal page is supplemented by separate Terms of Use and Privacy Policy documents.