Based on the communications and actions initiated by the relevant node operators, specifically:
- The merger between Blockdaemon and Anyblock Analytics, consolidation of operations and treating the two operators as one, and then the subsequent winddown of the Anyblock Analytics infrastructure via prioritization in the exits process, and
- Jump Crypto’s request to exit the validator set and the subsequent winddown of their infra via the prioritization in the exits process
and given that both Node Operators are at zero unconfirmed (i.e. newly submitted) keys, and there is no intent to submit new keys by the relevant organizations
I propose that the DAO proceed to mark these entries in the Curated Node Operator Registry (operator ids 1 and 12) as “inactive”. This makes it easier/clearer to people ingesting protocol data that the operator entries are no longer in use and adds an additional safeguard in the case that somehow keys may be submitted in the future without following proper process.
This action would be accomplished by utilizing the deactivateNodeOperator(_id) method for both ids.