DFINITY proposes update to canister interface for long-term stability

DFINITY has outlined a proposal to adjust how some data structures are defined in the Internet Computer’s management canister interface. The aim is to make the system more adaptable to future needs without creating compatibility issues for existing canisters.

At present, certain records use variant types that are closed, meaning their branches cannot be safely renamed or expanded once they have been set. When new branches are added, older canisters attempting to decode them will fail, creating potential breakages. This issue affects structures such as change_details, source and globals in snapshot metadata responses.

To address this, DFINITY is proposing that fields which rely on variants should instead become optional. Under the updated model, records like change and read_canister_snapshot_metadata_response would allow for optional details, source and globals fields. The shift would mean that new branches could be introduced over time without disrupting canisters that rely on earlier versions of the schema.

DFINITY argues that this approach is vital because management canister records are long-lived and form part of the Internet Computer’s core state. As new features are developed, such as extended snapshot metadata or additional operations, the system needs a way to evolve without forcing changes that could destabilise existing deployments.

By making these elements optional, developers gain flexibility to extend functionality in a controlled way, ensuring forward compatibility while preserving stability for users already running on the network.