cjdelisle / packetcrypt

Bandwidth-hard proof of work

PacketCrypt Pool Utils

YOU PROBABLY DON'T WANT TO BE HERE

You might have arrived here from outdated instructions. If you're looking to do ordinary mining, go to PacketCrypt mining instructions

Contents

• Master - pool coordinator
• BlkHandler - validator for block shares
• Paymaker - utility for handling payment

All configuration runs through pool.js

License

You may use this software under the terms of the LGPL-2.1 OR at your option, the LGPL-3.0. It is intended that you may embed this software in products, regardless of the licenses which those products use, however any changes to the internals of this codebase (for example to improve performance) should be made open source.

packetcrypt's Issues

AnnHandler

I am having trouble with the following piece of the Announcement Handler in the latest pool code. After matching the (in our case right now) pool.js to the pool.toml files, and making sure all the proxy stuff is setup right, and also making sure everything is externally resolving,
"annhandler.rs:350 This annhandler's URL [http://xxxxx.ourtld.ext] is not in the list from the pool"
Looking at this I think this stems from a bit of the changes that were made in this release, as it looks like when the public_url is not defined, this error is triggered.

./autogen.sh no longer exist in the github repository

Master node and handlers

I thought it was fixed using dev branch, but no luck I am having trouble with the following piece of the Announcement Handler and it's comms with master in the latest pool code, also main branch, or dev branch. After matching the (in our case right now) pool.js to the pool.toml files, and making sure all the proxy stuff is setup right, and also making sure everything is externally resolving,
"annhandler.rs:350 This annhandler's URL [http://xxxxx.ourtld.ext] is not in the list from the pool"
Looking at this I think this stems from a bit of the changes that were made in this release, as it looks like when the public_url is not defined, this error is triggered.

How is the data sent by the final C-end user socially reflected in PacketCrypt？

How is the data sent by the final C-end user socially reflected in PacketCrypt

pcblk efficiency decreases over time

In order to mine with maximum efficiency, you need to have the best announcement set in memory at the time of mining. The definition of the best announcement set is the set for which count * minimum_degraded_effort is the highest. Over time, the amount of degraded_effort (the value) of an announcement, so if the rate at which announcements are being made decreases, the block miner should recall announcements which were previously discarded as "not part of the best announcement set". Currently this is not happening.

An appropriate workaround is to simply restart the block miner every few minutes.

How mining revenue is distributed to announcement miners and block miners

How mining revenue is distributed to announcement miners and block miners