Pre-release

@petermz petermz released this Aug 2, 2018 · 303 commits to master since this release

Assets 4

In This Release

This is a bugfix release.

Update notes

We have rolled back the Testnet blockchain to the last compatible block. Please resync your nodes from scratch, or import this blockchain file

Pre-release

@alexeykiselev alexeykiselev released this Jul 24, 2018 · 309 commits to master since this release

Assets 4

In this release

This is a feature-freeze release. Smart Accounts are getting their final shape.

  • Performance, storage and API polishing improvements to Smart Accounts
  • Configuration cleanup

Bug Bounty

We have started the Bug Bounty Program. Please, read the related forum topic. You can apply if you have found the bug both Mainnet or Testnet.

Update notes

We have rolled back the Testnet blockchain to the last compatible block. Please, resync your nodes from scratch or use import.

@alexeykiselev alexeykiselev released this Jun 26, 2018 · 776 commits to master since this release

Assets 4

In this release

This is a bug fix release. We have fixed various API bugs and validation issues.

This is mandatory release. Miners have to update to this release before the activation of the Data Transaction feature.

Update notes

We have made some changes to the storage's structure. Please, rebuild your node's storage.
Use lates binary blockchain file to import or resync the node from the network.

Checksums

MD5 (waves-all-0.13.4.jar) = f114d4366b9b5cb429e39fbc5f3c23ad
MD5 (waves_0.13.4_all.deb) = a7c61d81765eeb8a95a7a35bd43865f0

@alexeykiselev alexeykiselev released this Jun 7, 2018 · 817 commits to master since this release

Assets 4

In this release

What is Data Transaction

Data Transaction allows storing additional information on the account. For now, this information could be used by third-party services, but as soon as Smart Contracts will come to Mainnet, this information could be used during transaction validation.
Please, reade detailed information about Data Transaction.

Burn Any Tokens

Now it is possible to burn any tokens your own before this update it could be done only by the issuer of the token. Read about the token burning.

How Fee Sponsorship works

Fee Sponsorship is here to replace the transactions fee paid in assets. Not all node owners were happy with receiving various assets as the fee paid for transactions processing. Now the things are going to change. After activation of this feature to process the transactions paid in assets issuer of the asset should set up a sponsorship for the asset. Sponsorship is a sum of Waves that the issuer is willing to pay for the processing of transactions paid in the asset. Miners will receive only Waves as the fee.
Please, read additional information about Sponsor Fee Transaction and Sponsored transactions.

Fair PoS

Fair PoS is an adjusted consensus algorithm that provides accurate performance ratio of mining. Please, read the paper about Fair PoS and following discussion.

Optimized Level DB storage

We've optimized node's storage. Some caches were put in-between that speed up the data processing. Import of the blockchain from a binary file is twice faster now. Due to this optimization, the node's storage should be rebuilt. Please, refer the update notes.

New features voting

With this release it is possible to activate following features:

  • Data Transaction, feature number 5
  • Burn Any Tokens, number 6
  • Fee Sponsorship, number 7
  • Fair PoS, feature number 8

To vote for any set of available features, please add them to node's configuration file as follows:

features {
    supported = [5, 7] # This is an example, make your own decision what vote for
}

How to update

Basically, the node should be updated as follows:

  1. Stop the node
  2. Export existing blockchain to a binary file or download binary file
  3. Update node's executables
  4. Import binary file
  5. Start the node

Prepare binary blockchain file

After stopping the node execute following command to export existing blocks to a binary file:

sudo -u waves java -cp '/usr/share/waves/lib/*' -Dwaves.directory=/var/lib/waves com.wavesplatform.Exporter /etc/waves/waves.conf /usr/share/waves/mainnet

Or download binary blockchain file created for you at height 1,031,479.

Import binary file

Remove data folder:

sudo rm -rdf /var/lib/waves/data

Install the new version of the node:

sudo dpkg -i waves_0.13.3_all.deb

Import blocks from the binary file:

sudo -u waves importer /etc/waves/waves.conf /usr/share/waves/mainnet-[some height]

After import do not forget to remove the file:

sudo rm /usr/share/waves/mainnet-[some height]

