57abb07e4e
I found this documentation a little confusing because it says "you must" leading me to think there may be some kind of dire consequences for NOT having it synced before starting the validator (in the context of importing existing keys from another setup, not starting a new validator with a new deposit). Modifying the language to make the consequences of not having the syncing done clear. |
||
|---|---|---|
| .. | ||
| nbc_audit_2020 | ||
| the_auditors_handbook | ||
| the_nimbus_book | ||
| README.md | ||
| amphora_catalyst_run.png | ||
| attestation_flow.dot | ||
| attestation_flow.md | ||
| attestation_flow.png | ||
| block_flow.dot | ||
| block_flow.md | ||
| block_flow.png | ||
| cpu_features.md | ||
| e2store.md | ||
| interop_merge.md | ||
| kintsugi_catalyst_logs.png | ||
| kintsugi_nethermind_logs.png | ||
| logging.md | ||
| neth-m2-nimbus.md | ||
| nimbus_localhost_run.png | ||
README.md
The books in this folder were produced using mdBook - see installation guide.
Some books also use mdbook-toc for tables of contents.
# Install or update tooling (make sure you add "~/.cargo/bin" to PATH):
cargo install mdbook mdbook-toc mdbook-open-on-gh
# Work on the book locally - open "http://localhost:4000" for live version
cd docs/the_nimbus_book
mdbook serve -p 4000
# Publish book using makefile (in the top-level dir)
make publish-book