Context
#1642 implemented the ExecutionRegistry, which serves a similar purpose as agave's StatusCache data structure in the context of replay (it does not store any of the extra data for being usable in RPC, which will have its own state tracking).
Initially that change set was made under the assumption that this commit in agave, included in v4.2.0, would be present in most validators on testnet (since it has been the recommended version to upgrade to on testnet for some time now). However that's not the case, so we had to pivot and inherit the key index from the snapshot.
Objective
This issue can be closed when we can remove all the code related to this, once the aforementioned commit in agave is present in most/all testnet validator nodes.
Context
#1642 implemented the
ExecutionRegistry, which serves a similar purpose as agave'sStatusCachedata structure in the context of replay (it does not store any of the extra data for being usable in RPC, which will have its own state tracking).Initially that change set was made under the assumption that this commit in agave, included in v4.2.0, would be present in most validators on testnet (since it has been the recommended version to upgrade to on testnet for some time now). However that's not the case, so we had to pivot and inherit the key index from the snapshot.
Objective
This issue can be closed when we can remove all the code related to this, once the aforementioned commit in agave is present in most/all testnet validator nodes.