ICRC Rosetta users have been advised to upgrade urgently following the release of version 1.2.9, which introduces critical compatibility for upcoming changes across ICRC ledgers.
The update adds support for ICRC-107 fee collector blocks, a new block type that will begin appearing once ICRC ledgers adopt the ICRC-107 standard. These blocks are designed to handle fee collection in a structured way, and their arrival marks an important technical evolution for how ledger activity is recorded.
The issue is that older versions of ICRC Rosetta, particularly anything before v1.2.9, are not able to correctly parse these new blocks. That means systems running outdated software may encounter failures as soon as ledgers begin producing fee collector blocks.
Developers behind the release warn of several possible risks for users who do not upgrade. Rosetta nodes may stop syncing entirely, which could interrupt services that rely on continuous ledger data. Operation mapping may become invalid, creating inconsistencies in how transactions are interpreted. More broadly, general parsing failures could affect the reliability of downstream applications.
For infrastructure providers, the implications are practical. Exchanges and custody platforms depend on accurate ledger ingestion to monitor deposits, withdrawals, and balances. Block explorers require full compatibility with new block types to display transaction histories correctly. Any organisation using ICRC Rosetta as part of their backend ledger integration could face disruptions if upgrades are delayed.
The release highlights how even small protocol-level adjustments can have wide-reaching effects across the ecosystem, especially for services operating at scale.
Maintainers also clarified that the update applies specifically to ICRC Rosetta. ICP Rosetta is not impacted by the introduction of ICRC-107 fee collector blocks, so ICP-focused deployments do not face the same requirement.
For teams running Rosetta in production, the guidance is clear: upgrading to ICRC Rosetta v1.2.9 is strongly recommended to ensure uninterrupted syncing and accurate transaction parsing as ICRC standards continue to develop.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion