Documentation for agents: an index at /llms.txt, every docs page in one file at /llms-full.txt, and Markdown for any docs page by adding .md to its URL.

Skip to Content
ensforgeSDK

Changelog

Release notes for @ensforge/sdk, newest first, from its GitHub releases.

November 2026

  1. @ensforge/sdk@1.0.1

    Patch Changes

    • e338a7f: Actions now declare the error codes they can raise (wallet, nonce, RPC, indexer, gateway, plan, commitment, migration and name-state codes), so their typed errors and the API reference list every code an action can fail with.
    • a393fc9: docsUrl on every ensforge error now points to the error's page in the API reference, https://ensforge.com/docs/reference/errors/<CODE> (it was https://ensforge.com/errors/<CODE>).
    • 9c3051f: - Errors.describe gives end-user copy for the error codes of packages that extend ensforge (such as @ensforge/hca), and falls back to generic copy instead of throwing for a code it does not know.
      • New Plan.deserializeRecord reads back a saved plan record for custom plan stores; Plan.localStorage() now rejects broken records with PLAN_INVALID.
      • Actions.batch runs reads of extension packages, such as @ensforge/hca.
      • Removed the error codes nothing raised: PRICE_ABOVE_MAXIMUM, DNS_OWNER_MISMATCH and TRANSACTION_REPLACED. INSUFFICIENT_ETH and CONTRACT_NOT_DEPLOYED are documented as errors any write or action can fail with.
      • More examples for Fuse, Name, Role, CoinType, ContentHash and Duration, corrected docs (grace-period renewals, avatar gateways, batch gateways), and a new README.
    • Updated dependencies [9c3051f]
      • @ensforge/contracts@1.0.1
  2. @ensforge/sdk@1.0.0

    Major Changes

    • 1743efc: ensforge 1.0: a rewrite of the SDK for ENSv1 and ENSv2. @ensforge/core is now @ensforge/sdk; the 0.x config-bound @ensforge/sdk client and every ./legacy entry are removed.

      • Ensforge.create({ publicClient, walletClient }) with action groups added by extend(ensActions()), or standalone Actions.<domain>.<action>(client, options); the same actions return Effects from @ensforge/sdk/effect.
      • 124 actions across names, records, resolvers, registration and renewal, subnames, registries, permissions, roles, approvals, primary names, the NameWrapper, DNS, migration to ENSv2, events and plans.
      • Writes are plans: .prepare, .simulate, .estimateGas, EIP-5792 batching, resume after failures, …Sync variants that wait for receipts, pluggable routes (via) and paymasters.
      • Pluggable indexers: bigname(), goldsky(), fallback() and defineIndexer() for lists, history and search.
      • Ensforge.fromWagmi in @ensforge/sdk/wagmi, for wagmi 2 and 3.
      • Typed errors with codes, hints and Errors.describe for UI copy. Each action's ErrorType, and its Effect error channel, is the classes its @throws documents plus Errors.CommonError (or Errors.WriteError for writes).

    Patch Changes

    • Updated dependencies [1743efc]
      • @ensforge/contracts@1.0.0

October 2026

  1. @ensforge/sdk@0.6.1

    Patch Changes

    • 4ebad9b: Support viem versions from 2.49.0 and use a peer dependency in the contracts package so applications can share their installed viem version.

      Keep V1 names visible when both indexers are enabled. Interpret indexed migration flags as ENSv1-to-ENSv2 migration rather than the historical V1 registry migration.

      Include names without a recorded expiry in expiryAfter filters, with consistent local filtering and pagination on the V2 indexer. Upper expiry bounds continue to require a recorded expiry.

    • Updated dependencies [4ebad9b]

      • @ensforge/core@0.6.1
  2. @ensforge/sdk@0.6.0

    Minor Changes

    • 9d82878: Migrate Sepolia ENSv2 to the October 1 deployment snapshot 07e55a05. Update contract addresses and deployed ABIs, export the ENS URI renderers and VerifiableFactory address prediction, and refresh the indexer schema and migration guides. Mainnet behavior is unchanged.

      Support idempotent HCA deployment: preserve verification of existing accounts after deployment approval is revoked, reject unapproved new deployments, and report account reuse when deployments race. Recreate Sepolia fixtures and HCA accounts for the new factory, keeping workflow state separate from earlier deployments.

      Update the pinned devnet build and preserve the deployed Solidity submodule revisions rather than replacing them with revisions from the stale upstream lockfile.

      Require Effect 4 stable (effect@^4.0.0) and migrate HTTP and reactivity imports to their new export paths. Upgrade the React Atom integration to 4.0.0 and preserve HCA funding status return types with the updated Effect inference.

      Applications upgrading from the release candidate must install effect@^4 alongside ensforge. Update any direct imports from effect/unstable/http and effect/unstable/reactivity to effect/http and effect/reactivity.

    Patch Changes

    • Updated dependencies [9d82878]
      • @ensforge/core@0.6.0

