Skip to content

Releases: koh-gt/ferrite-core

Ferrite Core 3.1.2r1

01 Aug 17:02
Compare
Choose a tag to compare
Ferrite Core 3.1.2r1 Pre-release
Pre-release

Minor gitian build fixes, boost fixes. Small changes for improved Mac compatibility.
Documentation updates for dependencies and faster compilation.
Update of default installation path to C:\Program Files\Ferrite\ from C:\Program Files\_Ferrite_Core\ for Ferritext usage.

What's Changed

Full Changelog: v3.1.1...v3.1.2r1

Ferrite Core v3.1.1

30 Jun 16:43
333157d
Compare
Choose a tag to compare

This is a revision of Ferrite Core v3.1.0 based on v3.1.1r1 changes.

Final pre-MWEB revision. MWEB activation height 150,000.

If you are using v1.x.x or v2.x.x, please update to v3+ due to DAA change.

Ferrite Core v3.0.0+ is a hardfork of v2.1.2

(Fork height $250,000$, Current height: $142,901$ 2 Jul 2023)
Hard fork will occur later next year in 2024.

Nodes are encouraged to upgrade to v3+ when possible.

v3.1.1 wallets

OS Bit Name Link SHA256 Checksum
Windows 64 New/clean install Download 9425b0af58b07492b3b06ac94757f2578cfa952c4a5452e2fa117494d8ec7aa5
Windows 64 Wallet Update Download 6a332f4205855cacf0b10a2cdf55d361ddf4442bd807b52d6a71b2c15a71b110
Windows 64 Server Download b2ba278213f319589f2f20ee36a1bc22a262795ab1b702f5dc10ad7a87f01139
Linux 64 Wallet Update Download d5d598abf27ff89f0b2b04c276be4b5c5e6efaec39fc3eee8869b50855aabc2d
Linux 64 Server Download 6cea9c772318f705491e02e1ae2615c5d3a032af7b40dddfb7815654b3f0817c

Mining

List of pools and settings

MiningPoolStats

Changes

Changes in v3.1.1
Checkpoint added to height 149,000
Pruning is only automatically enabled for New installers for height > 500,000.
Pruning/Txindex can be disabled in ferrite.conf file.
Minor changes and security updates from Litecoin 0.21.2.2

Previous changes (in v3+)

Difficulty adjustment algorithm -> DarkGravityWell v3 from Dash (Darkcoin) by Evan Duffield

MWEB is optional

MWEB is optional for getblocktemplate as of v2.1.0. Mining pools that do not have MWEB compatibility can mine Ferrite, however no MWEB transactions will be validated and MWEB fees will not be collected.

MWEB will be currently optional since most miners mining Ferrite are currently not fully compatible with MWEB, which is a relatively new Litecoin feature.
Before, getblocktemplate on v2.0.0 must be called with the MWEB rule
getblocktemplate '{"rules": ["mweb", "segwit"]}'
Now, pools that are not compatible with MWEB can also validate blocks without MWEB transactions using
getblocktemplate '{"rules": ["segwit"]}'
For the near future, MWEB will be activated no earlier than 2024 to allow time for mining pools to gradually update for MWEB support.

Future changes

Checkpoint just after MWEB activation, new nodes.
MWEB fixes
Checkpoints for block 200,000 and 250,000 (important).
Small fixes if necessary.
MacOS compatibility issues when necessary.
Bitcoin 24.0 updates

Included in this release is a stratum-pool miner based on CCMiner v2.3.1 by @tpruvot with new pool configurations.
ASIC mining is recommended. You can opt to rent an Scrypt ASIC.

Everyone is invited to pull ferrite-core or join the Telegram group to suggest feature updates/chain parameters.
Setup guide

  • Windows and Linux builds compiled on Ubuntu Linux 22.10 by @koh-gt
    Uploaded on 1 Jul 2023.

Other notes

All versions of Ferrite Core wallets will maintain backwards compatibility

At height 250,000 all Ferrite will be split into 1 Ferrite (FEC) and 1 Ferrite Classic (FECC). v1.x.x and v2.x.x will only be able to spend the FECC portion, while v3+ will only be able to spend the FEC portion.
Do not be alarmed if coins sent through v1.x.x and v2.x.x (Ferrite Classic) do not appear in your v3+ (Ferrite) balance - your Ferrite balance is unchanged.
Coins sent to Ferrite Classic through Ferrite will not show up, but are not lost. Ferrite Classic users need to copy their wallet to a v3+ Ferrite Core client to be able to access the coins.
One can attempt to run both Ferrite Classic and Ferrite after Ferrite Classic is launched. Ferrite Classic may encounter hashrate instability.

