A dashboard with stats and a --quiet mode would be nice

General
1

What it says on the tin. I run the binary and I have absolutely no idea what’s happening. It’s making connections over the network. Sometimes it will engage one thread of my CPU at 100%. Then it’ll be back to crickets again.

I understand that releasing a --quiet mode and a dashboard (if only a one-line thing) would take time. However, it would be really great if the devs could tell the users exactly what they need to look for to confirm that

  1. They’re connected to peers / the backbone
  2. They are mining something
  3. They have mined something
2

Search your output/logs for “mining”. If you see “mining-on” followed by numbers and no errors on the next line, you’re probably mining. There should also be mining threads using full CPU cores. And your ram will likely be quite full at that point.

Here’s an example where the node tries to start work on a new block:
[%mining-on 14.013.155.469.355.287.694 17.658.163.466.538.601.719 16.139.960.547.538.818.049 13.146.085.519.865.444.801 3.604.770.390.141.248.621]

Find a way to write your logs to a file for easier searching.

1 Like
3

Where would the logs happen to be? (are they already recorded somewhere?)

4

I don’t see any of that, sorry. I had no issues during compilation, so I think it must be my network. What do I need to enable / disable to allow peer discovery (in case that isn’t happening)?

5

Logs are just the process stdout and stderr afaik. You could try using tee to still see it displayed live while also writing to a file.

Keep in mind that nockchain is very experimental software. It’s the first app running on a new tech stack. I don’t think anyone outside of Zorp and their partners were able to run the stack until code was released on github weeks ago. There are many things that can go wrong even if the code compiled on your machine.

1 Like
6

for quieter logging modes, check our update here: GitHub - zorp-corp/nockchain: Nockchain protocol monorepo

To reduce logging verbosity, you can set the RUST_LOG environment variable before running nockchain:

Show only info and above

RUST_LOG=info nockchain

Show only errors

RUST_LOG=error nockchain

Show specific module logs (e.g. only p2p events)

RUST_LOG=nockchain_libp2p_io=info nockchain

Multiple modules with different levels

RUST_LOG=nockchain_libp2p_io=info,nockchain=warn nockchain

1 Like