# Web3Signer w/ keymanager UI project To increase client diversity among non-technical stakers it's key that all implementations can expose a UI to perform keymanager actions. For context on other explored options please check [Road to eth2 multiclients in DAppNode ⧫ #329](https://github.com/dappnode/DAppNode/issues/329) Attaching a UI to a separate component (a remote signer) is the frictionless route for the current consensus client teams; since now they only need to implement [EIP 3030](https://eips.ethereum.org/EIPS/eip-3030) and get access to a keymanager UI at no extra development cost. [Consensys web3signer](https://github.com/ConsenSys/web3signer/) is currently the only productionized, battle tested remote signer. Please reach out to [@dapplion](https://twitter.com/dapplion) if you know of any other implementation with similar security guarantees. ## Project summary - Extend [Consensys web3signer](https://github.com/ConsenSys/web3signer/) to implement a minimal keymanager API as described in this proposed standard https://github.com/ethereum/beacon-APIs/pull/151 - Implement a UI that interacts with a backend following https://github.com/ethereum/beacon-APIs/pull/151 - Participate in the stakers community long term to add requested features and expand the project as needed I [@dapplion](https://twitter.com/dapplion) can offer mentorship and direction throughout the project.