What's Changed

Full Changelog: v3.1.0...v3.1.1

Ferrite Core 3.1.1r1

30 Jun 15:58
333157d
Compare
Choose a tag to compare
Ferrite Core 3.1.1r1 Pre-release
Pre-release

Added checkpoint at height 149,000
Adjusted pruning height to 500,000

Updates from Litecoin 0.21.2.2

Important Security Updates

This release contains fixes that harden node and network security. These fixes are important for every node operator and wallet user.
Limit and tightly manage memory usage in events of high network traffic or when connected to extremely slow peers. This protects nodes on lower end hardware to not run out of memory in the face of increased network activity.

RPC API Changes

Added addconnection for use by functional tests.
getpeerinfo provides 2 new fields per peer, addr_processed and addr_rate_limited, that track addr message processing.

What's Changed

Full Changelog: v3.1.0...v3.1.1r1

Ferrite Core v3.1.0

14 May 22:08
a761e4c
Compare
Choose a tag to compare

This is a revision of Ferrite Core v3.0.1 based on v3.1.0r1 changes.

If you are using v1.x.x or v2.x.x, please update to v3+.

Ferrite Core v3.0.0+ is a hardfork of v2.1.2

(Fork height $250,000$, Current height: $142,434$ 15 May 2023)
Hard fork will occur later next year.

Nodes are encouraged to upgrade to v3+ when possible.

Difficulty adjustment algorithm (DAA) changed to DarkGravityWell v3 activated on Block Height $250,000$ to avoid hashrate and difficulty oscillations for providing a stable and consistent block confirmation time. This is to avoid difficulty oscillations due to highly variable hashrate from abusing the default difficulty algorithm. More details on the new DAA hardfork upgrade can be found on the updated whitepaper.

Given the average block time has slowed from 70-80s to 300-600s in the past 10,000 blocks, this would provide at least 400 days of time for the difficulty algorithm hard fork. As the block emission schedule is unchanged, all funds stored or mined before this height will be safely compatible with v3.0.0 even in the case of late upgrading.

All current and future versions of Ferrite Core wallets will maintain backwards compatibility.

At height 250,000 all Ferrite will be split into 1 Ferrite (FEC) and 1 Ferrite Classic (FECC). v1.x.x and v2.x.x will only be able to spend the FECC portion, while v3+ will only be able to spend the FEC portion.
Do not be alarmed if coins sent through v1.x.x and v2.x.x (Ferrite Classic) do not appear in your v3+ (Ferrite) balance - your Ferrite balance is unchanged.
Coins sent to Ferrite Classic through Ferrite will not show up, but are not lost. Ferrite Classic users need to copy their wallet to a v3+ Ferrite Core client to be able to access the coins.
One can attempt to run both Ferrite Classic and Ferrite after Ferrite Classic is launched. Ferrite Classic may encounter hashrate instability.

v3.1.0 wallets

OS Bit Name Link SHA256 Checksum
Windows 64 Setup Download 528f7f23f52a484bafce9a0b14df930aa8b4660141fd6869867c1a0c910b1676
Windows 64 Qt Wallet Download 6c6dcd1d08801aeba7f5acc00b6d7cc175b37ef650fc65e7f6c6e1b684eed8c1
Windows 64 Qt + Daemon Download 130cde3f15bd89d52dd1368f500a0a2e2ed1dfa57b01a71777616f275aa42fce
Linux 64 Qt Wallet Download de4e854ff9ecfde363cb2228588e50fd5c34565fb98f4bc4a0bc397c4b3a4311
Linux 64 Qt + Daemon Download 5acbe0a21880b02946eb0f646beb130505c02eeae8fdeaed5436dfe99780da56
MacOS 64 Qt Wallet Download b840ebcd14a7da5923a97312a2d853359f6ed41ce6131fca397edaa56142bd3b
MacOS 64 Qt + Daemon Download 380d35876a8f51bebc996f9b84c946bd3a326670f5fa16d542c5d3a5e56699b6

v1.3.30 wallets (32-bit)

