Web3Signer setup guide
Last updated
Last updated
Web3Signer is an open-source signing service developed under the and written in Java. Web3Signer is capable of signing on multiple platforms using stored in an external vault, or encrypted on a disk.
It is an innovative tool designed to enhance security and simplify the process of signing transactions in web3 applications. With Web3Signer, developers can seamlessly integrate external wallets or vaults into their decentralized applications, ensuring robust protection for private keys and providing users with a seamless and secure transaction signing experience.
This tool streamlines the signing process and offers enhanced security measures, making it a valuable asset for developers and users in the Web3 ecosystem.
Web3Signer offers two setup options: Docker mode or running it natively with a binary.
For Docker mode, refer to the following documentation:
To set it up in native mode, follow the instructions provided in this documentation:
The signing mode of your Web3signer should be consensus layer client mode. To enable this signing mode simply add "eth2" after the web3signer command. For example: web3signer <commands> eth2 <sub commands>
To explore the available commands that can be used with web3signer in eth2 mode, you can run web3signer eth2 --help. This will provide you with a list of possible commands and their usage.
When integrating Web3Signer with your validator client, it is highly recommended to set up slashing protection. Slashing protection ensures that validators do not sign duplicate attestations or blocks, preventing potential double signing issues.
To restrict access to the web3signer instance you have set up, you can create a whitelist of permitted hosts. This ensures that only specified hosts can make use of the web3signer's REST API.
After setting up your web3signer, it is highly advisable to establish a connection between web3signer and your running validator client. This connection is crucial to prevent duplicate keys. Typically, you would have one key imported with the validator client and a duplicate copy stored on platforms like AWS KMS or Hashicorp Vault. This is an inconvenient situation which can potentially cause double slashing.
To seamlessly connect web3signer with your validator clients, please refer to the provided documentation for detailed instructions and guidelines. Following these instructions will ensure a smooth and secure integration between web3signer and your validator clients.
To enable slashing protection with Web3Signer, the node operator needs to maintain a database that can be shared among multiple instances of Web3Signer. This enables efficient slashing protection across the network.
For a detailed understanding of slashing protection, please refer to the following documentation:
Find the relevant commands for setting up slashing protection in the following documentation:
To determine the storage location for your keys in Web3Signer, you need to create a configuration file that specifies the desired storage location. This configuration file can then be passed to Web3Signer using the following flag:
For detailed instructions on how to curate the configuration file and to learn about the supported platforms for Web3Signer, please refer to this documentation:
To set up the host whitelist, you can utilize the allowlist command. This command enables you to specify the hosts that are allowed to access the REST API. For more detailed information on using this command, please refer to the following documentation:
For lighthouse -
For Nimbus -
For Prysm -
For Teku -
For a comprehensive tutorial on setting up web3signer and establishing a connection with your validator client, we recommend following this resource: