mirror of
https://github.com/darkrenaissance/darkfi.git
synced 2026-04-28 03:00:18 -04:00
55ee919906
Notable changes: * Rewritten transport protocols into Dialer and Listener (Nym is TODO) This simplifies using the transports a lot, as can be seen for example in src/rpc, and generally around the p2p library. It also defines features for each transport (all of which are enabled by default). We drop the socks client for Tor and Nym and use first-class support with the Arti Tor library, and nym-sphinx/nym-websockets (to be used with nym-client). * Outbound session healing The outbound session will now poll and try to fill all the requested slots more efficiently, and if needed, will activate peer discovery to find more peers if we can't connect to any known ones. Also if we're unable to connect to any, we shall drop them from our set. Additionally, transport mixing is enabled by default, so when we're allowing transport mixing, and we use Tor, we will also be able to connect to other transports that Tor can connect to (e.g. tcp://). * Unix socket transport dropped We haven't been using this, and it seems we're not going down this path, so the code has been obsoleted and removed. * TLS session verification We fully verify server and client TLS certificates upon connection so we're able to perform TLS1.3 with forward secrecy. * lilith pruning lilith now periodically prunes known peers from its sets if it's unable to connect to them.
Dnetview
A simple tui to explore darkfi p2p network topology. Explore:
- Active p2p nodes
- Outgoing, incoming and manual sessions
- Each associated connection and recent messages.
Dnetview is based on the design-pattern Model, View, Controller. We create a logical seperation between the underlying data structure or Model; the ui rendering aspect which is the View; and the Controller or game engine that makes everything run.
Install
% git clone https://github.com/darkrenaissance/darkfi
% cd darkfi
% make BINS=dnetview
Usage
On first run, dnetview will create a config file in .config/darkfi. You must manually enter the RPC ports of the nodes you want to connect to and title them as you see fit.
Check the example config file for more details.
Run dnetview as follows:
dnetview -v
Navigate up and down using j and k.
Logging
Dnetview creates a logging file in /tmp/dnetview.log. To see json data and other debug info, tail the file like so:
tail -f /tmp/dnetview.log
Or use multitail for colored output:
multitail -c /tmp/dnetview.log