Browse all documentation
Manage names · 3 of 7

Bulk edit records and resolvers

Prepare record or resolver changes across selected names.

stableWeb app and unsigned plan helpersVerified 2026-07-29Owner: ENS.Tools Portfolio
Open this feature

Bulk Edit builds exact updates for multiple controlled names. Because names can use different resolvers, owners, managers, and wrapper paths, results and prerequisites remain visible per name.

Address, text, contenthash, and supported profile-record changes.
Resolver updates and compatibility checks.
Owner/manager role validation.
Per-name transaction construction and failure reporting.
No hidden broadcast or private-key handling.
Production contract

Before you run this workflow

Networks

  • Ethereum mainnet

Prerequisites

  • Connected controlling wallet
  • Correct owner, manager, registrant, or resolver authority

Wallet permissions

  • Only the transaction or typed-data signature shown for the selected operation

Expected result

  • A confirmed onchain update with per-name status for bulk operations

Errors and recovery

  • Inspect authority and wrapped-name state
  • Retry only failed items after refreshing chain state
Workflow

How to use it

  1. 1

    Select exact names

    Do not assume one wallet has the same role on every portfolio entry.

  2. 2

    Choose the change type

    Enter only public record values and validate addresses, URLs, content identifiers, and text.

  3. 3

    Review resolver prerequisites

    A record write may require setting or changing the resolver first. Keep dependency order intact.

  4. 4

    Simulate and sign

    Review each target and calldata plan; one failed name should not be mistaken for a successful batch.