--- title: "Upcoming Changes to Node Account IDs: What Developers Need to Know" id: "15545" type: "post" slug: "upcoming-changes-to-node-account-ids-what-developers-need-to-know" published_at: "2025-09-30T08:00:00+00:00" modified_at: "2026-02-03T18:04:58+00:00" url: "https://hedera.com/blog/upcoming-changes-to-node-account-ids-what-developers-need-to-know/" markdown_url: "https://hedera.com/blog/upcoming-changes-to-node-account-ids-what-developers-need-to-know.md" excerpt: "As part of the network evolution and the rollout of the Dynamic Address Book (DAB) on Hedera, upcoming releases of the consensus node software (v0.68 in December, 2025) will enable changes to node account IDs. This article provides an overview..." taxonomy_category: - "Uncategorized" taxonomy_post_tag: - "technical" --- [Skip to content](#content) blog # Upcoming Changes to Node Account IDs: What Developers Need to Know September 30, 2025 ![Keith Kowal](/wp-content/uploads/2025/12/1648503390497.jpeg) Keith Kowal Director of Product Management, Hashgraph ![Ed Marquez](https://hedera.com//wp-content/uploads/2025/12/Headshot.jpeg) Ed Marquez Head of Developer Relations As part of the network evolution and the rollout of the **Dynamic Address Book (DAB)** on Hedera, upcoming releases of the consensus node software (**v0.68 in December, 2025**) will enable changes to **node account IDs**. [HIP-1299](https://github.com/hiero-ledger/hiero-improvement-proposals/blob/HIP-update-node-account-id/HIP/hip-1299.md) marks an important milestone in strengthening network flexibility and governance, while also introducing some considerations for developers and integrators. #### **What Are Node Account IDs?** Each consensus node on the Hedera network is associated with an **account ID**. These IDs are used for: - **Reward and fees routing**: Rewards and transaction fees that apply to a node flow through its account ID. - **Transaction signing**: The account ID must be included in the transaction body when submitting to a given node. Because they are part of the signed transaction body, node account IDs are critical identifiers for the network’s function and integrity. #### **Node ID vs Node Account ID** It’s important to distinguish between a **Node ID** and a **Node Account ID**: - **Node ID**: A unique identifier for each consensus node in the network. Node IDs are stable and do not change over time. - **Node Account ID**: The account on the Hedera ledger that is associated with the node. This account can change over time and is the target for node rewards, penalties, and fees. **Example:** - Node ID: **1** (stable identifier, never reused for another node) - Node Account ID: **0.0.3** (current assignment, can change in the future) If, for example, the operator of Node 1 updates its account ID, the **Node ID remains “1”**, but the **Node Account ID might change to something new, such as 0.0.1235**. ⚠️ Applications must always rely on the latest account ID from the address book rather than assuming it is fixed. ⚠️ #### **What’s Changing?** With the DAB feature (introduced in[HIP-869](https://hips.hedera.com/hip/hip-869) ) and [HIP-1299](https://github.com/hiero-ledger/hiero-improvement-proposals/blob/HIP-update-node-account-id/HIP/hip-1299.md) , node properties such as **account IDs** can be updated on-chain. Beginning with the upcoming **v0.68 release in December**, node operators will be able to change their node’s account ID. Key points to note: - **Node account IDs are unique, but not fixed**: No two nodes can share the same account ID at the same time, but IDs can be reassigned over time. - **Account ID changes are immediate**: These changes take effect at consensus, are not scheduled, and are not tied to upgrades. Rewards reflect the new ID by 00:00 UTC, and any record-file path lag until the next upgrade is cosmetic only. - **Operator flexibility**: Node operators can change their node account IDs at their discretion, with changes coordinated through the address book. **Example:** - Before upgrade: Node ID 1 → Account ID 0.0.1234 - After upgrade: Node ID 1 → Account ID 0.0.32498 #### **Why It Matters?** Transactions must be signed with the correct node account ID. If an application submits a transaction to a node using an outdated account ID, the transaction will fail with an **INVALID_NODE_ACCOUNT** error. While newer versions of the Hiero SDKs automatically refresh the address book, **older SDKs may contain hardcoded node account IDs**. Applications using those older SDKs are at risk of disruption if the node account IDs they depend on change. A recent survey shows that some developers still manually configure the Hedera client to connect to a single node. **This manual approach is not recommended**. While many applications will not experience issues, those that hardcode node account IDs or use very old SDKs could be impacted. #### **Impact Scenarios** - **Applications using Hiero Java/JS/Rust/GO/Swift/C++ SDKs with dynamic node lists (****forMainnet****,****forTestnet****,****forPreviewnet****)** - By default, these automatically refresh the address book (by default, every 24 hours) - Minimal or no impact. - **Applications using****Client.forNetwork(oneOrMoreNodes)** - Does not dynamically update nodes in its list - Support to update dynamically will be added in the future - **Applications using Hiero Java/JS/Rust/GO/Swift/C++ SDKs with static node lists** - May fail to submit transactions to nodes whose account IDs have changed. - If configured to talk only to one node, the risk of disruption is higher. - **Applications using custom or community SDKs** - Behavior will depend on how node information is managed by each [community-managed SDK](https://docs.hedera.com/hedera/sdks-and-apis/sdks#consensus-node-code-sdks) . #### **Hiero SDK Versions That Refresh the Address Book** | SDK | Version (and above) | | --- | --- | | Java | v2.17.4 | | JavaScript | v2.18.2 | | Rust | v0.17.0 | | Go | v2.17.4 | | Swift | v0.20.0 | | C++ | v0.17.0 | #### **Recommendations for Developers** - **Do not treat node account IDs as permanent.** They can change. - **Upgrade to SDK versions** equal to or greater than the ones listed above to ensure automatic address book refresh. - **Avoid hardcoding node account IDs** in your applications. - **If you manage custom node lists**, refresh them regularly using the[Hedera Mirror Node API](https://mainnet.mirrornode.hedera.com/api/v1/docs/#/network/getNetworkNodes) . - **Test your applications** ahead of the v0.68 release to ensure compatibility. These changes will be available for testing in previewnet and testnet starting in early Q4, 2025. #### **Looking Ahead** The changes introduced in [HIP-1299](https://github.com/hiero-ledger/hiero-improvement-proposals/blob/HIP-update-node-account-id/HIP/hip-1299.md) are part of ongoing work to improve the flexibility, resilience, and network governance of Hedera. While **most applications are** **not expected to be impacted**, clear notice can help the developer community prepare and update where needed. All developers are encouraged to: - Upgrade to the latest SDKs. - Review your use of node account IDs. - Reach out to community contributors via[https://hedera.com/discord](https://hedera.com/discord) Discord if you have questions. #### **Call to Action** **If your application uses older client applications that may be affected please upgrade before the scheduled v0.68 release in December to avoid transaction submission issues.** [Back to Blog](/blog) discover See more articles [View All](/blog) ![Image](https://hedera.com/wp-content/uploads/2026/08/Regulation_Blog-1024x576.png) August 5, 2026 ### Details decide. What digital asset policy did in July 2026 Halfway through 2026, the regulatory picture is coming into focus. Hedera Chief Policy Officer Nilmini Rubin and VP Global Policy Isadora Arredondo break down what moved in June across the [Read More](https://hedera.com/blog/details-decide-what-digital-asset-policy-did-in-july-2026/) ![Deploy Multichain Dapps](https://hedera.com/wp-content/uploads/2026/07/HH600301_DeployMultichainDapps_Final-1024x576.png) July 17, 2026 ### Deploy Multichain Dapps on Hedera in 60 Seconds with scaffold-hbar Deploying multichain dapps on Hedera has never been easier! With just one command, you can spin up a fully functional dapp using Next.js, Hardhat or Foundry, and AI agent context… [Read More](https://hedera.com/blog/deploy-multichain-dapps-on-hedera-in-60-seconds-with-scaffold-hbar/) ![Regulation is finding its form](https://hedera.com/wp-content/uploads/2026/07/Regulation_Blog-1-1024x576.png) July 13, 2026 ### Regulation is finding its form in summer 2026 Halfway through 2026, the regulatory picture is coming into focus. Hedera Chief Policy Officer Nilmini Rubin and VP Global Policy Isadora Arredondo break down what moved in June across the [Read More](https://hedera.com/blog/regulation-is-finding-its-form-in-summer-2026/) ## Ready to get started? Discover why Hedera is the trusted institutional-grade network powering the new digital economy. [Start Building](/start-building) [Contact](/contact) We use cookies to deliver the best experience on our website and to analyze traffic. By continuing to use this site, you consent to our cookie policy. Review our [Privacy Policy](/privacy) to understand how Hedera collects and uses information. Accept All CookiesAccept Necessary Cookies