P2Pool v3.6 release
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
Yep, already upgraded and that sync was super quick.
Nice to see, I'm sure moneroos will be updated soon https://github.com/4rkal/moneroOS
Prolly gonna make a new release first thing tomorrow.
Can the wiki be updated for more user friendly in terms of guides
Wdym by more user friendly?
First installation setup and configuring the .json files do they just go in /COSMOS or into certain folders as when placed in /COSMOS it throws errors upon booting
What kind of errors?
p2pool has really come a long way in a pretty short time, the dev is a coding machine!
I see one of the two recommended priority nodes for monerod has been changed from node.supportxmr.com to p2pmd.xmrvsbeast.com. It seems that when a priority node is down, monerod doesn't start, which can be fixed by temporarily removing the offending --add-priority-node parameter (correct me if I'm wrong).
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.
I mean, when I try to start monerod, monerod fails to start if
sample.netin--add-priority-node=sample.netis down. I experienced that a few times, though it's just me.To Start p2pool:
Great connection @xmrvsbeast.com!
If you're a full node, you can just do
p2pool --host 127.0.0.1That would be the case if you use
--add-exclusive-node--add-priority-nodeshould not behave like that, not sure what the issue is with your situation.maybe try deleting your
p2pstate.binfile and restart monerodI 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-nodewouldn't hurt, I guess.)Anyway one of the two priority nodes, in a recommended command in README.md, has changed.
FYI: According to Github pages, v3.6 doesn't start on some OSes (e.g. CentOS, Windows 7) perhaps as an accidental side effect of the compiler change; fixed in v3.6.1.