OS Bit Name Link SHA256 Checksum
Windows 32 Setup Download ebd11b7ad69435d492893351c051d90f9af96a46b3f8c5becb5abe589c977327
Windows 32 Qt Wallet Download 86841129b5625b2680ee0e9937af3b788b788038ba6e2aae37e9c131aee3a413
Windows 32 Qt + Daemon Download 6bcdc77631e3083553c253c56b8de980786c3787ac63f578a9c2b1f975b0804e

Mining

List of pools and settings

MiningPoolStats

Changes

Changes in v3.1.0
More addnodes are added into seeds for faster block synchronisation and a more reliable network.
MWEB is now deployed on mainnet and will be fully deployed when 97.5% of miners add the 'mweb' rule and include MWEB transactions. This consensus is determined by windows of 40 blocks, of which at least 39 blocks must be mined with the additional 'mweb' rule in order for MWEB to be fully activated.
MWEB is still usable even when the 'mweb' rule is not needed. This will however mean that some blocks may not include any MWEB transactions, leaving MWEB transactions in the mempool to wait for the next block that contains the 'mweb' rule for peg-in or peg-out.

When this consensus occurs, all blocks must require the additional 'mweb' rule and include MWEB transactions.
Till this happens, the 'mweb' rule is optional and MWEB transactions may need to wait in the mempool until a block is mined by a miner that includes MWEB transactions.

Previous changes (in v3.0.0)

Difficulty adjustment algorithm -> DarkGravityWell v3 from Dash (Darkcoin) by Evan Duffield

MWEB is optional

MWEB is optional for getblocktemplate as of v2.1.0. Mining pools that do not have MWEB compatibility can mine Ferrite, however no MWEB transactions will be validated and MWEB fees will not be collected.

MWEB will be currently optional since most miners mining Ferrite are currently not fully compatible with MWEB, which is a relatively new Litecoin feature.
Before, getblocktemplate on v2.0.0 must be called with the MWEB rule
getblocktemplate '{"rules": ["mweb", "segwit"]}'
Now, pools that are not compatible with MWEB can also validate blocks without MWEB transactions using
getblocktemplate '{"rules": ["segwit"]}'
For the near future, MWEB will be activated no earlier than 2024 to allow time for mining pools to gradually update for MWEB support.

Future changes

Taproot testing on Testnet 4
Checkpoints for block 150,000. 200,000 and 250,000 (important).
Small fixes if necessary.
MacOS compatibility issues when necessary.

Included in this release is a stratum-pool miner based on CCMiner v2.3.1 by @tpruvot with new pool configurations.
ASIC mining is recommended over GPU and CPU mining. You can opt to rent an Scrypt ASIC.

Everyone is invited to pull ferrite-core or join the Telegram group to suggest feature updates/chain parameters.
Setup guide

  • Windows and Linux builds compiled on Ubuntu Linux 22.10 by @koh-gt
  • MacOS builds are compiled on MacOS Monterey 12.0.1 by @koh-gt and @artucuxi
    Uploaded on 15 May 2023.

What's Changed

Full Changelog: v3.0.0...v3.1.0

Ferrite Core 3.1.0r1

14 May 20:56
9f06ef5
Compare
Choose a tag to compare
Ferrite Core 3.1.0r1 Pre-release
Pre-release

MWEB will be fully deployed when 97.5% of miners add the 'mweb' rule and include MWEB transactions. This is determined by windows of 40 blocks, where 39 blocks will be the cut-off.

When this consensus occurs, all blocks must require the additional 'mweb' rule and include MWEB transactions.
Till this happens, the 'mweb' rule is optional and MWEB transactions may need to wait in the mempool until a block is mined by a miner that includes MWEB transactions.

MacOS currently compiled and tested on Monterey 12.0.1.
Compatible for MacOS Big Sur 11 and MacOS Ventura 13.

What's Changed

Full Changelog: v3.0.1r1...v3.1.0r1

Ferrite Core v3.0.1

20 Apr 22:20
ffa7288
Compare
Choose a tag to compare

This is a revision of Ferrite Core v3.0.0 based on v3.0.0r1 changes.

Ferrite Core v3.0.0+ is a hardfork of v2.1.2

(Fork height $250,000$, Current height: $131,807$ 22 Apr 2023)

Nodes are encouraged to upgrade to v3 when possible.

Difficulty adjustment algorithm (DAA) changed to DarkGravityWell v3 activated on Block Height $250,000$ to avoid hashrate and difficulty oscillations for providing a stable and consistent block confirmation time. This is to avoid difficulty oscillations due to highly variable hashrate from abusing the default difficulty algorithm. More details on the new DAA hardfork upgrade can be found on the updated whitepaper.

