Keys are currently fetched using the KeyGetters trait, which is subpar because a) it muddles concerns by making fetching keys be tied to a header, and b) it only fetches one key at a time. #7523 introduces a new registry with the capacity to read all keys at once, as well as a new leaner API that can be used to leverage this, but maintains the old API and keeps callsites intact to reduce disruption.
We should remove KeyGetters and change usage for get_current_public_keys or get_historical_public_keys were applicable (in most cases it'll be current, except odd scenarios such as the voting contract).
Keys are currently fetched using the
KeyGetterstrait, which is subpar because a) it muddles concerns by making fetching keys be tied to a header, and b) it only fetches one key at a time. #7523 introduces a new registry with the capacity to read all keys at once, as well as a new leaner API that can be used to leverage this, but maintains the old API and keeps callsites intact to reduce disruption.We should remove
KeyGettersand change usage forget_current_public_keysorget_historical_public_keyswere applicable (in most cases it'll be current, except odd scenarios such as the voting contract).