@artblocks/abx-sdk 0.1.0-alpha.32 → 0.1.0-alpha.33

package/CHANGELOG.md

@@ -1,102 +1,8 @@
 # @artblocks/abx-sdk
 
-## 0.1.0-alpha.32
-
-### Minor Changes
-
-- 0fed512: `deploy-code`'s post-deploy setup (script chunks, PostParam schemas, dependency declarations,
-  on-chain-URI legs, reserve mints) no longer rides one atomic multicall no matter how large the
-  on-chain script is. A 60KB script (3 chunks) produced a setup transaction wanting 17,307,586 gas
-  against the ~16,777,216 (2^24) `eth_estimateGas` ceiling — not the block gas limit — and failed with
-  a useless "gas limit too high", leaving a verifiably half-configured contract on chain.
-
-  The setup now splits into gas-bounded transactions when it doesn't fit one: every script-chunk batch,
-  then every config (schema/dependency/on-chain-URI) batch, then every mint batch, in that order and
-  never mixed. Script-chunk writes and config setters are idempotent, so an interruption at any split
-  point is finished by the existing `deploy-code --resume` (which now also gas-batches whatever it
-  finds missing); mints ride strictly last because a mint is the one non-idempotent leg. A setup that
-  already fit one transaction is unaffected — same single combined multicall as before. There is no new
-  size-based refusal; the dry run's `transactions`/`approvals` reports the real transaction count and
-  cost for the whole plan.
-
-  `@artblocks/abx-sdk` exports the reusable pieces: `packCallsByGas` (a generic gas-bounded bin packer,
-  the call-level sibling of `planContentTxs`'s own batching), `estimateChunkGasForBytes`, and
-  `SETUP_LEG_GAS` (flat gas estimates for a schema/dependency/on-chain-URI/mint call).
-
-## 0.1.0-alpha.31
-
-### Minor Changes
-
-- c068a0f: Add `probeChunkStore` — a fail-closed sibling to `ensureChunkStore` that resolves whether a usable
-  on-chain chunk store exists (configured address, has code, answers the current `writeContent` ABI)
-  without ever sending a transaction or deploying one. Returns a typed verdict (`ok` / `unconfigured` /
-  `no-code` / `incompatible` / `unreachable`) instead of throwing, so a request-scoped or read-only
-  service can call it at startup and branch on the reason.
-- c068a0f: Local data-directory resolution (`.abx-self-host` / `ABX_DATA_DIR`) is now centralized in one SDK
-  resolver (`resolveDataDir` from `@artblocks/abx-sdk/node`) instead of five independent copies of the
-  same fallback across the CLI, indexer, and storage packages — the setup that could silently split a
-  project's SQLite projection from its managed Arweave key into two different directories.
-
-  A handful of READ commands (`status`, `state`, `verify`, `doctor`, `capabilities`, `tokens`,
-  `tokenuri`, `contracturi`, `inspect`, `minter show`) now search upward from the current directory,
-  git-style, for an already-existing `.abx-self-host` before falling back to creating one at cwd —
-  bounded at the home directory, a `.git` repository root, or the filesystem root, and never crossing
-  into an unrelated directory tree. Running one of these from a project subdirectory (e.g. a
-  `contracts/` folder) now finds the same node a run from the project root would, instead of quietly
-  reporting an empty one. `abx status`'s existing `data: <path>` line — and a new one-line notice —
-  name the directory whenever it was found this way. Every WRITE command is unaffected: it always
-  resolves strictly to the current directory, exactly as before, so nothing is ever created somewhere
-  you didn't `cd` into. `ABX_DATA_DIR`, when set, still always wins outright and disables the search
-  entirely.
-
-- c068a0f: `deploy-code --resume <address>` now works against an EditionCode (`--copies`) target, not just
-  SeriesCode. The mint leg diffs per id against that id's own `totalSupply(id)` — pass the same
-  content flags the original deploy used, plus `--mint-count`/`--mint-amount` if it premint any ids.
-- c068a0f: `reconstructProject()` and `reconstructIncremental()` accept `toBlock: 'safe' | 'finalized'` in
-  addition to a literal block number and the existing `'latest'` default. The tag is resolved to a
-  concrete inclusive block number (via the new `resolveBlockTag()`) before any `eth_getLogs` scan
-  starts, and that number — never the tag — is what lands in the persisted `ProjectState.toBlock`. An
-  RPC that doesn't support the requested tag throws the new `BlockTagUnavailableError` instead of
-  silently falling back to `latest`. `SelfHostIndexer#reindex` gained a matching `blockTag` option.
-  Existing callers (the `'latest'`/unset default) are unaffected.
-
-  `abx index --to-block safe|finalized` stops a re-index at a reorg-safe boundary.
-
-- c068a0f: Add `abx replace-script <address> --script <file>` — a safe, first-class way to replace an UNLOCKED
-  code project's on-chain program (`SeriesCode`/`EditionCode`, before `abx lock-script`). It refuses
-  outright on a locked script or a non-code target, diffs the replacement by content against what's
-  on-chain (an index that already matches is never re-sent), handles a smaller replacement by queuing
-  the trailing `removeLastScriptChunk` calls it needs, folds every write and remove into ONE atomic
-  transaction (a revert can never leave a half-applied script), and reads the completed script back to
-  verify it reassembles exactly to the file before reporting success. Supports `--dry-run` and every
-  signing lane.
-
-  The SDK gains the primitives this is built on: `prepareSetScriptChunk`/`prepareRemoveLastScriptChunk`
-  (no `prepare*` wrapper existed for `OnChainScript.sol`'s writers before this — every caller hand-
-  encoded `encodeFunctionData`), plus `planScriptReplace`/`verifyScriptReplace`, which take a small
-  reader interface (mirroring `resume.ts`'s own reader seam) so the diff and post-write verification
-  are testable without a chain.
-
-- c068a0f: Additive for SDK consumers — a new exported function, nothing existing changed shape or behavior.
-
-  `abx verify` now compares a collection's actual `tokenURIRenderer` and `animation_url` generator
-  pointers against the current canonical singletons for its chain, reporting each as current or
-  not-current (never treating an older-but-working deployment as broken). Adds the SDK helper
-  `isCurrentGenerator` alongside the existing `isCurrentRenderer` probe.
-
-### Patch Changes
-
-- c068a0f: `decodeReader` now requires the canonical `abi.encode(address reader, address pointer)`
-  shape — exactly two 32-byte words, each zero-padded — and rejects truncated, trailing-byte,
-  or double-encoded `reader` field values with an actionable error instead of silently
-  decoding a wrong address pair.
-
-## 0.1.0-alpha.30
+## 0.1.0-alpha.33
 
 ### Patch Changes
 
-- 64248d9: Establish the public source baseline and refresh dependency constraints.
-
-## Unreleased
-
-Public release history begins here.
+- 9242a05: Prepare package metadata, release notes, and public-facing source comments for the initial public
+  source release.

package/dist/deployments.d.ts

@@ -115,13 +115,13 @@ export declare function resolveFixedPriceMinter1155(chainId: number, override?:
 export declare function resolveGenerator(chainId: number, override?: string): Address | undefined;
 /**
  * Is `generator` the chain's CURRENT canonical generator — the per-collection pointer check
- * `abx verify` runs for the singleton `generatorFor(state)` resolves (site/content/docs, #128).
+ * `abx verify` runs for the singleton `generatorFor(state)` resolves (see site/content/docs).
  *
  * Binary by construction, on purpose: it answers current / not-current and nothing finer. A
  * mismatch can mean either "pinned to a prior canonical generation" or "a fully custom field
  * renderer", and this file's own docstring is explicit that no superseded generator address is
  * EVER kept as live state here — so there is nothing recorded to tell those two apart against.
- * Building that historical registry is the out-of-scope half of #128 (the factory-generation
+ * Building that historical registry is deliberately out of scope (the factory-generation
  * ladder already has one, {@link ANCHOR_GENERATIONS}; the generator deliberately does not).
  *
  * `null` ⇒ this chain has no canonical generator recorded at all (unshipped) — a different fact

package/dist/deployments.js

@@ -175,13 +175,13 @@ export function resolveGenerator(chainId, override) {
 }
 /**
  * Is `generator` the chain's CURRENT canonical generator — the per-collection pointer check
- * `abx verify` runs for the singleton `generatorFor(state)` resolves (site/content/docs, #128).
+ * `abx verify` runs for the singleton `generatorFor(state)` resolves (see site/content/docs).
  *
  * Binary by construction, on purpose: it answers current / not-current and nothing finer. A
  * mismatch can mean either "pinned to a prior canonical generation" or "a fully custom field
  * renderer", and this file's own docstring is explicit that no superseded generator address is
  * EVER kept as live state here — so there is nothing recorded to tell those two apart against.
- * Building that historical registry is the out-of-scope half of #128 (the factory-generation
+ * Building that historical registry is deliberately out of scope (the factory-generation
  * ladder already has one, {@link ANCHOR_GENERATIONS}; the generator deliberately does not).
  *
  * `null` ⇒ this chain has no canonical generator recorded at all (unshipped) — a different fact

package/dist/node.d.ts

@@ -35,9 +35,9 @@ export interface ResolveDataDirOptions {
  * indexer's SQLite store, the storage package's local-disk backend, content index, and managed
  * Arweave key — used to carry an INDEPENDENT copy of `ABX_DATA_DIR ?? cwd/.abx-self-host`, which is
  * exactly the setup that silently splits one project's SQLite projection from its managed Arweave
- * key into two different directories the moment any single copy drifts from the others (issue
- * #121's "keep managed Arweave key location and projection location coherent" criterion). Every
- * one of those call sites now resolves through here instead.
+ * key into two different directories the moment any single copy drifts from the others. To keep
+ * managed Arweave key and projection locations coherent, every one of those call sites now
+ * resolves through here instead.
  *
  * `ABX_DATA_DIR` always wins outright — set it and discovery never runs, full stop. That isolation
  * is load-bearing (tests rely on it to run concurrently against disposable temp dirs; an operator
@@ -48,13 +48,13 @@ export interface ResolveDataDirOptions {
  * per-command allowlist in `config.ts`), and only when nothing already exists at cwd, this walks
  * UP the directory tree looking for an EXISTING `.abx-self-host`, so (say) `abx status` run from a
  * project subdirectory finds the same node a run from the project root would — instead of quietly
- * opening a second, empty one (the bug in #121).
+ * opening a second, empty one.
  *
  * The search is BOUNDED, git-style — it stops at (but still checks) the user's home directory, a
  * directory containing `.git` (a repository root), or the filesystem root, so it can never wander
  * into an unrelated ancestor tree. And it never merges two directories: the first EXISTING
  * `.abx-self-host` found wins outright, and `source: 'discovered'` tells the caller to say so — a
- * discovered node is not the one a human just `cd`-ed into, and #121 requires that stay visible
+ * discovered node is not the one a human just `cd`-ed into; that distinction must stay visible
  * rather than silently answering from the wrong place.
  */
 export declare function resolveDataDir(options?: ResolveDataDirOptions): DataDirResolution;

package/dist/node.js

@@ -30,9 +30,9 @@ function isDirectory(path) {
  * indexer's SQLite store, the storage package's local-disk backend, content index, and managed
  * Arweave key — used to carry an INDEPENDENT copy of `ABX_DATA_DIR ?? cwd/.abx-self-host`, which is
  * exactly the setup that silently splits one project's SQLite projection from its managed Arweave
- * key into two different directories the moment any single copy drifts from the others (issue
- * #121's "keep managed Arweave key location and projection location coherent" criterion). Every
- * one of those call sites now resolves through here instead.
+ * key into two different directories the moment any single copy drifts from the others. To keep
+ * managed Arweave key and projection locations coherent, every one of those call sites now
+ * resolves through here instead.
  *
  * `ABX_DATA_DIR` always wins outright — set it and discovery never runs, full stop. That isolation
  * is load-bearing (tests rely on it to run concurrently against disposable temp dirs; an operator
@@ -43,13 +43,13 @@ function isDirectory(path) {
  * per-command allowlist in `config.ts`), and only when nothing already exists at cwd, this walks
  * UP the directory tree looking for an EXISTING `.abx-self-host`, so (say) `abx status` run from a
  * project subdirectory finds the same node a run from the project root would — instead of quietly
- * opening a second, empty one (the bug in #121).
+ * opening a second, empty one.
  *
  * The search is BOUNDED, git-style — it stops at (but still checks) the user's home directory, a
  * directory containing `.git` (a repository root), or the filesystem root, so it can never wander
  * into an unrelated ancestor tree. And it never merges two directories: the first EXISTING
  * `.abx-self-host` found wins outright, and `source: 'discovered'` tells the caller to say so — a
- * discovered node is not the one a human just `cd`-ed into, and #121 requires that stay visible
+ * discovered node is not the one a human just `cd`-ed into; that distinction must stay visible
  * rather than silently answering from the wrong place.
  */
 export function resolveDataDir(options = {}) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@artblocks/abx-sdk",
-  "version": "0.1.0-alpha.32",
+  "version": "0.1.0-alpha.33",
   "license": "MIT",
   "description": "Typed SDK for ABX protocol reads, deployments, operations, reconstruction, and verification.",
   "type": "module",
@@ -49,7 +49,7 @@
     "access": "public"
   },
   "dependencies": {
-    "viem": "^2.56.0"
+    "viem": "^2.56.3"
   },
   "devDependencies": {
     "esbuild": "^0.28.2"