Skip to content

Releases

Fulcrum 2.1.4

Choose a tag to compare

@cculianu cculianu released this 18 Oct 23:02
02e22da

What's New:

Fulcrum 2.1.4 is a maintenance release of the 2.x series. It contains one important performance optimization when servicing subscriptions and the blockchain.*.get_history RPCs. This optimization can yield up to a 5x-10x speedup for this particular RPC call in some cases. All users of Fulcrum are recommended to update to this release to reap the performance benefits!

Detailed Summary of Changes (vs v2.1.3)

  • Performance: Storage::getHistory (used by the subscriptions and the history RPCs) is now 5x-10x faster for "uncached" lookups (as in from a cold start or when the txhash cache lacks the entries). This is a huge performance benefit discovered by @sethforprivacy . Special thanks to him! For more info, see: PR #335, and also this X thread: https://x.com/sethforprivacy/status/2110672740902396397
    • This performance speedup involves a new tiny subsystem to lookup the hashes in parallel, the behavior of which is controlled by the new conf file parameter history_lookup_threads.
    • You normally don't need to touch this parameter since the default setting is good for almost all systems.
  • Updated the internal servers.json seed list for BCH and BTC networks.

Pre-compiled Binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-2.1.4-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-2.1.4-arm64-linux.tar.gz, which is compiled on an Ubuntu 20.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, libminiupnpc, Qt6Core, Qt6Network (from Qt 6.10.0), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled Binaries for Windows

  • Fulcrum-2.1.4-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, libminiupnpc, Qt 6.10.10, OpenSSL 3.3.0, and gcc 15.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!

Fulcrum 2.1.3

Choose a tag to compare

@cculianu cculianu released this 02 Oct 21:36
7ccabb8

What's New:

Fulcrum 2.1.3 is a minor maintenance release of the 2.x series. It contains one important bugfix as well as a refresh of the jemalloc library that is compiled with the release binary.

Detailed Summary of Changes (vs v2.1.2)

  • Bugfix - Fix a bug with the internal Merkle::Cache class whereby it sometimes had an off-by-1 error. On BCH mainnet can be triggered with specifying cp_height on a certain boundary. Thanks to Jonathan Silverblood for catching this one.
  • Updated the jemalloc library we compile into the release binary to version 5.4.0 latest.
  • Some other minor internal nits and fixups.

Pre-compiled Binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-2.1.3-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-2.1.3-arm64-linux.tar.gz, which is compiled on an Ubuntu 20.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, libminiupnpc, Qt6Core, Qt6Network (from Qt 6.10.0), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled Binaries for Windows

  • Fulcrum-2.1.3-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, libminiupnpc, Qt 6.10.10, OpenSSL 3.3.0, and gcc 15.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!

Fulcrum 2.1.2

Choose a tag to compare

@cculianu cculianu released this 20 Aug 23:35
6c9f074

What's New:

Fulcrum 2.1.2 is a minor maintenance release of the 2.x series. It contains internal code nits and refactoring and refreshes one of the dependent hash map libraries internally (robin_hood is now updated to ankerl).

Detailed Summary of Changes (vs v2.1.1)

  • Small nit to avoid theoretical but not actual UB in Storace/Compat.cpp
  • Various typo fixups
  • Some nits and fixes for Mempool.cpp and BlockProc.cpp
  • Improved the docker-based static builder to allow for building on arm64 hosts.
  • API nit: Use Util::AsyncOnObject everywhere instead of QTimer::singlShot()
  • Nit in ByteView class; add 'iterator'
  • Remove dead code: CityHash unused code (always compiled out)
  • Some nits and fixups to the bitcoin cash address parser and wrapper class.
  • Some internal API additions to App, BTC::Address, prevector, serializer, and others
  • Replaced the no-longer-supported "robin_hood" flat map with the more modern ankerl (same author, he just renamed the project and internally re-wrote his codebase).

Pre-compiled Binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-2.1.2-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-2.1.2-arm64-linux.tar.gz, which is compiled on an Ubuntu 22.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, libminiupnpc, Qt6Core, Qt6Network (from Qt 6.10.0), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled Binaries for Windows

  • Fulcrum-2.1.2-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, libminiupnpc, Qt 6.10.10, OpenSSL 3.3.0, and gcc 15.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!

