PoC-Consortium/scavenger

What to put in URL? (Solo mine)

Closed this issue · 9 comments

New to burst and saw scavenger as a recommended tool.

I'm using a Raspberry Pi 4, installed the 1.7.8 arm version and stumped on the configuration.

Documentation says account id and pass phrase are required. I did that. Then I added in the paths to plots. So far so good.

When I got to the URL, no documentation says where to get it. For pool, you get it in their site. But what about solo?

The one on the wiki is http://wallet.dev.burst-test.net:6876 which I don't think is the right one given that metadata says it's a test url. Pool URL doesn't apply either.

I have a Phoenix wallet opened and I can't find the URL.

Kept the default value in the config and it doesn't work. Also tried commenting it out and it doesn't work.

What do I add in the URL for solo mining?

use this:

url: 'http://127.0.0.1:8125' # solo mining with local wallet

i assume you run a full node on your pi? not just the phoenix wallet?

Thanks for that. No, I don't have a node running actually. I read the mining docs and I didn't read anything about running a node so I skipped that one. The only thing I read (or at least that's what I understood) is you:

  1. Plot; then
  2. Mine;
  3. Commit (for bigger earnings)

Is running a node a requirement?

My wallet is actually on a separate device (Mac and iOS).

solo mining requires you to submit your passphrase to a node. so you need a node you trust. And the only node you can trust is your own node.

Makes sense.

I was able to join a pool. Was actually waiting for confirmation a while ago. Not that that's come through, I added the pool url there. When I try to run it, I'm now getting this error

[INFO] Scavenger v.1.7.8
[INFO] SIMD extensions: none
[INFO] path=/path/to/directory, files=1, size=0.0227 TiB
thread 'main' panicked at 'called `Option::unwrap()` in a `None` value', src/libcore/option.rs:347:21
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

can you start scavenger via cmd? and before starting, enter:
set RUST_BACKTRACE=1

this will provide more information on what goes wrong.

I tried re-installing everything and got rid of the errors. Now Scavenger can't read any of my plots across my drives.

I plotted using turboplotter on both Mac and Windows 10 (via boot camp).

PS: I also opened an issue in signum-miner directly with the same concern but using different binaries link

I got it to work. I think.

I'm starting to see logs like these:


pi@raspberrypi:~/signum $ ./signum-miner 
10:57:30 [INFO]  signum-miner v.1.8.0
10:57:30 [INFO]  path=/media/pi/USB01/Burst, files=0, size=0.0000 TiB
10:57:30 [WARN]  no plots in /media/pi/USB01/Burst
10:57:30 [INFO]  path=/media/pi/DAS03/Burst, files=0, size=0.0000 TiB
10:57:30 [WARN]  no plots in /media/pi/DAS03/Burst
10:57:30 [INFO]  plot files loaded: total drives=0, total capacity=0.0000 TiB
10:57:30 [INFO]  reader-threads=3 CPU-threads=4
10:57:30 [INFO]  CPU-buffer=4(+4)
10:57:31 [INFO]  new block: height=892103, scoop=926                                             
10:57:34 [INFO]  new block: height=892104, scoop=2733 

That means it's working?

For reference, what worked was the 1.7.8 arm Linux CPU/GPU version.

The arch64 and the cpu only won't recognize the plots.

looks better but not there yet. the miner doesnt recognize your files...

total capacity=0.0000 TiB

Can you switch directio in config.yaml to false and try again?

Must have copied the wrong log. I was trying to switch around the plots maybe that's why. It's all good now. I even earned a small burst already as checked in the pool's calculator. Thanks for the help.