https://github.com/dappnode/dappnodepackage-web3signer-generic
Dappnode package template for managing keystores
https://github.com/dappnode/dappnodepackage-web3signer-generic
Last synced: about 2 months ago
JSON representation
Dappnode package template for managing keystores
- Host: GitHub
- URL: https://github.com/dappnode/dappnodepackage-web3signer-generic
- Owner: dappnode
- License: apache-2.0
- Created: 2024-07-09T07:19:14.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2026-04-04T16:17:00.000Z (2 months ago)
- Last Synced: 2026-04-04T19:18:48.029Z (2 months ago)
- Language: Shell
- Size: 154 KB
- Stars: 0
- Watchers: 4
- Forks: 3
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Dappnode Package _Web3Signer_
This repo includes the Web3Signer packages for: Hoodi, Mainnet, LUKSO and Gnosis
A validator client contributes to the consensus of the Ethereum Blockchain by signing proposals and attestations of blocks, using a BLS private key which must be available to this client at all times.
The BLS remote signer API is designed to be consumed by validator clients, looking for a more secure avenue to store their BLS12-381 private key(s), enabling them to run in more permissive and scalable environments.
More information about the EIP can be found at [the official website](https://eips.ethereum.org/EIPS/eip-3030)
### Why _Web3signer_ ?
Client diversity is a key benefit of DAppNode, with our implementation of ConsenSys's remote Web3Signer you will be able to use different clients and don't need to put all your trust in just one validator client. The remote signer can work as a load balancer, keeping your validators always validating.
### Requirements
Rquirements to run the Web3Signer package
- **Validator**: Set up your validator at https://launchpad.ethereum.org/
- **Ethereum Node**: Set up your Ethereum full node by selecting a pair of clients (execution + consensus layers) in the Stakers menu of your Dappnode