4.4.0 Release Candidate 9 - Mempool fix

This release fixes the mempool issues the network was experiencing since the fork.
Update is most important for service operators, pools, and wallet servers.

Other actors are encouraged to upgrade as well to ensure the best possible network health and quick transactions.

Unless a critical bug is discovered, this will be the final post fork release on 4.4. branch.

Here is a quick script to upgrade from a default 4.4.0.5+:

cd
rm master.zip
rm -rd Bismuth-master
wget https://github.com/bismuthfoundation/Bismuth/archive/master.zip
unzip master.zip
rm Bismuth-master/config.txt
cp -a ./Bismuth-master/. ./Bismuth/

Then restart the node, fi
cd Bismuth;python3.7 commands.py stop

Mandatory 4.4.0.7 - Critical fix

A critical post fork hotfix is needed.

Upgrade is mandatory. Failing to upgrade will get you on a stalled chain.

More info on our discord.

Here is a quick script to upgrade from a default 4.4.0.5:

cd
rm master.zip
rm -rd Bismuth-master
wget https://github.com/bismuthfoundation/Bismuth/archive/master.zip
unzip master.zip
rm Bismuth-master/config.txt
cp -a ./Bismuth-master/. ./Bismuth/

Then restart the node, fi
cd Bismuth;python3.7 commands.py stop

Mandatory 4.4.0.5

Release for supply reduction fork.

The fork is scheduled at block 1,450,000

A critical hotfix was included lately.

Upgrade is mandatory and can be done by just replacing the node.py file from the Bismuth directory by the current one: https://raw.githubusercontent.com/bismuthfoundation/Bismuth/master/node.py
then restarting the node.

More info on our discord.

Stable 4.4.0.4

Release for supply reduction fork.

The fork is scheduled at block 1,450,000

All existing nodes will have to be upgraded before that.

4.4.0 Release Candidate 3

3rd release candidate for supply reduction fork.

This is a pre-release, for tests only.

The fork is scheduled at block 1,450,000

All existing nodes will have to be upgraded before that.

4.4.0 Release Candidate 1

First release candidate for supply reduction fork.

This is a pre-release, for tests only.

Fork is scheduled at block 1,450,000

All existing nodes will have to be upgraded before that.

4.3.0.8 Release candidate 2

This is the most up to date candidate for 4.3 branch, post fork.

4.3.0 was a mandatory update, in order to support the fork at block 1 200 000.
See: https://hypernodes.bismuth.live/?p=586

This release brings cleanup and safeties for late upgrades, or post-fork upgrade.
It's also the required release for newest hypernode versions, beta99 branch.

Warning: if upgrading from a previous version:
From the Bismuth directory, do:

• pip3 install bisbasic
• pip3 install -r requirements.txt
• rm -rd polysign

4.3.0.6 Release Candidate

This is the most up to date candidate for 4.3 branch, post fork.

4.3.0 was a mandatory update, in order to support the fork at block 1 200 000.
See: https://hypernodes.bismuth.live/?p=586

This release brings cleanup and safeties for late upgrades, or post-fork upgrade.
It's also the required release for newest hypernode versions, beta99 branch.

Warning: if upgrading from a previous version:
From the Bismuth directory, do:

• pip3 install bisbasic
• pip3 install -r requirements.txt
• rm -rd polysign

4.3.0.2 Post fork release, beta 1

This is the most up to date candidate for 4.3.0.2 release, post fork.

4.3.0 was a mandatory update, in order to support the fork at block 1 200 000.
See: https://hypernodes.bismuth.live/?p=586

This release brings a few cleanup and safeties for late upgrades, or post-fork upgrade.

Service operators, pools, exchanges, are invited to upgrade to that version.
Minimal changes have been added to the -beta6 pre-relase, for maximum compatibility.
Mainly, force reject old nodes versions.

Changelog: fixed api_ calls

4.3.0.1 Post fork release, beta 1

This is the most up to date candidate for 4.3.0.1 release, post fork.

4.3.0 was a mandatory update, in order to support the fork at block 1 200 000.
See: https://hypernodes.bismuth.live/?p=586

This release brings a few cleanup and safeties for late upgrades, or post-fork upgrade.

Service operators, pools, exchanges, are invited to upgrade to that version.
Minimal changes have been added to the -beta6 pre-relase, for maximum compatibility.
Mainly, force reject old nodes versions.