Author

Topic: Armory 0.96.5 on Ubuntu 18.04: can't use Bitcoin Core 28.0+ (Read 43 times)

legendary
Activity: 3766
Merit: 1364
Armory Developer
Quote

Per Bitcoin Core 28.0 release notes (verified the hard way!):

The minimum required glibc to run Bitcoin Core is now 2.31.
This means that RHEL 8 and Ubuntu 18.04 (Bionic) are no-longer supported. (#29987)

I'm guessing they want C++17 features, seeing as they're dropping boost along the way. There may be a backport of a more modern GCC for ubuntu18 (I think it's on GCC8, there may be up to GCC11 for it). You can always check the backport repo I guess.

Quote
The XOR pattern is only applied when the blocksdir is freshly created,

...all is well! Just can't run 28+

You can, as nc50lc has noted. You'd have to set --blocksxor=0 in your bitcoin.conf file.
legendary
Activity: 2534
Merit: 6080
Self-proclaimed Genius
For others who prefer the latest release version, there's still a way:
Add a blocksxor=0 line to bitcoin.conf file or use it as a command line arg: --blocksxor=0

Of course, it should be done before attempting IBD else the change in setting will be detected
and Core will prompt the user that it can't be disabled (without generating a new blocksdir).
els
jr. member
Activity: 41
Merit: 0
If I am not mistaken, Ubuntu 18.04 is the latest LTS that Armory 0.96.5 can reasonably run on.

Per Bitcoin Core 28.0 release notes (verified the hard way!):

The minimum required glibc to run Bitcoin Core is now 2.31.
This means that RHEL 8 and Ubuntu 18.04 (Bionic) are no-longer supported. (#29987)

Unfortunately I'd updated my blockchain on an Ubuntu 24.04 system (with Bitcoin Core 28.0) before moving it to my Ubuntu 18.04 instance.

I am the process of figuring out how to down-rev Bitcoin Core to 27.2 (with minimal reprocess of blockchain data) but I am curious if anybody has any better & practical resolutions for this situation.

Thanks!
--els


UPDATE:

In my case, down-rev to Bitcoin Core 27.2 was effortless. Just ran the v27.2 bitcoind with the existing ~/.bitcoin in place. Although 28.0 release notes also mention:

Block files are now XOR'd by default with a key stored in the blocksdir. Previous releases of Bitcoin Core or previous external software will not be able to read the blocksdir with a non-zero XOR-key. Refer to the -blocksxor help for more details. (#28052)

Since my blocksdir was NOT freshly created by 28.0 and per #28052:

The XOR pattern is only applied when the blocksdir is freshly created,

...all is well! Just can't run 28+
Jump to: