e1830519a4
Whether new blocks/attestations/etc are produced internally or received via REST, their journey through the node is the same - to ensure that they get the same treatment (logging, metrics, processing), this PR moves the routing to a dedicated module and fixes several small differences that existed before. * `xxxValidator` -> `processMessageName` - the processor also was adding messages to pools, so we want the name to reflect that action * add missing "sent" metrics for some messages * document ignore policy better - already-seen messages are not actaully rebroadcast by libp2p * skip redundant signature checks for internal validators consistently |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| README.md | ||
| deposit_downloader.nim | ||
| download_mainnet_deposits.sh | ||
| e2store.nim | ||
| e2store.py | ||
| logtrace.nim | ||
| ncli.nim | ||
| ncli_common.nim | ||
| ncli_db.nim | ||
| ncli_query.nim | ||
| ncli_split_keystore.nim | ||
| nim.cfg | ||
| nimquery.nim | ||
| requirements.txt | ||
| resttest-rules.json | ||
| resttest.nim | ||
| validator_db_aggregator.nim | ||
| validator_db_reports.ipynb | ||
README.md
Introduction
ncli is a set of low level / debugging tools to interact with the nimbus beacon chain specification implementation, simliar to zcli. With it, you explore SSZ, make state transitions and compute hash tree roots.
Tools
- transition: Perform state transition given a pre-state and a block to apply (both in SSZ format)
- hash_tree_root: Print tree root of an SSZ object
- pretty: Pretty-print SSZ object as JSON
Building
Follow the instructions from nimbus-eth2
git clone https://github.com/status-im/nimbus-eth2.git
cd nimbus-eth2
make
Usage
# Build with minimal config
../env.sh nim c -d:const_preset=minimal ncli_transition
# Build with mainnet config
../env.sh nim c -d:const_preset=mainnet ncli_transition
# Run..
./ncli_transition --help