TestNet 0.8.4

TestNet 0.8.4

In this release we introduce optimizations to minimize memory footprint:

• Configuration setting to turn off transactions storage, that allows saving space in memory and on disk
• In-memory state was reimplemented in order to reduce memory consumption
• MVStore's page size was decreased to 4Kb

New settings in waves.conf:

• waves.mvstore-page-split-size - allows to change size of MVStore in-memory pages, default value 4096 bytes
• waves.blockchain.store-transactions-in-state - allows to switch transactions storage in state, default value "on"
• waves.blockchain.in-memory-chunk-size - sets the size of in-memory blocks window, the smaller value reduces the memory footprint, default value is 5
• waves.blockchain.in-mem-chunks-amount - number of in-memory windows, default value is 10, the fast rollback is possible up to in-memory-chunk-size * in-mem-chunks-amount blocks

We recommend to set Xmx parameter to 4G in case of transaction storage turned on, and 2G if you switched off transactions storage.

WARNING

Then transactions storage is turned off some API method calls could produce invalid results. We will fix it later.

NOTE

When updating from version 0.8.x, there's no need to delete blockchain or state files, just update executables. If you are updating from earlier versions, please be sure to read 0.8.0 release notes.

TestNet 0.8.3

TestNet 0.8.3

In this update

• Fixed the bug that caused multiple rebroadcasts of a key block
• Default JVM memory size increased to 2GB (application.ini)
• Default size of the in-memory state decreased to 110 blocks (waves.conf)

NOTE

When updating from version 0.8.x, there's no need to delete blockchain or state files, just update executables. If you are updating from earlier versions, please be sure to read 0.8.0 release notes.

TestNet 0.8.2

TestNet 0.8.2

In this update

• Various NG fixes and tunings
• Acceptable block time drift reduced to -100ms from -15 seconds

NOTE

When updating from version 0.8.x, there's no need to delete blockchain or state files, just update executables. If you are updating from earlier versions, please be sure to read 0.8.0 release notes.

TestNet 0.8.1

TestNet 0.8.1

In this release

• Fixed BlockV3 activation moment (it will be activated on TESTNET on block # 161700)
• Fixed API bug that replaced an addresses with a public key in few methods

NOTE

When updating from version 0.8.0, there's no need to delete blockchain or state files, just update executables. If you are updating from earlier versions, please be sure to read 0.8.0 release notes.

TestNet 0.8.0

TestNet 0.8.0

In this release:

• Waves Feature Activation Protocol (will be activated on TESTNET on Monday, October 16, 2017 9:00:00 UTC)
• Feature to reduce required balance for mining to 1000 Waves (Feature ID: 1)
• Feature to activate NG protocol (Feature ID: 2)

NOTE 1

Please, remove files blockchain.dat, state.dat and peers.dat after upgraiding to the version.

NOTE 2

Waves Feature Activation Protocol will be turned on the old way by timestamp. But new features (1 and 2) have to be activated according to the activation protocol. Please, read Waves Features Activation Protocol article and change your node's configuration file accordingly. By default, mining nodes will vote for NG activation (Featue ID: 2). And it will be approved after 3000 blocks and activated after another 3000 blocks.

MainNet 0.7.9

Version 0.7.9

This is security bug fix release.

Following issue was fixed:

• Possible infinite loop during validation was fixed

When updating from 0.7.x, there's no need to delete blockchain or state files. If you are updating from 0.6.x, please be sure to read 0.7.5 release notes to familiarize yourself with recommended update procedure.

Version 0.7.8 (Mainnet & Testnet)

Version 0.7.8

This is bug fix release.

Following issue was fixed:

• Incorrect handling of fork that contains an invalid block

The issue may lead to the stalled node. If you experienced node's failure to append new blocks, please update.

When updating from 0.7.x, there's no need to delete blockchain or state files. If you are updating from 0.6.x, please be sure to read 0.7.5 release notes to familiarize yourself with recommended update procedure.

Version 0.7.7 (Mainnet & Testnet)

Version 0.7.7

This is bug fix release.

Following issues were fixed:

• Known peers interchange was fixed, that will prevent node isolation
• Mainnet official nodes list was updated (please, update known-peers parameter in your configuration file according to waves-mainnet.conf)

When updating from 0.7.x, there's no need to delete blockchain or state files. If you are updating from 0.6.x, please be sure to read 0.7.5 release notes to familiarize yourself with recommended update procedure.

Version 0.7.6

Version 0.7.6

This is a maintenance-only release, which fixes two issues:

• UTX Pool no longer throws StackOverflowError when remove is called repeatedly (e.g. when rebuilding state from scratch)
• recipient field in Transaction JSON no longer contains address: prefix, which fixes compatibility with 0.6.x

When updating from 0.7.5, there's no need to delete blockchain or state files. If you are updating from 0.6.x, please be sure to read 0.7.5 release notes to familiarize yourself with recommended update procedure.

Version 0.7.5

Version 0.7.5

This release highlights include:

• Create Alias transaction will be activated at 2017-08-28T10:00:00Z
• New universal DEB package for both Upstart- and SystemD-based distributions
• State has been rewritten from scratch, also Blockchain and State data are now stored in two separate files
• Network layer has been rewritten from scratch
• Support for legacy JSON configuration file has been removed
• Numerous Matcher improvements
• You can now buy Waves without initial Waves balance for fee

Create Alias Transaction

New type of transaction introduced to create unique short and readable aliases for an account. It is possible to specify alias instead of full address for asset transfers and leasing transactions. Alias is a string between 4 and 30 characters long consisting of lowercase Latin letters, digits and symbols @, -, _, .. Create Alias Transaction costs 1 waves.

New DEB Package

We will no longer build two different packages for Upstart and SystemD. Instead, we will provide a single universal package, which includes required configuration files for both init systems. The new package also follows FHS, which means the following things have changed:

• waves user home directory is now at /var/lib/waves (/var/lib/waves-tesnet for Testnet). This is where blockchain, state and matcher data files are stored by default.
• Configuration file is now located at /etc/waves/waves.conf (/etc/waves-testnet/waves.conf for Testnet). It will be preserved even when you uninstall DEB package with --purge.
• Log files are written in a native fashion, message format has been tweaked. In Upstart-based distros, you'll find the log in /var/log/upstart/waves.log (/var/log/upstart/waves-testnet.log for Testnet). In SystemD-based distros, you can use journalctl to view the log.

If you want to change where ${waves.directory} points, you will need to edit the node's service configuration file. Changing this setting in waves.conf won't have any effect. This is a known limitation.

New Storage Formats

Some data files in ${waves.directory}/data need to be manually deleted when upgrading to this release from a previous version. When installing from a DEB package, ${waves.directory} is set to /var/lib/waves for a Mainnet package, and to /var/lib/waves-testnet for a Testnet package.

IMPORTANT: Due to internal format changes, you will need to delete your blockchain.dat file and re-sync your node. You can also download Mainnet blockchain snapshot (at height 623623) to speed up update process.

IMPORTANT: Please also delete ${waves.directory}/data/peers.dat. Peer databases created by node versions before 0.7.x are incompatible with this release.

Configuration File Changes

Empty strings are no longer accepted as "default" values. If you don't want to specify a seed or matcher account in waves.conf, just comment those lines out or remove them altogether.