[P0] Make handling of warm keys deterministic (research) #913
Priority: High devshards
At the moment, devshards handle hosts' warm keys in a non deterministic way.
Different hosts can check whether a warm key is authorized at different points in time, using the mainnet bridge, and therefore get different results.
One example could be a host H shutting down for 20 mins, and then becoming available again. They'll need to process diffs from 20 mins ago. If some other host has rotated their warm key in the meantime, H will not deem the warm key used to sign the original diff as authorized (even though it was at the time it was signed)
We need to think of a solution to make this deterministic, and implement it.
💬 Comments (1)
🔄 Auto-synced from Issue #913 every hour.
Will be finished by March 27th.