> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://ensforge.com/api/mcp` to find what you need.

# Upgrade to 0.6

Version 0.6.0 requires **Effect 4 stable** and updates Sepolia ENSv2 to the October 1, 2026 deployment.
Mainnet deployment configuration is unchanged. If you are upgrading from before 0.5, first review
the [0.5 API changes](/migrations/0-5).

## Effect 4 stable

Follow the [package upgrade commands](/migrations/overview#upgrade-packages-together), including
`effect@^4`. Replace any direct Effect RC dependencies in your application. If you use
`@effect/atom-react`, `@effect/platform-node`, or `@effect/vitest` directly, update those to their
compatible stable releases too. Stable `@effect/vitest` 4.0.0 requires Vitest 5.

### Removed `effect/unstable` import paths

Update direct imports that include the removed `unstable` segment:

```ts
import { FetchHttpClient } from "effect/unstable/http"; // [!code --]
import { FetchHttpClient } from "effect/http"; // [!code ++]
import { Atom, AsyncResult } from "effect/unstable/reactivity"; // [!code --]
import { Atom, AsyncResult } from "effect/reactivity"; // [!code ++]
```

The new paths do not make every module's API stable: Effect still marks some modules as unstable.
If your application uses Effect APIs directly, review its
[4.0.0 changelog](https://github.com/Effect-TS/effect/blob/effect%404.0.0/packages/effect/CHANGELOG.md),
particularly Schema branding and the successes-first ordering of partition helpers.

## Replaced Sepolia deployment

The built-in Sepolia profile now uses contracts from
[`07e55a05`](https://github.com/ensdomains/contracts-v2/tree/07e55a056f5b6a9c90119f501bdd05714e67dddd/contracts/deployments/sepolia).
Recreate your config after upgrading. If you supply custom deployment addresses, update the complete
profile and use its matching ABIs; changing the npm version does not overwrite a custom profile.

Registries, the registrar, resolvers, HCA factory, implementations, and mock payment tokens changed.
The Universal Resolver proxy addresses stayed the same, but now resolve through the replacement
deployment. Recreate test names and resolver permissions on that deployment before using them.

For repository playgrounds and verification commands, follow
[Sepolia deployment setup](/core/guides/sepolia-deployment).

## HCA accounts and payment tokens

Predict and deploy an account using the new factory. Do not hard-code an HCA address from 0.5 or
expect a saved session proof to authorize the replacement account. Grant resolver permissions to
the new HCA and create fresh session authorizations if you use Rhinestone.

Check the current registrar's payment token before funding the account. Balances of an old mock
token cannot pay the new registrar. Likewise, review cross-chain route token addresses against the
destination configuration before signing a funding operation.

The HCA account and session-validator interfaces are unchanged from 0.5. The factory now supports
idempotent deployment: a certified existing account can be reused even if its initial implementation
is no longer approved for new deployments. A deployment result can therefore report account reuse;
do not assume each successful call creates a new account or sends a transaction.

## Keep workflows with their deployment

Do not resume a 0.5 registration or funding record with the new config. Reconcile any submitted work
on its original deployment first, retain that state for recovery, then create a new workflow on
the replacement deployment. Keep session private keys outside workflow storage.

## Verify your upgrade

Run your typecheck and build, then verify a read against your own Sepolia fixture. For HCA apps,
verify the new account, perform a record update with your chosen provider, and check its receipt
and resulting record value. If you use registration or cross-chain funding, verify those flows
separately with the new payment token.

Continue with [Pimlico](/hca/pimlico/getting-started),
[Rhinestone sessions](/hca/rhinestone/sessions), or
[cross-chain funding](/hca/rhinestone/cross-chain).