To manage network upgrades, SKALED utilizes a "patch" system where features are toggled via configuration timestamps. Conversely, precompiled contracts are currently static; they lack patch integration and are active from genesis. This creates a functional gap: patches that introduce new precompiled contracts require redundant, separate timestamp handling logic.
We need to implement an activation layer for precompiled contracts that is coherent with the existing patch system. By bridging these two, precompiled contracts can be registered to a specific patch timestamp, ensuring unified and predictable behavior across the network.
To manage network upgrades, SKALED utilizes a "patch" system where features are toggled via configuration timestamps. Conversely, precompiled contracts are currently static; they lack patch integration and are active from genesis. This creates a functional gap: patches that introduce new precompiled contracts require redundant, separate timestamp handling logic.
We need to implement an activation layer for precompiled contracts that is coherent with the existing patch system. By bridging these two, precompiled contracts can be registered to a specific patch timestamp, ensuring unified and predictable behavior across the network.