vc: initial documentation #3798
Conversation
bare-bones, but enough to get started
| The validator client is currently only available when built from source. To build the validator client, [build the beacon node](./build.md), then issue: | ||
|
|
||
| ```sh | ||
| make -j4 nimbus_validator_client |
There was a problem hiding this comment.
The documentation typically uses this rather than something like -j$(nproc). Presumably, this compromises between a reasonable guess at lowest-common-denominator number of cores and compatibility across Linux and macOS (which doesn't support, per se, nproc, though it has its own approaches to this), but it's not ideal.
There was a problem hiding this comment.
indeed - this lowest-common-denominator approach gives most of the benefit without the mess
There was a problem hiding this comment.
This is an issue of not-great defaults though, and while it's messy, it's messiness that should be handled by default by the build system: #3806
There was a problem hiding this comment.
But, out of scope of this PR, sure.
There was a problem hiding this comment.
Yes, apparently that's difficult to do, at a make level for whatever reason. I'm guessing nimble will learn this at some point
|
|
||
| ## Options | ||
|
|
||
| `nimbus_validator_client` supports command line options similar to the beacon node: |
There was a problem hiding this comment.
Probably better to be consistent here and either refer to beacon nodes generically as a non-specific noun (as is now) but in a way that's accurate and precise with regard to what beacon nodes in general do, or specifically nimbus_beacon_node, with which it's being compared.
bare-bones, but enough to get started