PegNet Software Update Released — Activation On Monday December 9th at 17:00 UTC

PegNet Version 0.3.0 Goes Live Block 222,270

Important PegNet Update

Notes below from the PegNet developers about this big update to the software.

“A PegNet update is ready and requires a mandatory update by all users and miners. The update has a block height activation of 222270, estimated to be Dec 9, 2019, at 17:00 UTC. You MUST update by this block height. This is a hard fork of the PegNet chain. This update spans just about every repo associated with PegNet. It is recommended to read the release notes https://github.com/pegnet/pegnet/releases/tag/v0.3.0 in their entirety. Any questions or concerns about updating can be directed to #support channel on the PegNet Discord.

For PegNet Miners

Listed below are the miners that need to update. If you fall into a category that needs to update, you must also update your Datasources. The exact method of updating your config should be listed in the release notes. If you have any specific questions, please direct them to #support. - If you are mining PEG, and operating the reference miner https://github.com/pegnet/pegnet/releases, you must download the latest release.

Only net coordinators or solo miners need to be updated. The netminer does not need to be updated. - If you are mining as apart of a pool, you do not need to do anything. The pool operators will update for you. - If you are running a mining pool, you will need to update your software. Please contact me if you have questions about what software updates need to be made. If you are running the open-source Prosper Pool software, your release update can be found here https://github.com/FactomWyomingEntity/prosper-pool/releases.

The Orax pool has been notified and will also be updated before the release. If you are running a mining operation with a custom software solution, you may reach out to me (@Emyrk) specifically if you need help getting these updates.

For Pegnetd Users

For users making transactions + conversions, you will need to update pegnetd. You can find the latest release on this page https://github.com/pegnet/pegnetd/releases. The biggest change is the 5K PEG Supply Capacity being enforced per block starting at the activation. This update enforces the PEG Conversion Capacity per block to be 5K. In the future, this 5K will be the lower bound, meaning 5K+ PEG can be converted per block based on a PEG Conversion Capacity equation and block height. Information regarding that change will be released with ample lead time.

If you wish to know how this will be implemented, you may read the release notes https://github.com/pegnet/pegnet/releases/tag/v0.3.0. If you are using the pegnetd api, there is a change to the conversions api output to handle this new behavior. An example of a new PEG conversion after the activation height can be found in this PR: https://github.com/pegnet/pegnetd/pull/98.

The remaining funds after the partial conversion are returned in the output field as a transfer to the original address. If you are using the pegnetd api for an application and need assistance, you may reach out in #support and ping me (@Emyrk#6604).

Summary

I advise you to read this announcement in its entirety. All parties in PegNet are affected by this update.”