Given the average block time has slowed from 70-80s to 300-600s in the past 10,000 blocks, this would provide at least 400 days of time for the difficulty algorithm hard fork. As the block emission schedule is unchanged, all funds stored or mined before this height will be safely compatible with v3.0.0 even in the case of late upgrading.

Current and future versions of Ferrite Core will maintain wallet backwards compatibility with all versions of Ferrite Core.

v3.0.1 wallets

OS Bit Name Link SHA256 Checksum
Windows 64 Setup Download da1accfa9800d7fb9af9c9c75d9bc3fbca66798064af969ac3a216ebf25ee04d
Windows 64 Qt Wallet Download 18c4e9a26be6528ffd2134a1cacca90574cc5216ea2a068c84d2b61544fb262f
Windows 64 Qt + Daemon Download f13b20323d24687d6c010f129dcc133a1e963c6bee461d361d15876915115c55
Unix 64 Qt Wallet Download 734e05d877bbe6fabc2303b32a29a72c0261e98f28af7a1ecf400bc0a24a29b1
Unix 64 Qt + Daemon Download c60c098188b11c4f64997b23d834382660fa433126f10cdd41e883d3e6b6065e

Mac wallets - In progress

Mining

List of pools and settings

MiningPoolStats

Changes

Changes in v3.0.1
More addnodes are added into seeds for faster block synchronisation and a more reliable network.
Testnet nodes have been added.
Testnet 4 is launched with DGWv3, Taproot and MWEB support enabled. You can get testnet coins from our Telegram or mine using generatetoaddress 1 <wallet_address>.

In order to switch to testnet mode, add this to the bottom of your configuration file ferrite.conf.

# testnet parameters
testnet=1   # Change this to 0 to switch to mainnet, 1 for testnet.
[test]
# Add your testnet settings below
#

Previous changes (in v3.0.0)

Difficulty adjustment algorithm -> DarkGravityWell v3 from Dash (Darkcoin) by Evan Duffield

MWEB is optional

MWEB is optional for getblocktemplate as of v2.1.0. Mining pools that do not have MWEB compatibility can mine Ferrite, however no MWEB transactions will be validated and MWEB fees will not be collected.

MWEB will be currently optional since most miners mining Ferrite are currently not fully compatible with MWEB, which is a relatively new Litecoin feature.
Before, getblocktemplate on v2.0.0 must be called with the MWEB rule
getblocktemplate '{"rules": ["mweb", "segwit"]}'
Now, pools that are not compatible with MWEB can also validate blocks without MWEB transactions using
getblocktemplate '{"rules": ["segwit"]}'
For the near future, MWEB will be activated no earlier than 2024 to allow time for mining pools to gradually update for MWEB support.

Future changes

Checkpoints for block 150,000. 200,000 and 250,000 (important).
New tab for wallet management (dumprivkey, importprivkey).

Included in this release is a stratum-pool miner based on CCMiner v2.3.1 by @tpruvot with new pool configurations.
ASIC mining is recommended over GPU and CPU mining. You can opt to rent an Scrypt ASIC.

Everyone is invited to pull ferrite-core or join the Telegram group to suggest feature updates/chain parameters.

  • Compiled on Ubuntu Linux 22.10 by @koh-gt
    Uploaded on 21 Apr 2023.

What's Changed

Full Changelog: v3.0.0...v3.0.1

Ferrite Core 3.0.1r1

20 Apr 21:34
d3057ae
Compare
Choose a tag to compare
Ferrite Core 3.0.1r1 Pre-release
Pre-release

Changes in v3.0.1
Built in addnodes, small fixes.
Testnet 4 launched with DGWv3, Taproot and MWEB support enabled.

From version 3.0.0r1

Exchanges and miners are encouraged to upgrade to v3.0.0 or v3.0.1 when possible

Given the average block time has slowed from 70-80s to 300-600s in the past 10,000 blocks, this would provide about 400 days of time for the difficulty algorithm hard fork.

No coin holdings will be lost for late upgrading.
However, coins mined using v1 and v2 will not be recognised after block 250,000 by v3, as such, some transactions made on old wallets may not be valid. Simply download ferrite-qt and your funds will be reflected. As the block emission schedule is unchanged, all funds stored or mined before this height will be safely compatible with v3.0.0 even in the case of late upgrading.

