Skip to content

Releases: plenteum/plenteum

v0.4.9 - Patch Release

20 Jan 02:33
Compare
Choose a tag to compare

MANDATORY PATCH RELEASE BEFORE BLOCK 400 000.

This release adds some additional transaction security to reduce the impact of TX flood attacks.

  • limits the total number of outputs allowed
  • limits the total number of fusion transactions allowed in the mempool
  • removes invalid traansactions from the mempool

v0.4.8

23 Dec 07:48
Compare
Choose a tag to compare

Upgrade to this release is required

Network Upgrade at block 400,000

Full Node Resync May Be Required

This release contains 2 fixes to the way that data is serialized/deserialzed. The fixes are necessary for the proper operation of Plenteumd; however, the fix may reveal data corruption in your local copy of the blockchain (both the database and underlying local cache). Unfortunately, the only way to resolve the data corruption is purge the corrupted data and resync from that point or perform a full resync.

If you encounter a message stating that your local blockchain cache is corrupted, please try the directions given (be patient, it may take a while).
Or, you may resync your node from scratch.

Checkpoints

To help speed up your sync, please use checkpoints.

Plenteumd Default Settings Change

The default database write buffer size, read buffer size, maximum open files, and background threads have decreased to help with daemon stability. The decreases are as follows:

Write Buffer Size: 1GB -> 256MB
Read Buffer Size: 1GB -> 128MB
Maximum Open Files: 500 -> 125
Background Threads: 10 -> 4
These values may need adjusted based on your system resources, configured limits, etc. Please review the Plenteumd --help for changing these values at runtime.
We recommend that pool and other service operators run with higher values for the best performance.

Release Notes

General Updates

Removed unused code and other general code cleanup
Removed some Boost dependencies throughout the codebase
Resolved OSX compilation errors in some environments
Resolved a bug when deserializing data in some edge cases
Added additional community seed nodes:
@CapEtn
Now builds consistently with boost >= 1.70

Plenteumd Updates

Resolved p2p-external-port out of range
Resolved setting db-enable-compression in a config file doesn't work
Moved a few warning messages to debug messages as part of normal network operations
Changed RocksDB compression engine from LZ4 to ZSTD for better compression ratios
Upgraded RocksDB to v6.4.0
Removed support for SQLite local blockchain cache due to performance issues
Removed support for RocksDB local blockchain cache due to storage amplification issues
Resolved an issue in returning RawBlocks via /getblocks endpoint
Added optional blockCount parameter to /getblocks endpoint
Improved the output of print_pool_sh in the daemon console
Improved the output of status in the daemon console
Improved the transaction validation routine to allow for faster transaction validation on adding to pool
Improved the pool transaction validation routine when a new block is added to the chain
The /queryblocksdetailed endpoint has been moved behind the --enable-blockexplorer-detailed configuration option
Updated daemon CORS policy to support request preflights -- (@kryptonchain)
Added the current version to the status command
Added ? as an alias of help in the daemon console
Added helpful error message that provides directions for recovering from blockchain cache corruption in the local data storage

zedwallet Updates

N/A

zedwallet++ (zedlwallet-beta) Updates

Resolved zedwallet-beta segfaults if you attempt to open a directory (@ExtraHash)
Added user-agent string to requests made to a node
Resolved issue when upgrading a wallet from legacy wallet structures
Resolved issue whereby locked inputs may have been removed from a wallet erroneously

wallet-service Updates

N/A

wallet-api Updates

Added user-agent string to requests made to a node
Resolved issue when upgrading a wallet from legacy wallet structures
Resolved issue whereby locked inputs may have been removed from a wallet erroneously

miner Updates

N/A

cryptotest Updates

N/A

wallet-upgrader (NEW)

Created a simple tool designed to upgrade wallets to the latest wallet format used by zedwallet++ and wallet-api

Known Issues

Error in JSON serialization in multiple RPC methods regarding large uint64_t values
Incorrectly resetting instead of rewinding on subwallet import

How To Sync Quickly

Visit the checkpoints how to use site for simple to follow directions on using checkpoints.

How To Compile

Please see the How To Compile section of the project README for instructions on how to compile this release on your system.

Thanks

Cryptonote Developers, Bytecoin Developers, Forknote Project, TurtleCoin Developers, Plenteum Community

v0.4.5

21 Jul 06:11
Compare
Choose a tag to compare

Special Notes

Please note, the build directions have changed, refer to the main Readme for instructions.

Upgrade to this release is required

Network Upgrade at Block 280,000

