ethereum
Minimal SSV API
Suggested API for VC to communicated with SSV node (SSV node will emulate BN API to VC, to keep things simple)
Here is an illustration on how the SSV node is supposed to work. It basically sits between the SSV node and the BN, and will emulate the BN API for the VC (this is to avoid duplication of work to build another API which would be very similar overall)
Don't know why the CI is failing, seems to be an error with the CI
There was invalid file references in stream. Funny enough, linter seems to missed it, but bundler caught it
@dankrad is the VC still connected to the BN? it would seem to me that it should as there are several calls that go along with signing.
Prysm's VC (for example) has a runner loop that asks for duties from BN, if any found it also asks to subscribe to the relevant topic, get data to sign and of course broadcast the sig. If the VC node is only connected to the SSV node then it needs to cover those calls as well and the VC code will need to change as not all nodes that take part in the SSV will need to subscribe to the relevant topic or request the signing data.
@dankrad is the VC still connected to the BN? it would seem to me that it should as there are several calls that go along with signing.
The idea is that the VC is now only connected to the SSV client. The SSV client could proxy any BN endpoints the VC needs, but I'm not sure if that would be necessary.
Prysm's VC (for example) has a runner loop that asks for duties from BN, if any found it also asks to subscribe to the relevant topic, get data to sign and of course broadcast the sig.
We will need to leave all this to the SSV node, the VC would become much more passive in this setting. The VCs core responsibility is key management and slashing protection.
