Mainnet Release: v1.1.4.2

This release fixes issues related to memory leaks and a new maxDepth check for tip selection. The -e flag has also been removed.

Mainnet Release: v1.1.4.1

This version fixes an issue related to claims and confirmation rate of value transfers. This is a mandatory upgrade.

Mainnet Release: v1.1.4

This is the official release of the improved and refactored version of the IRI Java core. After having been thoroughly tested and optimized in our own private deployments, as well as several public testnets, we are releasing the refactored version on the IOTA mainnet. This client brings with it many improvements (all of which will be discussed in a technical blog post), and you can expect overall better performance on both, resource usage as well as confirmation rates. A quick summary of some of the changes:

• More performant DB engine (utilizing RocksDB)
• Accelerated solidity
• Improved networking, including the support of TCP alongside UDP
• API runtime improvements (especially for getBalances and getInclusionStates
• Quadratic tip selection speedup
• ... a lot more

It should be noted that the release of the refactored version is a planned in several stages. In this release, we are not doing a snapshot, for the specific purpose of further testing the software. You can expect more information about this to follow soon.

What you have to do

As this is a new release, we want to completely revamp the mainnet. What this means is that you have to do the following steps:

1. Make sure to delete your entire IRI database. Make sure to also not use any of the older IRI versions (even though both versions are compatible and have been tested, we want to have the entire network upgrade to the new version).
2. Remove all of your neighbors. Go to #nodesharing to find new neighbors. We want to start with a fresh new topology.
3. Change your minWeightMagnitude to 13. In this release we have downgraded the minWeightMagnitude to 13. The decision on minWeightMagnitude is not final, but with the testing over the coming days we will be able to assess this and make a final decision. Expect your transactions to be made a lot faster now 😄
4. 🎉 🎉 🎉

For those with remaining claims

We will be turning off the automated claims before the exchange launch, as such please make your automated claims as soon as possible. We cannot guarantee that they will be processed manually in time before the exchange launch.

Testnet Release: 1.1.3.10

This testnet release is accompanied by a new reset of the testnet.

NEW PORTS

Protocol	Port
TCP	15777
UDP	14777

What you have to do

As we are completely resetting the network, you have to do the following:

1. After having shut down your current node, remove the ixi, testnetdb and testnetdb.log folders
2. Download version 1.1.3.10
3. Remove all of your existing neighbors. Pick a new port UDP or TCP receiver port for your node. We suggest you to use the following setting: -t 15777 -u 14777 (TCP Port 15777; UDP Port 14777)
4. Before you start your node, make sure you have actually followed steps 1 through 3.
5. Search for new neighbors in #testnet-nodesharing

Testnet Release: 1.1.3.9

This release brings again some major improvements to performance, this time related to syncing, restarting and becoming solid. With this release, we are also restarting the Testnet. This means that you have to carefully read the instructions below.

It should be noted that we have also added the --max-peers flag. This new flag lets you determine how many neighbors you will accept in non-mutual tethering mode. Initially it is set to 0, indicating that you want mutual tethering. Increase it to a higher number that you're comfortable with (usually between 7 and 9)

What you have to do

As we are completely resetting the network, you have to do the following:

1. After having shut down your current node, remove the ixi, testnetdb and testnetdb.log folders
2. Download version 1.1.3.9
3. Remove all of your existing nodes. Pick a new port UDP or TCP receiver port for your node (e.g. -t 14666 -u 14666)
4. Before you start your node, make sure you have actually followed steps 1 through 3.
5. Search for new neighbors in #testnet-nodesharing

Testnet Release: Version 1.1.3.7

This is a new version of the refactored IRI client. This version is specifically targeted for the newly announced IOTA testnet. Please ensure to follow all suggested instructions:

HOW TO RUN THIS VERSION

• Ensure that you run this version with the --remote. You can --remote-limit-api all calls except for getNodeInfo and `getNeighbors
• Run it with minWeighMagnitude: 13
• Run it with --port 14900.
• Run it with the --testnet option

Here is an example on how to successfully and correctly launch IRI:

java -jar iri-1.1.3.7.jar -p 14900 --testnet -n 'udp://14.14.14.14:14900 udp:13.13.13.13:14900' --remote --remote-limit-api 'attachToTangle, addNeighbors, removeNeighbors'

Testnet Release: Version 1.1.3.8

Version 1.1.3.8 brings some major changes to IRI. Most notably bootup and shutdown times have increased significantly and overall DB performance has improved.

IMPORTANT

We have introduced some breaking changes to the database, as such you are required to delete your database folder. Delete the testnetdb folder before starting the new version.

Main net 1.1.2.2

Mainnet new Release 1.1.2.2.

Release: 1.1.2

First major release since 1.1.0.1. Many new additions such as flags and complete refactoring of the codebase.

Testnet Release: 1.1.2

Merged all changes from dev into the testnet branch.