David

It needs some adjustments based on configurations of Wallet Connect. Redo is in the work

Would especially like to look at this again with a (Gnosis) SAFE implementation in the background in mind https://docs.safe.global/getting-started/readme

SOURCE: https://docs.ssv.network/developers/smart-contracts Contract | Address -- | -- SSV Token | 0x9D65fF81a3c488d585bBfb0Bfe3c7707c7917f54 SSVNetwork | 0xDD9BC35aE942eF0cFa76930954a156B3fF30a4E1 SSVNetworkViews | 0xafE830B6Ee262ba11cce5F32fDCd760FFE6a66e4 SSV DAO Treasury | 0xb35096b074fdb9bBac63E3AdaE0Bbde512B2E6b6 SSV DAO Vesting | 0xB8471180C79A0a69C7790A1CCf62e91b3c3559Bf Testnet v1...

Was fixed at some point by @NeoPlays

For Besu, I would reuse the component we also used in #719. Important however is that we difference them somehow because of their different functionality. This would look something like...

Lets just start off by going through the complete validator registration flow: ### STEP 1# Connect your Wallet (Login)  ...

Please don't forget to add screenshots to the translation to simplify the process and give context to the translators. This can be done by entering CONTENT > SCREENSHOTS and uploading...

Guiding the whole potential process. https://help.joinstakehouse.com/en/articles/6206942-how-do-i-stake-a-validator-using-the-ethereum-cli Also a reference on how we can differentiate "Stakehouse" Validator Keys with "Solo Staking" Keys.

Done with #1041 & #1045

After some discussion, we decided that supporting this would currently be too much work. So we will go for the first option, notifying that this key format is not supported...