-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Service Integration]: Obol integration #1162
Comments
Ansible playbooks by Obol: https://github.com/ObolNetwork/obol-ansible |
Originally posted by @OisinKyne in #1246 (comment) |
|
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 |
hoppala |
|
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. |
Obol Contract AddressesSOURCE: https://docs.obol.tech/docs/sc/introducing-obol-splits Factory ContractMainnet: 0x119acd7844cbdd5fc09b1c6a4408f490c8f7f522 |
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.
The text was updated successfully, but these errors were encountered: