mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2024-12-22 11:32:09 +00:00
798bbbdc82
* coldstart flags for validator * WIP beacon node flags * wip beacon chain, flag fix in validator, arg fix in validator * checkpoint * Added interop service * working on mock chainstart * save the state lol * fix tests * Save genesis validators * gaz * fix validator help flags * WaitForChainStart actually waits for genesis time * cold start fixes * cache * change back * allow for genesis state too * remove logs * increase mmap size * dont process if head doesn't exist * add 10ms tolerance * enable libp2p debug at debug, fix pubsub * works with checkpt * initialize justified and finalized in db * Removed preloadStatePath from blockchain service * Clean up * Write to disk for now post state * revert b466dd536f8eadbdae2264a545a755370223d917 * Builds * Only RPC test fails now * use minimal config, no demo config * clean up branch * Lint * resolve lint * more lint fixes * lint * fix viz * Fixing RPC test * skip before epoch 2 * RPC time out * Fixed ordering * rename * remove some dbg statements * ensure index is correct * fix some panics * getting closer * fix tests * Fix private key * Fixed RPC test * Fixed beacon chain build for docker * Add interop.go to validator go_image * Fixed docker build * handle errors * skip test, skip disconnecting peers * Fixed docker build * tolerance for attestation processing * revert copy * clearer err message parse * fix launching from dep contract |
||
|---|---|---|
| .. | ||
| BUILD.bazel | ||
| main_test.go | ||
| main.go | ||
| 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