this post was submitted on 31 Aug 2023
2 points (62.5% liked)

Monero Mining

226 readers
1 users here now

founded 1 year ago
MODERATORS
[email protected]
[email protected]
2
P2Pool v3.6 release (monero.town)
submitted 1 year ago by [email protected] to c/[email protected]
16 comments fedilink hide all child comments
 

P2Pool v3.6 was released.

Changes:

  • Avoid unnecessary block broadcasts and block requests to save traffic (works best when connected to v3.6+ nodes)
  • 2 times faster initial sync when connected to v3.6+ nodes
  • Release binaries for Windows are now built with clang compiler (7-8% faster block verification)
  • Tweaked how release binaries for other OS are built, binary sizes are reduced significantly
  • Fixed a rare data race bug that could happen during block verification
  • Added a full source code archive with all dependencies

Github - SChernykh p2pool

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

Your monerod should have it's own node list, especially if it has been on the network for some time. A priority node being offline should not affect your node.

[–] [email protected] 1 points 1 year ago (2 children)

I mean, when I try to start monerod, monerod fails to start if sample.net in --add-priority-node=sample.net is down. I experienced that a few times, though it's just me.

[–] [email protected] 2 points 1 year ago (1 children)

To Start p2pool:

p2pool --host p2pmd.xmrvsbeast.com --rpc-port 18081 --zmq-port 18084

Great connection @xmrvsbeast.com!

[–] [email protected] 1 points 1 year ago

If you're a full node, you can just do p2pool --host 127.0.0.1

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

That would be the case if you use --add-exclusive-node

--add-priority-node should not behave like that, not sure what the issue is with your situation.

maybe try deleting your p2pstate.bin file and restart monerod

[–] [email protected] 1 points 1 year ago

I see. Disregard it then, it might have been something accidental. Actually I didn't check if the node was up or down, so it was just a guess. (If someone happens to experience a weird error where the daemon refuses to start, tweaking --add-priority-node wouldn't hurt, I guess.)

Anyway one of the two priority nodes, in a recommended command in README.md, has changed.