[Service Integration]: Obol integration

[stefa2k]

Is your feature request related to a problem? Please describe. Right now there is no UI guided way to setup an Obol cluster.

Describe the solution you'd like Integration of Obol in Stereum.

• [x] Having Obol as an option in the OneClickInstaller
• [x] Having Obol as an option in the custom installer
• [ ] Create a cluster with Stereum and the Obol API
• [x] Obol Grafana dashboard inlcuded in Stereum
• [ ] Obol Grafana alerts included in Stereum Notifications (also Stereum Mobile App)
• [ ] #1983

[stefa2k]

Ansible playbooks by Obol: https://github.com/ObolNetwork/obol-ansible

[stefa2k]

          Hey guys, loving that you guys are integrating Obol ❤️  One small heads up, the Icons you guys have outlined, are our older versions (note the shape of the loop is much more asymetrical/fish like), you can get copies of our latest icon [here](https://blog.obol.tech/branding). Let me know if you need any other resolutions/formats. :D

Originally posted by @OisinKyne in https://github.com/stereum-dev/ethereum-node/issues/1246#issuecomment-1568972122

[daGscheid]

          Hey guys, loving that you guys are integrating Obol ❤️  One small heads up, the Icons you guys have outlined, are our older versions (note the shape of the loop is much more asymetrical/fish like), you can get copies of our latest icon [here](https://blog.obol.tech/branding). Let me know if you need any other resolutions/formats. :D

Originally posted by @OisinKyne in #1246 (comment)

New Icons used

[daGscheid]

That was a little preemptively closed haha. I am going to check the boxes you have so far @NeoPlays & fill the issue with the current path I have planned for the UI

[NeoPlays]

hoppala

[daGscheid]

• [x] Add a path to make a keystore backup in the Obol UI

[daGscheid]

Current planned UI:

On first open of Obols Modal with no ENR present the user is prompted to either import an existing or generate a new one

Path 1 Generate a new ENR

Clicking the option to create a new ENR shows a log box...

...which either leads to a failed generation of an ENR, returning the user to the first access screen, ...

...or an successful generation of an ENR, in which the user is prompted to back the ENR up & the ENR is copied / saved in a text file (?)

& after which the user can press continue to the next modal

This modal is shown in the case that the user has an ENR present in his OBOL client bu there is still no keystore shared with OBOL - the user is then prompted to start the DKG (Distributed Key Generation)

When the user clicks the button they are next prompted to run the command.

The user has to past the command from the OBOL Launchpad into this field and click the "RUN" button with the other participant around the same time leading them to a modal running the logs

...until the process is either sucessful, which gets the user to continue to the management modal or fails returning the user. On sucess I would like to create a small animation.

#

Having both ENR & the keystore files means the OBOL generation process is complete - which the modal showing the option to back up the keystore files (pathpicker). We could discuss if should include this as an non optional step one step before.

[daGscheid]

Obol Contract Addresses

SOURCE: https://docs.obol.tech/docs/sc/introducing-obol-splits

Factory Contract

Mainnet: 0x119acd7844cbdd5fc09b1c6a4408f490c8f7f522 Goerli Testnet 0xe9557FCC055c89515AE9F3A4B1238575Fcd80c26