Skip to main content

Deployed Addresses

Reference addresses for the ATS infrastructure contracts, taken from the deployment records in packages/ats/contracts/deployments/.

Verify before you rely on these

These are the latest addresses recorded in this repository, not a guaranteed-current registry. A deployment record reflects the contract version deployed at that time, which may differ from the current code. Always confirm against the newest file in deployments/<network>/ (or your own deployment output) before using an address in production.

Hedera Testnet​

Source: deployments/hedera-testnet/newBlr-2026-06-12T11-19-42-198.json (the latest recorded testnet deployment, v8.0.0) · Deployer: 0x5d0D8CE855670888044794Bf42Af7A8b9F666506

ContractContract IDEVM AddressHashScan
ProxyAdmin0.0.92122180x92664E864200b8fA891195CeEC93880F5Bfa6f22view
BLR Proxy0.0.92122260xBA2D5FC2083A0b8f164c50e65d782087fBA18E0aview
BLR Implementation0.0.92122220x86ba690fA76625162501EC1e773056870E56a06Dview
Factory Proxy0.0.92133910xd1F118A40f3b02883D35909eF2517e7EDd78379dview
Factory Implementation0.0.92126550xe6E7cd61CAB14d26b80B8181B26F45D181BF7504view

The same file lists every facet address (with resolver keys) and the configuration versions created in that deployment (Equity, the three Bond variants, Deposit token, Loan, and Loans portfolio). The BLR Proxy address is the one you pass to the SDK and to the upgrade workflows (BLR_ADDRESS).

Hedera Mainnet​

No mainnet deployment is recorded in this repository. For an official mainnet deployment, consult the project's release notes, or deploy with the current code following Deployment.

Finding addresses for any deployment​

The deployment output files are the source of truth. To read the newest one for a network:

cd packages/ats/contracts

# Infrastructure addresses from the newest testnet deployment
cat "$(ls -t deployments/hedera-testnet/newBlr-*.json | head -1)" | jq '.infrastructure'

# A specific facet
jq '.facets[] | select(.name == "CapFacet")' \
"$(ls -t deployments/hedera-testnet/newBlr-*.json | head -1)"

On-chain, the BLR proxy answers getBusinessLogicCount(), getLatestVersion(key), and resolveLatestBusinessLogic(key) (see Managing the BLR).

  • Deployment — produce a fresh deployment and its address record.
  • Architecture — what each of these contracts does.
  • SDK integration — wiring these addresses into application code.