f62c58f8de
During snap-sync, we request ranges of values: either a range of accounts or a range of storage values. For any large trie, e.g. the main account trie or a large storage trie, we cannot fetch everything at once. Short version; we split it up and request in multiple stages. To do so, we use an origin field, to say "Give me all storage key/values where key > 0x20000000000000000". When the server fulfils this, the server provides the first key after origin, let's say 0x2e030000000000000 -- never providing the exact origin. However, the client-side needs to be able to verify that the 0x2e03.. indeed is the first one after 0x2000.., and therefore the attached proof concerns the origin, not the first key. So, short-short version: the left-hand side of the proof relates to the origin, and is free-standing from the first leaf. On the other hand, (pun intended), the right-hand side, there's no such 'gap' between "along what path does the proof walk" and the last provided leaf. The proof must prove the last element (unless there are no elements). Therefore, we can simplify the semantics for trie.VerifyRangeProof by removing an argument. This doesn't make much difference in practice, but makes it so that we can remove some tests. The reason I am raising this is that the upcoming stacktrie-based verifier does not support such fancy features as standalone right-hand borders. |
||
|---|---|---|
| .. | ||
| internal | ||
| README.md | ||
| crawl.go | ||
| discv4cmd.go | ||
| discv5cmd.go | ||
| dns_cloudflare.go | ||
| dns_route53.go | ||
| dns_route53_test.go | ||
| dnscmd.go | ||
| enrcmd.go | ||
| keycmd.go | ||
| main.go | ||
| nodeset.go | ||
| nodesetcmd.go | ||
| rlpxcmd.go | ||
| runtest.go | ||
README.md
The devp2p command
The devp2p command line tool is a utility for low-level peer-to-peer debugging and protocol development purposes. It can do many things.
ENR Decoding
Use devp2p enrdump <base64> to verify and display an Ethereum Node Record.
Node Key Management
The devp2p key ... command family deals with node key files.
Run devp2p key generate mynode.key to create a new node key in the mynode.key file.
Run devp2p key to-enode mynode.key -ip 127.0.0.1 -tcp 30303 to create an enode:// URL
corresponding to the given node key and address information.
Maintaining DNS Discovery Node Lists
The devp2p command can create and publish DNS discovery node lists.
Run devp2p dns sign <directory> to update the signature of a DNS discovery tree.
Run devp2p dns sync <enrtree-URL> to download a complete DNS discovery tree.
Run devp2p dns to-cloudflare <directory> to publish a tree to CloudFlare DNS.
Run devp2p dns to-route53 <directory> to publish a tree to Amazon Route53.
You can find more information about these commands in the DNS Discovery Setup Guide.
Node Set Utilities
There are several commands for working with JSON node set files. These files are generated by the discovery crawlers and DNS client commands. Node sets also used as the input of the DNS deployer commands.
Run devp2p nodeset info <nodes.json> to display statistics of a node set.
Run devp2p nodeset filter <nodes.json> <filter flags...> to write a new, filtered node
set to standard output. The following filters are supported:
-limit <N>limits the output set to N entries, taking the top N nodes by score-ip <CIDR>filters nodes by IP subnet-min-age <duration>filters nodes by 'first seen' time-eth-network <mainnet/goerli/sepolia/holesky>filters nodes by "eth" ENR entry-les-serverfilters nodes by LES server support-snapfilters nodes by snap protocol support
For example, given a node set in nodes.json, you could create a filtered set containing
up to 20 eth mainnet nodes which also support snap sync using this command:
devp2p nodeset filter nodes.json -eth-network mainnet -snap -limit 20
Discovery v4 Utilities
The devp2p discv4 ... command family deals with the Node Discovery v4
protocol.
Run devp2p discv4 ping <enode/ENR> to ping a node.
Run devp2p discv4 resolve <enode/ENR> to find the most recent node record of a node in
the DHT.
Run devp2p discv4 crawl <nodes.json path> to create or update a JSON node set.
Discovery v5 Utilities
The devp2p discv5 ... command family deals with the Node Discovery v5
protocol. This protocol is currently under active development.
Run devp2p discv5 ping <ENR> to ping a node.
Run devp2p discv5 resolve <ENR> to find the most recent node record of a node in
the discv5 DHT.
Run devp2p discv5 listen to run a Discovery v5 node.
Run devp2p discv5 crawl <nodes.json path> to create or update a JSON node set containing
discv5 nodes.
Discovery Test Suites
The devp2p command also contains interactive test suites for Discovery v4 and Discovery v5.
To run these tests against your implementation, you need to set up a networking environment where two separate UDP listening addresses are available on the same machine. The two listening addresses must also be routed such that they are able to reach the node you want to test.
For example, if you want to run the test on your local host, and the node under test is also on the local host, you need to assign two IP addresses (or a larger range) to your loopback interface. On macOS, this can be done by executing the following command:
sudo ifconfig lo0 add 127.0.0.2
You can now run either test suite as follows: Start the node under test first, ensuring
that it won't talk to the Internet (i.e. disable bootstrapping). An easy way to prevent
unintended connections to the global DHT is listening on 127.0.0.1.
Now get the ENR of your node and store it in the NODE environment variable.
Start the test by running devp2p discv5 test -listen1 127.0.0.1 -listen2 127.0.0.2 $NODE.
Eth Protocol Test Suite
The Eth Protocol test suite is a conformance test suite for the eth protocol.
To run the eth protocol test suite against your implementation, the node needs to be initialized as such:
- initialize the geth node with the
genesis.jsonfile contained in thetestdatadirectory - import the
halfchain.rlpfile in thetestdatadirectory - run geth with the following flags:
geth --datadir <datadir> --nodiscover --nat=none --networkid 19763 --verbosity 5
Then, run the following command, replacing <enode> with the enode of the geth node:
devp2p rlpx eth-test <enode> cmd/devp2p/internal/ethtest/testdata/chain.rlp cmd/devp2p/internal/ethtest/testdata/genesis.json
Repeat the above process (re-initialising the node) in order to run the Eth Protocol test suite again.
Eth66 Test Suite
The Eth66 test suite is also a conformance test suite for the eth 66 protocol version specifically.
To run the eth66 protocol test suite, initialize a geth node as described above and run the following command,
replacing <enode> with the enode of the geth node:
devp2p rlpx eth66-test <enode> cmd/devp2p/internal/ethtest/testdata/chain.rlp cmd/devp2p/internal/ethtest/testdata/genesis.json