Fulcrum 2.1.1

Choose a tag to compare

@cculianu cculianu released this 07 May 23:53
f06d28f

What's New:

Fulcrum 2.1.1 is a bugfix version of the 2.x series. Most significantly, it fixes a bug when using BTC on the Windows version of Fulcrum, where sometimes you can get spammy messages about exhausted Win32 API handles. (See: #324 ). This issue has now been fixed. It also contains other minor nits and fixups and 1 new JSON-RPC protocol method.

Detailed Summary of Changes (vs v2.1.0)

  • Add RPC method: blockchain.address.get_status & blockchain.scripthash.get_status (#316), providing a way to query scripthash status without actually subscribing. Thanks to @mainnet-pat for suggesting this change.
  • Minor nit/tweak to BTC::Address toCScript()
  • Performance: Add ability of CScript to push byte blobs from std::span
  • Internals: Fix isWindows() returning the wrong result on Windows in Common.h
  • PeerMgr: Throttle new connections in process() (fixes issue #324)
  • On unclean shutdown and restart, lower the number of blocks we undo to 1 (was: 6).
  • Fix for compile issue with rocksdb v11 or greater (thus fixing a build issue on latest arch linux).
  • Code nits: Moved the code to figure out rocksdb version into Storage/Compat.cpp
  • Pulled latest changes from BCHN sources for: bitcoin/token.h, plus some code quality tweaks to bitcoin/token.h.

Pre-compiled Binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-2.1.1-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-2.1.1-arm64-linux.tar.gz, which is compiled on an Ubuntu 22.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, libminiupnpc, Qt6Core, Qt6Network (from Qt 6.10.0), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled Binaries for Windows

  • Fulcrum-2.1.1-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, libminiupnpc, Qt 6.10.10, OpenSSL 3.3.0, and gcc 15.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!

Fulcrum 2.1.0

Choose a tag to compare

@cculianu cculianu released this 19 Nov 11:09
ff93ce5

What's New:

Fulcrum 2.1.0 is a minor upgrade version of the 2.x series. Most significantly, it contains support for the new Electrum Cash protocol v1.6 (which has some minor tweaks, mainly for BTC). This release also contains some bugfixes, optimizations and improvements to peering, and some dependent packages were updated for the static build.

Detailed Summary of Changes vs v2.0.0

  • Added support for Electrum Cash protocol v1.6. See: https://electrum-cash-protocol.readthedocs.io/en/latest/protocol-changes.html#version-1-6-0 for differences vs. 1.4 & 1.5.
    • Note: As usual, if the client declares protocol <1.6, nothing changes.
    • This upgrade to the protocol came from the BTC people and mainly concerns BTC. See: spesmilo/electrum-protocol#6
      • Note for BTC admins: If you want to take full advantage of protocol 1.6, please upgrade your node to Bitcoin Core or Bitcoin Knots v28.0.0 or above.
  • Improvements to the logic and code of the PeerMgr which controls peering (federation) behavior of Fulcrum:
    • Fulcrum no longer maintains active connections to all peers in the "Good" list, as it has always done. Instead, it simply disconnects from "Good" peers and periodically reconnects to them to refresh them (every 30 mins).
      • Motivation: The previous behavior of keeping connections alive to all "Good" turned-out to annoy some people, in particular on the BTC mainnet network, because there are so many BTC peers that Fulcrum can eat 200+ connections on any 1 server doing this. See: #307 .
    • Fulcrum tries harder now to reconnect to seemingly-failed peers on their SSL port if their TCP port has failed.
      • Motivation: Many servers declare a TCP port that doesn't work, but their SSL port works ok.
  • Switched all static builds to no longer use the Qt5 series but instead use the Qt6 series, specifically Qt 6.10.0.
    • Motivation: Qt5 is ancient at this point and I don't trust it to not contain dragons and subtle bugs.
  • Static build: Updated miniupnpc to use a custom-patched version. This fixes an esoteric crash bug when using UPnP (--upnp) and when more than 1024 clients are connected.
  • Some code quality / compiler warning fixups for newer GCC, etc.
  • Some updates of the codebase to use more modern C++20 features in many places.
  • Updated servers.json for BCH and BTC.

Pre-compiled Binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-2.1.0-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-2.1.0-arm64-linux.tar.gz, which is compiled on an Ubuntu 22.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, libminiupnpc, Qt6Core, Qt6Network (from Qt 6.10.0), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled Binaries for Windows

  • Fulcrum-2.1.0-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, libminiupnpc, Qt 6.10.10, OpenSSL 3.3.0, and gcc 15.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!


Note: If ugprading from Fulcrum 1.x, please read the below!

Brief Summary: What's New in the 2.x series

A brief summary of what Fulcrum 2.x offers vs the 1.x series:

  • Database Reliability - one of the main weaknesses of Fulcrum 1.x was that should the process be killed at an inopportune time, or should abrupt powerloss or kernel-level crash occur at an inopportune time, there was always a risk that the datadir would get corrupted and the admin would be forced to do a full database resynch. This is no longer the case!
    • Fulcrum 2.x series will no longer suffer from this problem and the process can be killed at any time (including abrupt powerloss), without any database corruption. At worst the last few blocks worth of data is rolled-back and Fulcrum will re-synch from the rollback point.
    • It is still recommended that admins gracefully shut-down Fulcrum, however, via SIGINT/SIGTERM/SIGQUIT (either from their init/systemd scripts or via kill -TERM <pid>, etc), and wait for it to terminate. This maximizes performance and minimizes startup times for Fulcrum the next time it is restarted.
  • Platform Neutrality - database format is now 100% platform-neutral. This means it should be possible to always copy datadirs around regardless if transferring them from Windows, Linux, BSD, macOS, and regardless of platform architecture (including big endian platforms).
  • Improved database performance.

Upgrading from the Fulcrum 1.x Series

Upgrade Instructions

Fulcrum 2.x has a different database format than the 1.x series. As such, you have two options for upgrading:

  • Create a blank new datadir and just re-synch from block 0 (slow, but 100% reliable)
  • Upgrade your existing 1.x datadir (faster, but irreversible and destructice)

To upgade your existing database, be sure to pass the one-time --db-upgrade flag to Fulcrum. It will refuse to start up if it detects that your datadir is in the old format and you did not pass this flag. This ensures that admins know what they are getting into.

Note: The upgrade process takes seconds to minutes on BCH and BTC testnet(s), maybe ~15 minutes on BCH mainnet, and around an hour or more (depending on hardware) on BTC mainnet.

--utxo-cache Removed

The --utxo-cache option has been completely removed. If you want to temporarily leverage memory to help out initial synch, use a temporary --db_mem (CLI) or db_mem= setting in the conf file to give Fulcrum more memory for initial synch, stop Fulcrum, then set it down again to a smaller value for continued operations.

Critical Note On Upgrading the DB from 1.x -> 2.x

Let it run to completion!

While Fulcrum 2.x is 100% reliable and may be killed at any time during its operation -- there is one exception to this rule: the upgrade process that converts 1.x databases -> 2.0. As such please let the upgrade process run to completion and do not kill, stop, molest, or otherwise abuse the Fulcrum process while it's upgrading the DB!!. If you do, the old 1.x database will be lost and your 2.x database will also be corrupted.

You have been warned!


Detailed Summary of Changes in 2.x vs 1.x:

  • Completely redid the database format to leverage rockskdb atomicity and reliability guarantees.
  • Added --db-upgrade CLI arg (required to upgrade an existing DB from Fulcrum 1.x to 2.x format)
  • Added some performance improvements to the rocksdb database
    • Made some tables use point-lookup optimizations
    • Made all tables use 2-level indexing which is more appropriate for the way Fulcrum data is laid out
    • Made some of the tables' keys be properly sorted (such as scripthash_history) -- they were not always completely sorted in an optimal fashion before, which cost a few cycles sometimes.
    • Changes to make better use of db_mem db memory (should also help slightly reduce memory consumption)
    • More forcefully enforce rocksdb kNoCompression for all levels.
  • Made the database format have a specifiec endian-ness for all data and so the database is completely cross-platform. You should now be able to copy any Fulcrum datadir from any OS and architecture to any other OS and architecture, regardless of endianness, word size, etc.
  • Got rid of the entire --utxo-cache mechanism (it's no longer compatible with Fulcrum's newfound data reliability guarantees).
  • db_mem now defauls to 2048 MiB or 25% of total physical memory, whichever is smaller
  • db_max_open_files now defaults to 1000 (was: 40)
  • Internal misc. other performance fixups
  • Internal code quality improvements
  • Removal of some dead/unused code
  • Redid some aspects of the internal unit test system, and added some unit tests
  • Various build system and misc. compile issue fixes

Fulcrum 2.0

Choose a tag to compare

@cculianu cculianu released this 23 Sep 20:55
df51b8a

What's New:

This is a major release of Fulcrum which adds much-needed reliability and performance improvements.

The database format has been completely redone and now Fulcrum provides reliability guarantees such that Fulcrum's db can no longer get corrupted. In other words, you should never see the dreaded "your database is corrupt, please resynch"-style messages, even if Fulcrum is killed at an inopportune time.

Since the database format has been completely redone, the database is no longer backward compatible with older Fulcrum versions, but you can upgrade your existing database to the new format by passing the one-time flag --db-upgrade the first time you run Fulcrum 2.0 when upgrading from a 1.x install.

Brief Summary: What's New in 2.0

A brief summary of what Fulcrum 2.0 offers vs the 1.x series:

  • Database Reliability - one of the main weaknesses of Fulcrum 1.x was that should the process be killed at an inopportune time, or should abrupt powerloss or kernel-level crash occur at an inopportune time, there was always a risk that the datadir would get corrupted and the admin would be forced to do a full database resynch. This is no longer the case!
    • Fulcrum 2.x series will no longer suffer from this problem and the process can be killed at any time (including abrupt powerloss), without any database corruption. At worst the last few blocks worth of data is rolled-back and Fulcrum will re-synch from the rollback point.
    • It is still recommended that admins gracefully shut-down Fulcrum, however, via SIGINT/SIGTERM/SIGQUIT (either from their init/systemd scripts or via kill -TERM <pid>, etc), and wait for it to terminate. This maximizes performance and minimizes startup times for Fulcrum the next time it is restarted.
  • Platform Neutrality - database format is now 100% platform-neutral. This means it should be possible to always copy datadirs around regardless if transferring them from Windows, Linux, BSD, macOS, and regardless of platform architecture (including big endian platforms).
  • Improved database performance.

Upgrading from the Fulcrum 1.x Series

Upgrade Instructions

Fulcrum 2.0 has a different database format than the 1.x series. As such, you have two options for upgrading:

  • Create a blank new datadir and just re-synch from block 0 (slow, but 100% reliable)
  • Upgrade your existing 1.x datadir (faster, but irreversible and destructice)

To upgade your existing database, be sure to pass the one-time --db-upgrade flag to Fulcrum. It will refuse to start up if it detects that your datadir is in the old format and you did not pass this flag. This ensures that admins know what they are getting into.

Note: The upgrade process takes seconds to minutes on BCH and BTC testnet(s), maybe ~15 minutes on BCH mainnet, and around an hour or more (depending on hardware) on BTC mainnet.

--utxo-cache Removed

The --utxo-cache option has been completely removed. If you want to temporarily leverage memory to help out initial synch, use a temporary --db_mem (CLI) or db_mem= setting in the conf file to give Fulcrum more memory for initial synch, stop Fulcrum, then set it down again to a smaller value for continued operations.

Critical Note On Upgrading the DB from 1.x -> 2.0

Let it run to completion!

While Fulcrum 2.0 is 100% reliable and may be killed at any time during its operation -- there is one exception to this rule: the upgrade process that converts 1.x databases -> 2.0. As such please let the upgrade process run to completion and do not kill, stop, molest, or otherwise abuse the Fulcrum process while it's upgrading the DB!!. If you do, the old 1.x database will be lost and your 2.0 database will also be corrupted.

You have been warned!


Detailed Summary of Changes:

  • Completely redid the database format to leverage rockskdb atomicity and reliability guarantees.
  • Added --db-upgrade CLI arg (required to upgrade an existing DB from Fulcrum 1.x to 2.0 format)
  • Added some performance improvements to the rocksdb database
    • Made some tables use point-lookup optimizations
    • Made all tables use 2-level indexing which is more appropriate for the way Fulcrum data is laid out
    • Made some of the tables' keys be properly sorted (such as scripthash_history) -- they were not always completely sorted in an optimal fashion before, which cost a few cycles sometimes.
    • Changes to make better use of db_mem db memory (should also help slightly reduce memory consumption)
    • More forcefully enforce rocksdb kNoCompression for all levels.
  • Made the database format have a specifiec endian-ness for all data and so the database is completely cross-platform. You should now be able to copy any Fulcrum datadir from any OS and architecture to any other OS and architecture, regardless of endianness, word size, etc.
  • Got rid of the entire --utxo-cache mechanism (it's no longer compatible with Fulcrum's newfound data reliability guarantees).
  • db_mem now defauls to 2048 MiB or 25% of total physical memory, whichever is smaller
  • db_max_open_files now defaults to 1000 (was: 40)
  • Internal misc. other performance fixups
  • Internal code quality improvements
  • Removal of some dead/unused code
  • Redid some aspects of the internal unit test system, and added some unit tests
  • Various build system and misc. compile issue fixes

Pre-compiled Binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-2.0.0-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-2.0.0-arm64-linux.tar.gz, which is compiled on an Ubuntu 22.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, libminiupnpc, Qt5Core, Qt5Network (from Qt 5.15.6), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled Binaries for Windows

  • Fulcrum-2.0.0-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, libminiupnpc, Qt 5.15.13, OpenSSL 3.3.0, and gcc 13.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!

Fulcrum 2.0 Pre-Release 1 (Beta)

Pre-release

Choose a tag to compare

@cculianu cculianu released this 19 Sep 18:49
5be20b4

This is a beta test and/or pre-release version of Fulcrum 2.0.

While it has been thoroughly tested by me here on several machines -- and should be very stable -- there have been massive modifications to the database format and/or other Fulcrum internals. As such, it is best if cautious admins don't run this version until it is officially released, and more adventuresome admins that are willing to test beta software do.

Note that, like I said, it should be very stable.

Brief Summary: What's New in 2.0

A brief summary of what Fulcrum 2.0 offers vs the 1.x series:

  • Database Reliability - one of the main weaknesses of Fulcrum 1.x was that should the process be killed at an inopportune time, or should abrupt powerloss or kernel-level crash occur at an inopportune time, there was always a risk that the datadir would get corrupted and the admin would be forced to do a full database resynch. This is no longer the case!
    • Fulcrum 2.x series will no longer suffer from this problem and the process can be killed at any time (including abrupt powerloss), without any database corruption. At worst the last few blocks worth of data is rolled-back and Fulcrum will re-synch from the rollback point.
    • It is still recommended that admins gracefully shut-down Fulcrum, however, via SIGINT/SIGTERM/SIGQUIT (either from their init/systemd scripts or via kill -TERM <pid>, etc), and wait for it to terminate. This maximizes performance and minimizes startup times for Fulcrum the next time it is restarted.
  • Database format is now 100% platform-neutral. This means it should be possible to always copy datadirs around regardless of whether one is transferring them from Windows, Linux, BSD, macOS, and regardless of platform architecture (including big endian platforms).
  • Improved performance.

Upgrading from the Fulcrum 1.x Series

Upgrade Instructions

Fulcrum 2.0 has a different database format than the 1.x series. As such, you have two options for upgrading:

  • Create a blank new datadir and just re-synch from block 0 (slow, but 100% reliable)
  • Upgrade your existing 1.x datadir (faster, but irreversible and destructice)

To upgade your existing database, be sure to pass the one-time --db-upgrade flag to Fulcrum. It will refuse to start up if it detects that your datadir is in the old format and you did not pass this flag. This ensures that admins know what they are getting into.

Note

The --utxo-cache option has been completely removed. If you want to temporarily leverage memory to help out initial synch, use a temporary --db_mem (CLI) or db_mem= setting in the conf file to give Fulcrum more memory for initial synch, stop Fulcrum, then set it down again to a smaller value for operations.

Critical Note On Upgrading the DB from 1.x -> 2.0

Let it run to completion!

While Fulcrum 2.0 is 100% reliable and may be killed at any time during its operation -- there is one exception to this rule: the upgrade process that converts 1.x databases -> 2.0. As such please let the upgrade process run to completion and do not kill, stop, molest, or otherwise abuse the Fulcrum process while it's upgrading the DB!!. If you do, the old 1.x database will be lost and your 2.0 database will also be corrupted.

You have been warned!

Fulcrum 1.12.0

Choose a tag to compare

@cculianu cculianu released this 22 Mar 14:48
7743cca

What's new:

This release of Fulcrum adds UPnP support for Fulcrum. This allows automatic port mapping for installs behind NAT firewalls. Enable with --upnp from the CLI or upnp=true in the conf file. In addition, the bitcoind ZMQ hashtx message is now supported (if configured on the bitcoind side, also needs to be enabled on the Fulcrum side with conf arg: zmq_allow_hashtx=true).

Also included in this release are some mempool-related performance improvements and some internal code quality improvements.


Summary of changes:

  • Added support for UPnP. Requires the libminiupnpc library be detected and linked at compiled-time (this is the case for the released static builds). UPnP is not used by default, but enable it if you are behind a NAT firewall and your router supports UPnP. You can use this new feature to automatically open up any non-loopback ports to the internet for incoming connections. (Enabled with CLI: --upnp/conf file: upnp=1) (#280).
  • Added support for bitcoind's ZMQ pubhashtx message. This means Fulcrum can be instantly-notified when new txn's show up in the bitcoind mempool and as such it should reduce latency for Fulcrum to "see" new mempool txns, at the expense of more CPU utilization. This support is off by default but can be enabled with conf file arg: zmq_allow_hashtx=true (#262).
  • Improved Fulcrum's mempool model efficiency by adding parent/child links for txns (this change makes mempool txn removal faster and as a consequence it makes block processing faster for new blocks being added to the chain tip and being reconciled with the mempool) (#265).
  • Fixed a rare and esoteric bug where Fulcrum would announce its TCP/SSL/WS/WSS port(s) to peers even if it was actually listening on a loopback interface for those ports (thus the announcement was useless and should ideally not show up/be suppressed).
  • Added support for Unix domain sockets in ZeroMQ notifications. (@doitwithnotepad, #267)
  • Assorted code quality/readability/etc improvements.

Pre-compiled binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-1.12.0-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-1.12.0-arm64-linux.tar.gz, which is compiled on an Ubuntu 20.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, libminiupnpc, Qt5Core, Qt5Network (from Qt 5.15.6), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled binaries for Windows

  • Fulcrum-1.12.0-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, libminiupnpc, Qt 5.15.13, OpenSSL 3.3.0, and gcc 13.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!

Fulcrum 1.11.1

Choose a tag to compare

@cculianu cculianu released this 13 Sep 07:20
a1f6a54

What's new:

This is a minor update to Fulcrum. The most significant feature added is support for BTC's new testnet4, which was recently merged into Core master but is as yet unreleased. BCH and LTC users of Fulcrum don't really have a pressing need to upgrade to this release, but are welcome to do so to take advantage of the minor performance fix contained in this release.


Summary of changes:

  • Added BTC testnet4 support (auto-detected) #255. Requires a bitcoin core bitcoind built to support this new chain.
    • There are currently 2 active servers, one Fulcrum, the other ElectrumX that serve blockchain data for testnet4.
  • Slight performance improvement to the UTXO Cache pre-fetcher mechanism
  • Various code quality fixes and nits

Pre-compiled binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-1.11.1-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-1.11.1-arm64-linux.tar.gz, which is compiled on an Ubuntu 20.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, Qt5Core, Qt5Network (from Qt 5.15.6), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled binaries for Windows

  • Fulcrum-1.11.1-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, Qt 5.15.13, OpenSSL 3.3.0, and gcc 13.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!

Fulcrum 1.11.0

Choose a tag to compare

@cculianu cculianu released this 09 Jun 05:33
10623d7

What's new:

This release brings with it performance improvements and an update to the pre-built binary's compiled-in RocksDB version (updated to latest 9.2.1). The latest RocksDB is faster and also better, so yay!

Also in this release we switched the Linux pre-built binary to statically-link libstdc++ which should improve compatibility for the binary and have it "just work" on a wider variety of systems.

NOTE: Since this release contains an updated RocksDB in the release binary, RocksDB will internally "upgrade" the data dir to the newer RocksDB format on first-run (this is fast). However, this means that users that run this version cannot "go back" to the previous Fulcrum versions before 1.11.0 with the same data dir, because RocksDB is backwards compatible but not "forward compatible".


Summary of changes:

  • Rename CLI/conf file option --fast-sync -> --utxo-cache
    • Also renamed various conf file options that contain hyphens in their names (-) to also work with _ instead (e.g. ts-format -> ts_format), so that they can be passed-in from env. vars.
    • Old option names that were renamed still are supported.
  • Switched codebase to use C++20. As a result of this, we also redid the static builds to use newer tools (e.g. gcc 13) and to also statically link libstdc++.
  • Switched pre-built binaries to use newer RocksDB v9.2.1. This breaks "forward compatibility" with previous Fulcrum releases, but should bring in performance and stability improvements from latest RocksDB.
  • Fixes for compatibility between datadirs copied between Windows & Unix (they should all be interoperable now).
  • Updated static pre-built binaries to use latest libzmq and libjemalloc
  • Performance optimizations related to RPA indexing, in particular, testnets as well as low-core-count machines should benefit from the improvements.
  • Controller: Ensure download blocks tasks use all physical CPUs.
  • IPv6: Render ip6:port as [ip6]:port in user-facing strings. Also accept this notation from the conf. file
  • Various fixups related to C++20 in the codebase such as fix some compile warnings, update to newer idioms such as: C++20 concept/requires replaced older std::enable_if, etc.
  • Fix for compiling against Qt 6.7.1
  • Fixed typos in fulcrum-example-config.conf & fulcrum-quick-config.conf
  • RPC: Support downloading of >1GiB blocks from bitcoind (requires Qt6)
  • Fixed assert() in Controller.cpp -- before this fix "Debug" builds were not working with RPA (oops! Fixed!).
  • Refreshed BCH & BTC compiled-in server lists
  • Fix to support BU chipnet (which is reported as "chipnet" rather than "chip" by BU).
  • Added FulcrumAdmin to the dockerhub docker image.
  • Misc. internal code quality nits, tweaks and fixes; various compiler warning fixups

Pre-compiled binaries for Linux

I have provided two pre-built binaries for Linux:

  • Fulcrum-1.11.0-x86_64-linux.tar.gz, which is compiled on an Ubuntu 18.04 system using Docker.
  • Fulcrum-1.11.0-arm64-linux.tar.gz, which is compiled on an Ubuntu 20.04 system (for ARM64 bit) using Docker.

All of the above binaries contain jemalloc, libzmq, Qt5Core, Qt5Network (from Qt 5.15.6), OpenSSL 1.1.1 and libstdc++ statically linked. They still require libz2, and the right libc version as dynamic libs on your system (but those are usually present if you are on a recent system).

Pre-compiled binaries for Windows

  • Fulcrum-1.11.0-win64.zip - Pre-built, statically linked Windows version.
    • It should "just work" on any Windows 10 or above 64-bit system.
    • Includes is a statically-linked Fulcrum.exe, built with jemalloc, libzmq, Qt 5.15.13, OpenSSL 3.3.0, and gcc 13.2.0.
    • Additionally, FulcrumAdmin.exe is included which is the python script, but made into a onefile .exe using PyInstaller.
      • NOTE Windows virus scanners have been known to erroneously identify FulcrumAdmin.exe as containing a virus. This is because many heuristic scanners dislike the use of PyInstaller onefile .exe's. See: #203. Please ignore this -- we contain no viruses! Also please complain to your virus software vendor about this.

See the .asc file for signatures; I signed the sha256 hashes of all the release binaries. My gpg public key can be obtained here: https://github.com/Electron-Cash/keys-n-hashes/blob/master/pubkeys/calinkey.txt


Binary builds for macOS coming soon -- Until then you can always build from source!