Skip to main content

Contract Addresses

Canonical Notareum contract addresses per network. The protocol is deployed initially on Ethereum Sepolia for public testing. Mainnet deployments are pending final audits and governance activation. All addresses here are TBD until the testnet launch.

Networks

Ethereum Sepolia (testnet)

Core contracts

Token contracts

Access and governance contracts

Block explorer

Once deployed, each contract is verified on Etherscan-compatible explorers:
  • https://sepolia.etherscan.io/address/<contract>
  • https://sepolia.blockscout.com/address/<contract>

Ethereum Mainnet

All addresses: TBD, pending audits and governance activation. Mainnet deployment requires:
  1. Completed external audit with published report.
  2. Successful testnet operation for the governance-set minimum observation window.
  3. Passing governance proposal to schedule mainnet deployment.

Canonical address source

Every SDK resolves addresses from a canonical addresses.json file served from the protocol GitHub release artifacts. This prevents hardcoded addresses from drifting in integrations.

File location

Example network folders:
  • deployments/sepolia/addresses.json
  • deployments/mainnet/addresses.json
Each release also attaches the addresses.json set for every supported network as a GitHub release asset.

File shape

Fields are stable across versions. New entries are additive.

Fetching programmatically

TypeScript

fetchAddresses fetches addresses.json with integrity checks (SHA-256 matching the latest release manifest). In production, pin to a specific release tag to avoid surprises.

Python

Rust

Shell

Pinning to a release

To make integrations reproducible, pin the address set to a specific release tag:
This reads the artifact attached to the release (immutable) rather than the mutable main branch. Recommended for production.

Migration policy

If an address changes (e.g., a proxy is migrated to a new deployment), the release notes include:
  1. The old and new addresses.
  2. The migration window during which both are live.
  3. The deprecation date of the old address.
  4. Integration steps required to cut over.
SDKs surface an addressDeprecated warning when the configured address is no longer current per the latest addresses.json.

Integrity

The addresses.json file is signed by the governance multisig. The SDK’s fetchAddresses verifies the signature against the known protocol public key before returning the parsed content.
Disabling signature verification is permitted for local testing but flagged in logs.