The v0.4.5 release of the core Plenteum software activates a network upgrade at block 280,000 that includes the following:

  • changed the difficulty algorithm parameters to allow for much faster network hashrate updates when large volumes of hash rate join or leave the network.
  • forces the verification of the signature counts on transactions send throughout the network.
  • helps reduce the risk of blockchain bloat from malformed transactions.
  • restricts transaction extra to a maximum of 1,0240 bytes to prevent chain storage bloat.
  • activates logic immediately that stops transactions exceeding this size limit from entering the transaction pool or being selected during the getblocktemplate calls; however, until block 280,000 transactions included in a block may still have transaction extra data exceeding the 1,0240 byte limit.

Pools, miners, and services can do their part by upgrading their daemons as soon as possible.

Release Notes

General Updates

  • Implements fork at 280,000 to reject new transactions with TX_EXTRA data > 1,0240 bytes and to reject new transactions where the signature count is incorrect for the number of inputs in the transaction.
  • Updates difficulty algorithm adjustment speed at height 280,000
  • Implements blockchain bloat protection from malformed transactions
  • Renamed PAGE_SIZE parameter in slow-hash functions that was causing errors when building for some users
  • Activated compiler cache for AppVeyor CI builds
  • Resolved a few edge case bugs whereby block synchronization may fall-through to different code paths
  • Resolved issue in AARCH64 builds that prevent the daemon from syncing to 100% height
  • Improved Mnemonics compilation speed
  • Resolved locale specific issue in Windows error messages
  • Updated to use platform independent randomness sources
  • Limits TX_EXTRA data field on transactions to <= 1,0240 bytes
  • CN Soft Shell algorithm altered (as yet unused by Plenteum) to allow for the user of CPU/GPU mining software
  • Removed all references to LWMA3 from the codebase to avoid any confusion about Difficulty algorithms in use
  • Resolved issue in some OSX build environments where building with the latest Xcode failed
  • Resolved an issue in the CMake build directions that were causing issues in a rare number of circumstances.
  • Added fundamental SQLite3 support into the project
  • Project now builds under MSVC 2019
  • Project no linked statically against OpenSSL for zedwallet-beta and wallet-api to facilitate encrypted communication with a node.
  • Upgraded MiniUPNP dependency from v1.9 to v2.1. Thanks @rixombea
  • Upgraded Crypto++ dependency to v8.2. Thanks @thinkpol2
  • Resolved issue whereby Release builds enabled assert() usage
  • Reorganized source code structure for better modularization of core libraries

Plenteumd Updates

  • Update core software to allow difficulty updates to NOT rely on block major version.
  • Resolved issue regarding consistent logging.
  • Increased the log level of the daemon when existing to provide insight and better error reporting when the daemon appears to hang while exiting.
  • Resolved issue with imprecision in fork countdown in status command.
  • Added optional blockCount parameter to getwalletsyncdata method.
  • Resolved various issues regarding Lite Blocks propagation.
  • Resolved Block Transactions Blob Shuffle.
  • Resolved Timestamp Locked Input Transactions.
  • Added --resync CLI argument that makes it easier to perform a full resync than searching for and deleting the data directory.
  • Added --rewind-to-height # CLI argument to allow for rewinding the local blockchain to a specific height thereby allowing us to overcome DB corruption errors.
  • Added --p2p-reset-peerstate CLI argument to allow for clearing the p2p state information.
  • Added support for lz4 compression in RocksDB backend.
  • To use, specify --db-enable-compression as a CLI argument.
  • Added experimental feature to allow the use of RocksDB for the local blockchain cache that replaces the .bin files.
  • Added experimental feature to allow the use of SQLite3 for the local blockchain cache that replaces the .bin files.
  • Updated JSON serialization methods.

zedwallet Updates

  • N/A

zedwallet-beta Updates

  • Replaced wallet saving/loading with rapidjson library.
  • Optimized synchronization flow logic.
  • Resolved edge case where wallet crashes when using a view wallet.
  • Added the ability to return the transaction private key of a transaction you have sent. If you reset or rebuild your wallet, this option will not work.
  • Added additional logging facilities.
  • Resolved issue with the display of the future unlock time in the UI if the input is locked as it comes in.
  • Resolved Prune spent inputs after some period of time from WalletBackend.
  • Resolved Rare Transaction Double Add Bug in WalletBackend.
  • Resolved Support Blockchain cache API in Nigel.
  • Resolved Added SSL support for talking to remote node(s). Activate it with a node via the --ssl CLI argument.
  • Resolved WalletBackend syncing doesn't remain O(1) when increasing the number of wallets.
  • Resolved Small bug in getFusionTransactionInputs().
  • Better daemon address parsing.
  • Refactored common utilities.
  • Added wallet synchronization backoff mechanism in the event that there is trouble retrieving blocks from the node.
  • Allow node to return earlier blocks during initial sync when scan height is specified.
  • Updated JSON serialization methods.
  • Aligned backup keys prompts to match current zedwallet order.
  • Resolved issue whereby the node fee was not being redectected correctly on swap of node.