Alongside this, the DAA aims to make sudden difficulty drops and spikes avoidable. For instance, the network will adjust difficulty rapidly when the hashrate changes exponentially, while also avoiding feedback oscillations. -bitcoin.com 20171113

What's Changed

Full Changelog: v3.0.0...v3.0.1r1

Ferrite Core v3.0.0

12 Apr 21:02
91d4300
Compare
Choose a tag to compare

Ferrite Core v3.0.0 is a hardfork of v2.1.2

(Fork height $250,000$, Current height: $127,710$ 13 Apr 2023)

All nodes are encouraged to upgrade to v3.0.0 when possible.

Difficulty adjustment algorithm (DAA) changed to DarkGravityWell v3 activated on Block Height $250,000$ to avoid hashrate and difficulty oscillations for providing a stable and consistent block confirmation time. This is to avoid difficulty oscillations due to highly variable hashrate from abusing the default difficulty algorithm. More details on the new DAA hardfork upgrade can be found on the updated whitepaper.

Current block height -> $127,710$ as of 20230413 (Upgrade before 20240601)

Given the average block time has slowed from 70-80s to 300-600s in the past 10,000 blocks, this would provide at least 400 days of time for the difficulty algorithm hard fork.

No cold wallet holdings will be lost for late upgrading.
However, coins mined/transacted using v1 and v2 will not be recognised after block 250,000 by v3.
In this case, replace the old ferrite-qt with v3.0.0+ and your funds will be reflected.

As the block emission schedule is unchanged, all funds stored or mined before this height will be safely compatible with v3.0.0 even in the case of late upgrading.

Current and future versions of Ferrite Core will maintain wallet backwards compatibility with all versions of Ferrite Core.

v3.0.0 wallets

OS Bit Name Link SHA256 Checksum
Windows 64 Setup Download 4d788dd0b15dc1b2ef53d4717f9abea320ae6d8c177cdc7d1f8b86dc8b700ce2
Windows 64 Qt Wallet Download ca215e4d0392fb9d078791baec1daabe2b55c08c7daf436ac331b606c219428f
Windows 64 Qt + Daemon Download dbc25e74d053d00fb47062fa9ad10e2ff90925620f19a4849bcafd83aade794e
Unix 64 Qt Wallet Download 656d293e621577c688226d90c66287a482bfd2ca2754e1f8185fe598c6c3dc83
Unix 64 Qt + Daemon Download 0522f554092211acd5e597b91f91f2d51cb764ab1f44eb1e24b90dead262162d

Mining

List of pools and settings

MiningPoolStats

Changes

Difficulty adjustment algorithm -> DarkGravityWell v3 from Dash (Darkcoin) by Evan Duffield

MWEB is optional

MWEB is optional for getblocktemplate as of v2.1.0. Mining pools that do not have MWEB compatibility can mine Ferrite, however no MWEB transactions will be validated and MWEB fees will not be collected.

MWEB will be currently optional since most miners mining Ferrite are currently not fully compatible with MWEB, which is a relatively new Litecoin feature.
Before, getblocktemplate on v2.0.0 must be called with the MWEB rule
getblocktemplate '{"rules": ["mweb", "segwit"]}'
Now, pools that are not compatible with MWEB can also validate blocks without MWEB transactions using
getblocktemplate '{"rules": ["segwit"]}'
For the near future, MWEB will be activated no earlier than 2024 to allow time for mining pools to gradually update for MWEB support.

Future changes

Checkpoints for block 150,000. 200,000 and 250,000 (important).
New tab for wallet management (dumprivkey, importprivkey).

Included in this release is a stratum-pool miner based on CCMiner v2.3.1 by @tpruvot with new pool configurations.
ASIC mining is recommended over GPU and CPU mining. You can opt to rent an Scrypt ASIC.

Everyone is invited to pull ferrite-core or join the Telegram group to suggest feature updates/chain parameters.

  • Compiled on Ubuntu Linux 22.10 by @koh-gt
    Uploaded on 13 Apr 2023.

What's Changed

Changelog (from previous release v2.1.2): v2.1.2...v3.0.0
Full Changelog (from previous version v2.0.0): v2.1.2...v3.0.0
Complete Changelog: v1.0.0...v3.0.0

Ferrite Core 3.0.0r1

12 Apr 19:59
91d4300
Compare
Choose a tag to compare
Ferrite Core 3.0.0r1 Pre-release
Pre-release

Difficulty algorithm changed to DarkGravityWell v3 activated on Block Height 250,000 to avoid hashrate and difficulty oscillations for providing a stable and consistent block confirmation time. Current block height -> 127,692 as of 20230413
Upgrade before 20240601

Exchanges and miners are encouraged to upgrade to v3.0.0 when possible.

Given the average block time has slowed from 70-80s to 300-600s in the past 10,000 blocks, this would provide at least 400 days of time for the difficulty algorithm hard fork.

No coin holdings will be lost for late upgrading.
However, coins mined using v1 and v2 will not be recognised after block 250,000 by v3, as such, some transactions made on old wallets may not be valid. Simply download ferrite-qt and your funds will be reflected. As the block emission schedule is unchanged, all funds stored or mined before this height will be safely compatible with v3.0.0 even in the case of late upgrading.

Alongside this, the DAA aims to make sudden difficulty drops and spikes avoidable. For instance, the network will adjust difficulty rapidly when the hashrate changes exponentially, while also avoiding feedback oscillations. -bitcoin.com 20171113

What's Changed

Full Changelog: v2.1.2...v3.0.0r1

Ferrite Core v2.1.2

01 Apr 16:26
78bc2b9
Compare
Choose a tag to compare

This is a revision of Ferrite Core v2.1.1 based on v2.1.2r1 and v2.1.2r2 changes.

Pruning option disabled by default in ferrite.conf rather than settings to avoid potential txindex error when both txindex and prune is enabled. This line prune=1 can be removed from ferrite.conf to prevent the default configuration file from overriding Ferrite Core pruning option.

Default configuration file now has more built in addnodes and seednodes for faster block propagation and synchronisation.

Forwarding your external WAN port 9574 at your router allows your node to broadcast block information to miners faster, reducing the risk of another miner finding a valid block at the same block height during the block propagation process.

Forwarding port 9573 on your router can reduce propagation time by 500-2000 milliseconds, providing a 1-3% increase in mining output.

New 32 bit binaries will no longer be released, with the final release as v1.3.1. Current and future versions of Ferrite Core will maintain backwards compatibility with all versions of Ferrite Core.

v2.1.2 wallets

OS Bit Name Link SHA256 Checksum
Windows 64 Setup Download 4fdc2486f1bf1770cc4a8570ac0e620c44d1128fd29d3a5d823d86532a6da7d0
Windows 64 Qt Wallet Download d62683228a8de98272405e445327e22fb4952bd3b0c09e1cba4b8f9fa65c64fa
Windows 64 Qt + CLI Download d4c98da1268eacb5f02c3150d599d2dca5a0e2055ae369bf07ee293e3705b832
Unix 64 Qt Wallet Download cdd6008fb89f7793725db766024d2459d1b015ecda6e1f81994fcbb0ebfae726
Unix 64 Qt + CLI Download 99bf3a3cf348cfbba00d2f07eff5dfa73c0107e37ef794efd9356e48b345a4a1

v1.3.1 wallet for 32-bit (old release)

OS Bit Name Link SHA256 Checksum
Windows 32 Setup Download fef28d405e7ec2c2061ec7771c7e72323a3de8c6f2709595fe76c4699e038477
Windows 32 Qt Wallet Download f8055d287b89fa22987a0d886e0ac18953d6b7363ddfa10f2a9b6542acaa9ee2
Windows 32 Qt + CLI Download f60353297a737d906e8582fab7565b265aaafce99f4bbf238db597369f2e9af3

Mining

List of pools and settings

Miner Type Link SHA256 Checksum
CCMiner ASIC / GPU / CPU Download 6799b0d090e3007d5cebb8485744c0d07a68c5dd0f4df84c17198ba94dac2ffd

Changes

Built in nodes.
Default configuration file settings.
Small changes.

Future changes

Checkpoints for block 150,000.
New tab for wallet management (dumprivkey, importprivkey).

Included in this release is a stratum-pool miner based on CCMiner v2.3.1 by @tpruvot with new pool configurations.
ASIC mining is recommended over GPU and CPU mining. You can opt to rent an Scrypt ASIC.

Everyone is invited to pull ferrite-core to suggest feature updates/chain parameters.

  • Compiled on Ubuntu Linux 22.10 by @koh-gt
    Uploaded on 2 Apr 2023.

What's Changed

Full Changelog: v2.1.1...v2.1.2