mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-22 19:40:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
82bbfce524
prysm-pulse/tools/unencrypted-keys-gen
History
Raul Jordan d077483577
Add V3 Suffix to All Prysm Packages (#11083) 
* v3 import renamings

* tidy

* fmt

* rev

* Update beacon-chain/core/epoch/precompute/reward_penalty_test.go

* Update beacon-chain/core/helpers/validators_test.go

* Update beacon-chain/db/alias.go

* Update beacon-chain/db/alias.go

* Update beacon-chain/db/alias.go

* Update beacon-chain/db/iface/BUILD.bazel

* Update beacon-chain/db/kv/kv.go

* Update beacon-chain/db/kv/state.go

* Update beacon-chain/rpc/prysm/v1alpha1/validator/attester_test.go

* Update beacon-chain/rpc/prysm/v1alpha1/validator/attester_test.go

* Update beacon-chain/sync/initial-sync/service.go

* fix deps

* fix bad replacements

* fix bad replacements

* change back

* gohashtree version

* fix deps

Co-authored-by: Nishant Das <nishdas93@gmail.com>
Co-authored-by: Potuz <potuz@prysmaticlabs.com>
2022-08-16 12:20:13 +00:00
..
keygen Add V3 Suffix to All Prysm Packages (#11083) 2022-08-16 12:20:13 +00:00
BUILD.bazel Add V3 Suffix to All Prysm Packages (#11083) 2022-08-16 12:20:13 +00:00
main_test.go Add V3 Suffix to All Prysm Packages (#11083) 2022-08-16 12:20:13 +00:00
main.go Add V3 Suffix to All Prysm Packages (#11083) 2022-08-16 12:20:13 +00:00
README.md dont lose keys (#3357) 2019-08-30 10:02:08 +05:30

README.md

Unencrypted Keys Generator

This tool is used to generate JSON file of unencrypted, base64 encoded, validator signing and withdrawal keys. These keys can be fed into the Prysm validator client for fast development startup times instead of using the Prysm keystore.

Usage:

bazel run //tools/unencrypted-keys-gen -- --num-keys 64 --output-json /path/to/output.json

Which will create 64 BLS private keys each for validator signing and withdrawals. These will then be output to an output.json file. Both arguments are required. The file can then be used to start the Prysm validator with the command:

bazel run //validator -- --unencrypted-keys /path/to/output.json