EC needs to be able to add and remove node operators from oracle network

[turadg]

@otoole-brendan commented on Mon Dec 19 2022

What is the Problem Being Solved?

The EC needs to be able to add and remove oracle node operators by proposing and voting on said action for vaults release as a short-medium term measure until we pivot to self-governing oracle network.

The EC should be able to make changes to oracle node network setup by removing any node operator (for whatever reason, but typically this is for risk purposes and to take emergency action to preserve price integrity. Similarly, the EC may choose to replace this bad actor or increase the number of node operators (greater than starting 5) to hedge against fewer points of failure.

The EC should be able to select any node operator (possible from a drop-down) and then propose to remove. Similarly, the EC needs to be able to add a new operator (not sure how best to visualize this in UI as it requires input of a node operator with related underlying information which would not be known until future date - open to suggestions)

Description of the Design

Contract changes

Preview Give feedback

1. EC can propose and vote on changes to oracle operators list agoric-sdk#6701
   enhancement vaults_triage +2
   

Security Considerations

Unknown

Test Plan

[dckc]

see also mock ui sketched with @otoole-brendan yesterday

[dckc]

Similarly, the EC needs to be able to add a new operator (not sure how best to visualize this in UI as it requires input of a node operator with related underlying information which would not be known until future date - open to suggestions

An address to send the operator an invitation seems necessary and sufficient. Perhaps a diagnostic label. I expect details of doing it from a cli will be part of Agoric/agoric-sdk#6701 , at which point things should be pretty clear.

Security consideration: blind-typing addresses is risky

Consider using an identicon to help the user be sure they entered the right address.