The same problem as https://github.com/RegionX-Labs/CoretimeHub/issues/252, but now the 2503 release is rolling out on production networks. Several storage entries are now clocked by the relay chain block number instead of local block number. Today I can see the following in Kusama Corehub: <img width="467" alt="Image" src="https://github.com/user-attachments/assets/b278684a-621d-4f0d-8e2f-55d1c0fd6b0e" />
The same problem as #252, but now the 2503 release is rolling out on production networks.
Several storage entries are now clocked by the relay chain block number instead of local block number.
Today I can see the following in Kusama Corehub: