Deployed Addresses

The addresses below are the shared contracts on æternity mainnet (ae_mainnet) and testnet (ae_uat). Per-community contracts (token, sale, DAO, community management) are deployed by the factory and resolved per token. See Reading addresses at runtime.

Mainnet (ae_mainnet)

The mainnet factory was deployed at key block height 1089546. Start an indexer backfill of factory events from there. The governance registry is older: its backfill starts at height 164578.

Testnet (ae_uat)

The testnet factory was deployed at key block height 1097291; the testnet governance registry backfill starts at height 168710.

Reading addresses at runtime

Everything hangs off the factory, so one lookup resolves the whole graph. The Superhero web app fetches the active factory from the API rather than hardcoding it.

Get the factory from the API

curl -s https://api.superhero.com/api/factory

The response is the community factory schema:

address                   ct_... the CommunityFactory
deployed_at_block_height  int, the key block the factory was deployed at
bctsl_aex9_address        ct_... the ProtocolDAO token
affiliation_address       ct_... the AffiliationTreasury
collections               map of collection id -> collection data

Collection ids have the shape <name>-<creator address>, for example WORDS-ak_.... create_collection stores the submitted name, a dash, and the caller's address, so the id you pass to create_community is the full concatenated string, not the bare name.

Read shared addresses from the factory

Every shared address is an entrypoint on the factory, so you can resolve them on chain without the API:

import { AeSdk, Node, Contract } from '@aeternity/aepp-sdk';
import fs from 'fs';
 
const aeSdk = new AeSdk({
  nodes: [{ name: 'mainnet', instance: new Node('https://mainnet.aeternity.io') }],
});
 
const factory = await Contract.initialize({
  aci: JSON.parse(fs.readFileSync('./contracts/CommunityFactory.aci.json', 'utf8')),
  address: 'ct_25cqTw85wkF5cbcozmHHUCuybnfH9WaRZXSgEcNNXG9LsCJWTN',
  onNode: aeSdk.api,
});
 
const treasury   = await factory.affiliation_treasury().then((r) => r.decodedResult);
const daoToken   = await factory.protocol_dao_token().then((r) => r.decodedResult);
const curve      = await factory.bonding_curve().then((r) => r.decodedResult);
 
console.log({ treasury, daoToken, curve });

affiliation_treasury(), protocol_dao_token() and bonding_curve() are non-stateful reads: they cost nothing and need no account.

Resolve per-community contracts

Given a collection id and a token name:

The factory has no getter for the DAO. Read it from the sale contract's state (get_state().dao_contract), or capture all three addresses from the CreateCommunity event, which carries the DAO, the sale and the community management contract.

If you already have a sale address, GET /api/tokens/<sale address> returns the same set of addresses without any chain calls.

Related

• Calling Contracts: how to turn one of these addresses into a working contract instance
• CommunityFactory: the entrypoints used above to resolve addresses
• Networks: node, middleware and explorer endpoints for both networks
• Factory and contracts API: the REST endpoints that serve the factory schema
• aeScan block explorer (opens in a new tab): inspect any address, its state and its calls