September 2026

  1. @ensforge/sdk@0.5.0

    Minor Changes

    • afe2eab: Migrate the Sepolia ENSv2 profile to deployment snapshot 71a3b733, including deployed ABIs, resolver permissions and record setters, registration, registry transfers, and HCA upgrade sets.

      HCA sessions now use reusable owner-signed authorization proofs rather than an on-chain enablement transaction. Pass the returned proof through the session authorization when executing with Rhinestone. Recreate Sepolia HCA accounts and fixtures for the new factory; old deployment workflow state and session proofs are not compatible.

      Add deployment verification commands, a pinned local devnet build, and updated playground setup and migration documentation. Mainnet behavior is unchanged.

      Sepolia Permissioned Resolver grants now require explicit scope-widening consent because record-key roles apply across names. Public-key writes and bulk record clearing are unsupported on that resolver. Registry transfers remain safe by default and expose an explicit unsafe-transfer option for compatible registry workflows.

      Fix Rhinestone stateless-session signing and validate HCA registrar token approvals against the current rent oracle, including mintable Sepolia test tokens. Update HCA funding examples to distinguish registration token balances from refund and cross-chain funding. Decode the new ENSv2 resolver record-update event formats and refresh live migration fixtures.

      Refresh the Sepolia V2 GraphQL schema and generated operations. Include record-model updates in general event-history filters and decode EAC role changes from their resulting bitmap, including complete revocation. Allow schema refreshes for a single protocol.

    Patch Changes

    • Updated dependencies [afe2eab]
      • @ensforge/core@0.5.0
  2. @ensforge/sdk@0.4.0

    Minor Changes

    • 0ced8e8: Support custom ENS V1 and V2 deployment profiles in Viem and Wagmi configuration. Validate chain IDs and complete contract address groups, snapshot custom deployments, and avoid inheriting preset indexer endpoints. Resolved network IDs and chain IDs now support arbitrary deployments; runtime deployment provenance is optional.

    • f53985c: Default SDK instances to their own memory workflow storage, and React providers created from config to lazy IndexedDB storage. Preserve caller-supplied storage and SDK instances. Keep the Effect service context when adding default storage to an existing core config.

    • e48eedc: Add HCA account inspection, EntryPoint deposits and owner-authorized withdrawals, signature verification, and upgrades with both directional gate checks. Expose factory, upgrade-gate, and trusted-set governance through hca/admin and sdk.hca.admin. Include exact deployed ABI fragments and an explicit function-coverage catalogue.

    • 0943f56: Add the optional HCA adapter package with typed execution envelopes, versioned tracking codecs, review and fee policies, and capability extensions. Preserve provider submission types through the SDK and add shared bounded execution waiting/watching with cancellation and receipt confirmation checks.

      Reserve type-only Rhinestone and Pimlico entrypoints for the initial provider integrations.

    • b9073ba: Add 16 HCA account, deployment, owner-execution and tracking actions with the existing sdk.hca group. Support direct atomic owner transactions and an explicit execution adapter boundary without wallet fallback. Add matching execution ABI fragments, profile configuration, session revocation, and validated submission tracking. Provider packages and session execution remain future work.

    • 9bef00b: Add resumable same-chain HCA registration with caller-owned revision-checked storage, explicit spending limits, atomic registration and resolver grants, optional primary-name setup, and safe submission reconciliation. Expose start, get, resume, and local cancellation on the existing SDK.

    • 47095d1: Add fixed-policy HCA destination sessions and a Rhinestone execution adapter. Core exposes owner enablement, bounded refunds, enabled-status reads and confirmed session references. Session plans validate complete calldata and reconcile expiry, replacement and nonce revocation.

      The optional Rhinestone subpath requires SDK 1.8.0 with the shipped compatibility patch. It supports prefunded same-chain destination execution, SDK signing, on-chain signature verification and restorable public intent tracking. Hosted relayer settlement remains a release verification step.

    • c1e8c43: Add shared config workflow storage with memory and IndexedDB adapters, generated workflow IDs, automatic unfinished-operation recovery, transaction checkpoints, and workflow inspection and reconciliation. Preserve explicit resume and legacy HCA storage while allowing HCA registration and independent Rhinestone funding to use config storage.

    Patch Changes

    • Updated dependencies [0ced8e8]
    • Updated dependencies [e48eedc]
    • Updated dependencies [41bf652]
    • Updated dependencies [0943f56]
    • Updated dependencies [b9073ba]
    • Updated dependencies [8aa0bb6]
    • Updated dependencies [0a68e20]
    • Updated dependencies [9bef00b]
    • Updated dependencies [47095d1]
    • Updated dependencies [bdf2872]
    • Updated dependencies [c1e8c43]
    • Updated dependencies [f53985c]
      • @ensforge/core@0.4.0
  3. @ensforge/sdk@0.3.1

    Patch Changes

    • aed1b6d: Move package repository metadata and release provenance to the Namespace GitHub organization.
    • Updated dependencies [aed1b6d]
      • @ensforge/core@0.3.1
  4. @ensforge/sdk@0.3.0

    Minor Changes

    • 2f7b053: Expose all indexer actions through the grouped SDK and add Effect Atom query and Suspense hooks for the complete indexer surface.

    Patch Changes

    • 1f829bd: Support Wagmi 2.19 and 3.x, including RainbowKit applications, and point package homepages to ensforge.com.
    • Updated dependencies [ab3b407]
    • Updated dependencies [67227c2]
    • Updated dependencies [2448cb6]
    • Updated dependencies [722707f]
    • Updated dependencies [7f43949]
    • Updated dependencies [1f829bd]
      • @ensforge/core@0.3.0

August 2026

  1. @ensforge/sdk@0.2.0

    Minor Changes

    • a5f4353: Add group-scoped Core and SDK type entrypoints, slim the SDK and React root type surfaces, and resolve workspace packages through generated declarations to improve editor IntelliSense. Import action-specific SDK types from @ensforge/sdk/<group>.

      Wagmi integration now uses the optional @ensforge/core/wagmi and @ensforge/sdk/wagmi entrypoints, so viem-only consumers no longer install Wagmi. Sequential write plans retain submitted transaction hashes across confirmation failures and resume without resubmission.

    Patch Changes

    • Updated dependencies [94e55fe]
    • Updated dependencies [a5f4353]
      • @ensforge/core@0.2.0