# IC System Canisters: ID Stability and API Backward Compatibility

**URL:** <https://forum.dfinity.org/t/ic-system-canisters-id-stability-and-api-backward-compatibility/41672>\
**Category:** Developers\
**Created:** [February 27, 2025, 8:59am UTC](https://forum.dfinity.org/t/ic-system-canisters-id-stability-and-api-backward-compatibility/41672 "2025-02-27T08:59:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![daniel-wong](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/daniel-wong/32/6248_2.png) [@daniel-wong](https://forum.dfinity.org/u/daniel-wong)\
**Post date:** [February 28, 2025, 4:06pm UTC](https://forum.dfinity.org/t/ic-system-canisters-id-stability-and-api-backward-compatibility/41672/3 "2025-02-28T16:06:51Z")

</div>

I concur.

In addition to avoiding breaking changes, when they seem unavoidable, we try as hard as possible to create a “nice” migration path for existing callers ([an example by yours truly](https://forum.dfinity.org/t/request-for-comments-api-changes-for-public-private-neurons/33360#how-to-migrate-2)). As Severin points out, particularly in the case of vulnerabilities, providing a nice migration path isn’t always feasible.

The Governance team within DFINITY is the main developer of CMC, Governance, and Root canisters. I would say @lara is a good person to tag for those.

For Ledger, consider contacting @mathiasb .

---

_[View the full topic](https://forum.dfinity.org/t/ic-system-canisters-id-stability-and-api-backward-compatibility/41672)._