wallet-service Updates

  • Restored -l CLI argument for the --log-file option.
  • Updated JSON serialization methods.
  • Resolved issue with opening View Only wallets in wallet-service.

wallet-api Updates

  • Added /balances endpoint.
  • Added optional unlock time parameter to /send/advanced endpoint.
  • Now returns the privateSpendKey when creating a new address.
  • Replaced wallet saving/loading with rapidjson library.
  • Resolved an error whereby two wallet-api instances attempted to share the same bind port and address.
  • Optimized synchronization flow logic.
  • Various bug fixes to improve stability and overall experience.
  • Resolved edge case where wallet crashes when using a view wallet.
  • Added new /address/validate endpoint.
  • Enhanced endpoints to allow the wallet to be open or closed depending on the endpoint used.
  • Added additional logging facilities.
  • Added publicSpendKey to /addresses/create.
  • Now performs additional validation of parameters on numerous endpoint calls.
  • Resolved Prune spent inputs after some period of time from WalletBackend.
  • Resolved Rare Transaction Double Add Bug in WalletBackend.
  • Resolved Support Blockchain cache API in Nigel.
  • Added SSL support for talking to remote node(s). Activate it with a node via the --ssl CLI argument.
  • Resolved WalletBackend syncing doesn't remain O(1) when increasing the number of wallets.
  • Resolved Small bug in getFusionTransactionInputs().
  • Added wallet synchronization backoff mechanism in the event that there is trouble retrieving blocks from the node.
  • Allow node to return earlier blocks during initial sync when scan height is specified.
  • Resolved issue whereby the node fee was not being redectected correctly on swap of node.

miner Updates

  • N/A

cryptotest Updates

  • Cleaned up and optimized duplicated code
  • Added benchmarks for underivePublicKey and generateKeyDerivation

How To Sync Quickly

Download the latest checkpoints.csv here https://github.com/plenteum/checkpoints/raw/master/checkpoints.csv
Place checkpoints.csv in the same folder as your Plenteumd daemon
Run Plenteumd with checkpoints added like this:
Linux, Apple ./Plenteumd --load-checkpoints checkpoints.csv
Windows Plenteumd.exe --load-checkpoints checkpoints.csv

Thanks

Cryptonote Developers, Bytecoin Developers, Forknote Project, TurtleCoin Developers and the Plenteum Community
Special Thanks to @rixombea, @thinkpol2, @anonanonymous, @zpalmtree and @brandonlehmann

v0.3.0 - Mandatory update before block 130, 000

08 Jan 04:05
Compare
Choose a tag to compare

This is a mandatory update to the core software including a PoW Algorithm change at block 130, 000. It's important that you update your software before this block height is reached.

You can read about the updates here: https://medium.com/@whassupza/introducing-plenteum-v0-3-0-338021614220

v0.2.3 - Mandatory Update before Block 67500

26 Oct 05:26
59b9fba
Compare
Choose a tag to compare

This release is an update to allow for larger transactions and block sizes from Block 67500. This is a mandatory update so please ensure you update your software before block 67500.

v0.2.2

21 Oct 16:32
Compare
Choose a tag to compare

Release includes 0 fees and first stage of dust extraction to the dust fund.

IMPORTANT NOTE: Due to the fact that it will take some time to get the entire network updated, and older nodes will still require a minimum transaction fee, we strongly recommend that you continue to send transactions with a minimum fee of 0.1 PLE to ensure those transactions are not rejected by older nodes.

Initial Release

03 Aug 06:36
17a382f
Compare
Choose a tag to compare

First Official Release of Plenteum

** Do not use poolwallet ** - use zedwallet, GUI (for windows users) for personal wallets, or service for rpc wallet

** A Note about the GUI - if you are having trouble connecting to the service using the remote nodes, we suggest you run a local instance of Plenteumd and then start up the wallet once it is sync'd.

Special Thanks to discord community Hero & moderator Charlie for the Linux binaries - compiled for ubuntu 16
note** if you're running 18 and having issues with zedwallet & libreadline, please see Charlie's mining guide which has some additional info on how to deploy these binaries to Ubuntu 18.
And another huge thank you to discord community member JerMe404 for the OSX binaries...