Fusion Test Network Upgrade

The FUSION test network will undergo a planned upgrade at block height 534,500, expected to arrive on Sunday, September 29, 2019. The exact time may change based on fluctuations in the average block time leading up to this block.

What does this upgrade involve?

The network upgrade is a hard fork, meaning all nodes will have to transition to the new chain to continue participating in the network. The improvements captured in this upgrade necessitate that the verification node needs to be adjusted, hence the hard fork.

Nodes that do not support the upgrade after block height 534,500, will no longer validate transactions on the Fusion test network.

What updates are included in this upgrade?

1. Check the SnapData data in the block header in the consensus.

2. Upgraded support for private swaps in the consensus.

3. Increase reporting and introduction of punishment mechanisms for ‘Double Blocking’.

4. Update PoS hash calculation method to V2 version.

5. Support transfer of short account numbers (USANs) through Fusion wallet interface.

6. Startup node will only start to buy tickets automatically after syncing to the latest block height.

7. Add interface fsn.getStakeInfo to get staking statistics.

What changes have been made to the APIs?

A. The original API functions remains compatible.

B. Additional API function to enable and disable autobuy ticket purchase and get staking statistics.

1. fsnbt.isAutoBuyTicket

2. fsnbt.startAutoBuyTicket

3. fsnbt.stopAutoBuyTicket

4. fsn.getStakeInfo

C. Modifications of the following API functions to add the optional parameter `toUSAN` to support the transfer of short account numbers (USANs).

1. SendAsset

2. assetToTimeLock

3. timeLockToAsset

4. timeLockToTimeLock

What are the steps necessary to execute the upgrade?

The instructions on how to update your node are in the efsn Fusion Github repository.

1. If you are building your test-net node from scratch:

Building efsn requires both a Go (version 1.11 or later) and a C compiler.

You can install them using your favourite package manager.

On Ubuntu 18.04, run these commands in order to build efsn:

add-apt-repository ppa:longsleep/golang-backports
apt-get update
apt-get install golang-go build-essential
git clone https://github.com/FUSIONFoundation/efsn.git
cd efsn
git checkout 3.1.0
make efsn

2. If you are updating a test net node. to the new code

1. Stop running your node
2. Go to your efsn installation directory
3. Run the following commands:

git pull
git checkout 3.1.0
make efsn

4. Redeploy your node

How does the upgrade impact me?

Whether you are holding native FSN, ERC20 FSN or BEP2 FSN, the planned upgrade will not impact you. You do not need to do anything, only the test net is being updated at this point in time.

If you are running a mining node / full node on the Fusion test net, then please download the latest Fusion client: v3.1.0 by following the instructions below. For users that are developing or testing applications on Fusion’s test net, you will need to support the hard fork to continue building.

I am running s mining node / full node on the fusion test net, what happens if I do not update to the latest version?

If you do not update your test net node to the latest version after the upgrade is executed, your client will use the pre-fork consensus rules to synchronize with other nodes that have also not supported the upgrade. Since the consensus rules have changed and are not compatible with each other, clients who do not update will not be able to send transactions on the updated Fusion test net.

What should I do as a service provider such as an exchange, a mining pool or a wallet?

If you are using an efsn client and API services, such as the RPC, API or SDK, please be aware of the changes that have been introduced to the test network. Test your application with the upgraded nodes as soon as possible.

Contact information:

- Fusion Telegram Channel

- Zendesk support

Disclaimer:

This is emerging, experimental and highly complex technology. If you choose to implement the recommendations in this article and continue to participate, please ensure that you have fully understood the impact of these recommendations on you. You should understand the risks involved in using experimental technology, including but not limited to unexpected code bugs. When executing on recommendations, please independently assess the risk of the results. This document and the recommendations therein are in no way a sales agreement and do not constitute a warranty in any sense, including but not limited to the warranties mentioned in the text for the Fusion network and the efsn client.