The addresses file

One JSON file per chain, generated at build from the deployment records and served from this origin. It is the first thing every integration needs — a decoded-contract submission, a TVL adapter, an indexer’s start block or an independent analyst all begin with “give us the addresses, the deploy block and the ABI”.

It is regenerated ahead of every build and every dev server, so the served copy cannot be the stale one, and it is never committed. If this documentation and the file disagree, the file is right.

Fetching it#

# What does this origin serve?
curl -s <origin>/addresses/index.json

{
  "schema": "thehood.addresses/1",
  "files": [
    { "chainId": 4663, "chainName": "Robinhood Chain", "environment": "production",
      "path": "/addresses/4663.json" }
  ]
}

schema is the string to pin against. It is "thehood.addresses/1" today and its version is bumped on any breaking shape change, so a consumer that checks it will notice a break rather than silently reading a field that moved.

What is in it#

Every field of every entry is listed on the field reference.

Prior factories#

priorFactories[] is assembled from three places, because the history is written in three and no one of them is complete: a built-in list in the app’s configuration (which carries the oldest mainnet factories, and no blocks), the retired deployment records (the only source carrying a block), and the environment’s configured prior-factory list. Each entry names its sources[] so you can see which of the three answered.

# Every factory an index has to read, current first
curl -s <origin>/addresses/4663.json \
  | jq '[.launchFactory] + [.priorFactories[].address]'

What it deliberately does not carry#

Warnings, published rather than logged#

warnings[] carries anything the generator could not resolve cleanly — an unknown chain id with no explorer links, a contract published without an ABI, or the app being pointed at a different factory from the one the deployment record names. It is in the file rather than only in a build log because the disagreement then becomes visible from outside, to the person consuming the addresses, and not only to whoever has the logs.

An empty warnings[] is the normal state. A non-empty one is worth reading before trusting anything else in the file.

Top level#

contracts[] and cloneTemplates[]#

contracts[] holds the singletons: one address each, on this chain, in this environment. cloneTemplates[] holds the families that have no fixed address, carrying the same fields minus the address and its block, plus deployedAtRuntime: true.

treasuries[] and externalContracts[]#

Only destinations appear in treasuries[] — places value comes to rest. A keeper key is readable on chain from the contract that holds it and is not published here. externalContracts[] is the inverse: addresses this platform reads but did not deploy, published because a USD-denominated figure cannot be reproduced without naming the same price feed, and a pool cannot be found without the PoolManager it was opened on.

thdBuckets[]#

A shareBps read on chain that disagrees with the file means the file describes a different deployment, not drift — the eleven shares are immutable and have no setter. See THD and the fee meter.

priorFactories[], notDeployed[], deploymentRecords[]#

A worked example#

{
  "name": "<ContractName>",
  "kind": "singleton",
  "source": "contracts/src/<area>/<ContractName>.sol",
  "purpose": "<what the contract does>",
  "abiPath": "/abis/<ContractName>.json",
  "address": "0x…",
  "record": "<record>-<chainId>.json",
  "recordField": "<recordKey>",
  "deployRunBlock": "<block>",
  "deployRunAt": { "unix": "<seconds>", "iso": "<ISO-8601>" },
  "explorerUrl": "…/address/0x…"
}

The address is elided here on purpose: this page is a schema, and an address copied into documentation is a mirror that will one day disagree with the deployment it claims to describe. Read every address from the file.