Implement submit for changing BLS to execution

[pablomendezroyo]

Tools like Wagyu allow you to create a JSON file to be submitted to the beacon to implement the BLS to execution. Implement a "submit" to import this generated JSON file to the beacon in the Bran UI

[Pol-Lanski]

This is how I see the flow happening in dappnode:

Option 1: Submission happens in Dappnode

[Pol-Lanski]

Option 2: Don't create a submission tool and reuse beaconcha.in's tool:

In "Step 1" The button says "Instructions" 😅

Beaconcha.in submission page: https://beaconcha.in/tools/broadcast

[Pol-Lanski]

Option 1

Pros:

• User has full control, submits to their own beacon node

Cons:

• More development, potentially duplicating work

Option 2

Pros:

• Less work, less duplication, faster GTM

Cons:

• Dependant of an external service.

Since we don't want people to create the message in Dappnode because it's an online machine, this means that they will have to go out to use an external service for the message creation anyway (Wagyu FTW). Hence it seems reasonable that we also link them to the beaconcha.in service for submitting the message.

On our side, we cover them by warning them that their withdrawal address is NOT 0x01 automatically and immediately offering a resolution path. For me that's the important part and it doesn't matter so much whether they submit to their beacon node or they submit in Beaconcha.in.