abx.
Using ABXGuides

Operate a project

These commands run against a live project. Each command that writes to the chain uses a signing lane and accepts --dry-run.

Ownership and payouts

  • abx transfer <address> --to 0x... [--token <id>]: move a token to a new holder.
  • abx set-royalty <address> --bps <0-10000> [--receiver 0x...]: change the royalty.
  • abx set-transfer-validator <address> <0x...|none|recommended>: re-point or suspend an ERC-721C collection's transfer validator. Only for a collection that enrolled at deploy.
  • abx set-admin <address> --to 0x...: hand over contract ownership.

Metadata and hosting

  • abx set-token-uri <address> --uri <base>: re-point token metadata to a resolver base. Use --override <uri> --token <id> to pin one token to a fixed locator.
  • abx set-contract-uri <address> --uri <base>: re-point the collection metadata.
  • abx set-renderer <address>: toggle URI resolution between on-chain and off-chain. --off clears to off-chain.
  • abx refresh <address> [--token <id>]: ask marketplaces to re-index. On a 721, ABX emits ERC-4906 on a metadata change and this nudges a marketplace to read it. An ERC-1155 edition emits no ERC-4906 (the standard is 721-only), so after a URI or renderer re-point also run abx ping-uri <address> --token-ids <ids> to re-emit the native URI event — abx refresh tells you which case applies.

Data plane

  • abx attach <address> <key> <uri>: attach a named, typed file to the token's data plane. --file <path> stores small bytes on-chain instead of a URI. Use --collection or --token <id>.
  • abx set-field <address> --field <name> ...: set an on-chain metadata field directly.

Freezing

  • abx lock-field <address> --field <name>: freeze a field permanently.
  • abx lock-uri <address>: freeze the URI configuration permanently. With the fields also locked, the metadata cannot change.

Editions

An edition (--copies) uses id-scoped variants of the commands above, plus two edition-only verbs:

  • abx mint <address> --token-id <n> --amount <n>: mint n copies of one id. --token-id defaults to 0 on a one-artwork edition; it's required on a multi-artwork edition (EditionImage/EditionCode).
  • abx transfer <address> --amount <n> --from 0x... --to 0x...: move n copies of an id between holders. --from is required — an id can have many concurrent holders, so there's no single on-chain "owner" to default from.
  • abx set-max-supply <address> --token-id <n> --cap <n>: lower one id's ERC-1155 supply cap — the per-id twin of set-max-invocations. Monotonic: the cap can only decrease, never below that id's current supply, and once set it can never return to open (--cap open is refused).
  • abx ping-uri <address> --token-ids <csv|range>: permissionlessly re-emit the native ERC-1155 URI event for the given ids. A contract-wide re-point (set-token-uri/set-renderer) emits its own config event but not a per-id one, so a consumer that honors only the native event needs this nudge after a re-point.

abx state <address> and abx tokens <address> both detect an edition automatically and report per-id supply/cap instead of a single owner — there is no whole-contract "supply" on an edition, since each id has its own. See Sales for per-id pricing.

Moving and removing

  • abx migrate <address> --from <url> --to <url>: move off-chain state to a new resolver, verifying parity first. See Self-hosting.
  • abx forget <address>: drop the local registration and projection. The chain is untouched.

On this page