Stable Contract Addresses Allow Evolution of Authorization Logic

NewtonProtocol's Smart Contract Integration has given new insights into upgradeability in smart contracts. According to their documentation, it is possible for a contract address to remain stable while its authorization logic evolves.

The PolicyClient can be pointed to a newer policy using the setPolicyAddress() method, but this isn't just a simple pointer update. The policy's factory version is checked against the TaskManager's minimum compatible runtime version, and if it's incompatible, the update reverts instead of attaching unsupported policy logic.

The migration flow involves checking compatibility, redeploying incompatible policy data, deploying the policy via the latest factory, updating the existing PolicyClient, and verifying the migration. What stands out is that the PolicyClient address stays the same, meaning the execution-facing client can remain stable while the policy implementation evolves.