This refactoring puts the JSON-RPC and REST APIs on more equal footing by renaming and moving things around, creating a separation between client and server, and documenting what they are - the aim is to have a simple-to-use base to start from when developing API clients, as well as make it easier to navigate the code when looking for the legacy JSON-RPC interface vs the new REST API. * move REST client, serialization and supporting types to spec/eth2_apis * REST stuff now starts with `rest_`, JSON-RPC stuff starts with `rpc_`, more or less * simplify imports such that there's a simple module to import for both server and client * map REST type and proc names to yaml spec more closely - in particular, reuse operation and type names in `rest_types` to make comparisons against spec more easy * cleaner separation between client and server modules - modules common between server and client such as `rest_types` and serialization move to the spec folder - this allows the client to be built with less knowledge about server internals |
||
---|---|---|
.. | ||
nbc_audit_2020 | ||
the_auditors_handbook | ||
the_nimbus_book | ||
README.md | ||
attestation_flow.dot | ||
attestation_flow.md | ||
attestation_flow.png | ||
block_flow.dot | ||
block_flow.md | ||
block_flow.png | ||
cpu_features.md | ||
e2store.md | ||
logging.md | ||
rayonism_catalyst_logs.png | ||
rayonism_merge.md | ||
rayonism_metamask_network_setup.png | ||
rayonism_metamask_send_eth.png | ||
rayonism_metamask_transaction_confirmation.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