Monero Mining

248 readers

1 users here now

founded 1 year ago

MODERATORS

[email protected]

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* (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.