Networks and deployments

Production networks are disabled in this release. Start on Base Sepolia. Sepolia is also supported; Arbitrum Sepolia has canonical contracts for explicit qualification work.

“Experimental” means the network is ready for deliberate qualification, but is not yet a recommended default. “Disabled” means the CLI refuses to operate on the network.

The machine-readable sources of truth are chain-support.json for network status and deployments.ts for addresses. If this page differs, the SDK data wins.

Shared addresses

The keyless CREATE2 proxy deploys the current abx-core-v3 contracts at the same address on all three testnets.

Address resolution follows this order: explicit option, environment override, SDK manifest.

Chain-specific generator

AbxGenerator includes chain-specific dependency configuration, so its address differs.

Sepolia also has the Art Blocks DependencyRegistryV0 at 0x5Fcc415BCFb164C5F826B5305274749BeB684e9b. Base Sepolia and Arbitrum Sepolia have no canonical dependency registry.

Contract generations

abx-core-v3 is current for new deployments. It is the first release candidate built from an exactly synchronized public source and generated-bytecode set. Its token runtime behavior matches the final v2 generation apart from reporting core version 3.

abx-core-v2 remains supported for existing collections: reads, writes, indexing, and serving stay enabled. New deployments use v3. The append-only generation registry in the SDK contains the six v2 factory addresses for provenance and compatibility.

Verify a project

abx verify 0xYourContract
abx state 0xYourContract

Canonical status comes from a factory's isAbxClone record. The SDK also reports older known factory generations as provenance without treating them as current trust anchors.

abx verify separately compares an already-deployed collection's ACTUAL singleton pointers — its tokenURIRenderer and its animation_url generator — against the addresses on this page, and reports each as current or not-current. Unlike the factory ladder above, this manifest keeps no history of a superseded renderer or generator address (see deployments.ts's file docstring): a prior deployment and a fully custom implementation both read as "not current", because there is nothing recorded here to tell them apart. That is a deliberate scope limit, not an oversight — a history registry for these two singletons is a future tranche, not this one.

Because existing collections read these addresses dynamically off this manifest (never storing a resolved value on their own for the un-pinned lane), any change to a canonical shared singleton address in this file must be called out explicitly in that package's release notes — a changeset that bumps @artblocks/abx-sdk silently is not enough for an address every deployed project's abx verify compares itself against.

All listed contracts should be source-verified in the appropriate block explorer. An unverified canonical address is a release bug.