Checksums

MD5 (waves-all-0.13.3.jar) = 061750cd20ef7ade66795129282717f3
MD5 (waves_0.13.3_all.deb) = 3f676c6512a11c25fbac3143d5a5d73a

Pre-release

@alexeykiselev alexeykiselev released this Jun 6, 2018 · 845 commits to master since this release

Assets 4

In the release

  • We have fixed the bug with a rollback of a Fee Sponsorship transaction
  • New in Smart Accounts:
    • Union Types, Case Types and Type Matching: Transaction = TransferTransaction | IssueTransaction | DataTransaction ...
    • Initialization of arrays using base64 text
    • Useful information in error message then a transaction is not allowed by the script
  • Update to RIDE IDE: multiple tabs and Base64 support

What are Union Types, Case Types and Type Matching

Previously it was not neccessary but very important to check transaction type before accessing field:

if (tx.type == 4) tx.recipent == ...

But that's error-prone, because

if (tx.type == 44) tx.recipent == ...

would still compile and result in execution error.

With this change, each transaction type has its own fields, and you have to match tx type first:

match tx {
 case t: TransferTransaction => t.recipient = ...          # works
 case d: DataTransaction =>     d.recipient = ...          # won't compile!
 case _ => false
}

In this example, tx, d don't have recipient field, but t has. All calls to transaction fields are now exception-free.

Update notes

Due to changes to RIDE scripts serialization we have to truncate the Testnet's blockchain. Please, delete existing data and resync from the network.

Pre-release

@alexeykiselev alexeykiselev released this May 28, 2018 · 1027 commits to master since this release

Assets 4

In this release

This is a bugfix release. The bug in the NXT PoS, that was introduced in v0.13.0, was fixed.

Update notes

Some blocks in Testnet are invalid. In order to switch on the correct chain, please, delete existing blockchain data and import blocks from a binary file or the network.

Pre-release

@phearnot phearnot released this May 23, 2018 · 1076 commits to master since this release

Assets 4

In this release

  • Fair PoS
  • DataTransaction update (increased value size, string data type, base64 encoding)
  • Smart Contracts improvements
  • Waves and Asset distribution report performance improvements

New features

Please vote for new feature 8.

Update notes

With this release, we're rolling back Testnet blockchain to block 366057 to accommodate for changes in the way Sponsor Fee Transaction is signed. Please, use import/export routine or download the blockchain from the network.

May 15, 2018
Version 0.10.4
Matcher will now use leveldb-backed snapshot store.
Pre-release

@alexeykiselev alexeykiselev released this Apr 28, 2018 · 1340 commits to master since this release

Assets 4

In this release

  • Smart Accounts & Smart Assets
  • Fee Sponsorship

New features

  • Feature 4 "Smart Accounts"
  • Feature 7 "Fee Sponsorship"

Read more about Fee Sponsorship at new Waves Documentation site.

Please, read about Smart Accounts & Smart Assets.
The IDE for Smart Contracts programming language RIDE is available at ide.wavesplatform.com. Feel free to ask questions and discuss Smart Accounts at our Discord channel #smart-contracts.

Please, vote for new features 4 and 7.

Note about activation of Fee Sponsorship

Activation of "Fee Sponsorship" starts a cooldown period of 3000 blocks (on Testnet). During this time it is possible to create Fee Sponsorship transactions, but they will be active and will replace the Assets Fee Settings only at the end of the cooldown period.

Update notes

A minor bug in the state was fixed. Because of this, the full rebuild of the state is required. Please, use import/export routine or download the blockchain from the network.

Pre-release

@alexeykiselev alexeykiselev released this Apr 6, 2018 · 1723 commits to master since this release

Assets 4

In the release

  • New feature 6 "Burn any tokens"; It's now possible to burn an asset by any owner not only by an issuer, of course, the burn is limited by the amount in possession
  • Fixed bug of how Data Transaction stored

Please, start voting for Feature 6.

Update notes

In case of moving from version 0.11.0 before activation of Data Transaction just update binary files, no need to rebuild the storage.
If you are moving from an older version or version 0.11.0 after activation of Data Transaction, please, remove existing data and reload from the network.