Old Dip Tracker

Closing this as the security policy has been on `master` for a while now.

> The error happens at a different block every time here is an example output. I have tried deleting and reinstalling everything, different networks, even a hardwired connection. The most...

> I do not want to degrade my disk! Repetitive writes will degrade any disk, so restarting the indexer over and over is not recommendable. > [120GB] should be close...

I have not been able to reproduce but I'd like to keep this open to further investigate the high write volume. I've seen several mentions of this since 1.10.0, so...

> It's not the project's issue. High write volume is something we should be able to work on.

What are the benefits?

`estimatefee` works for me - this was fixed in 1.14.7 (and everyone should really be on 1.14.9 right now) - but please do file an issue if this is not...

I was able to reproduce the issue from #3673 on FreeBSD 14.1 and boost 1.85 using the `qcow2` distributed file. Tested with: ```bash ./configure --without-gui --enable-c++17 \ BDB_LIBS="-L/usr/local/lib/db5 -ldb_cxx-5.3" \...

> I'm leery of reversing the check order because we're vulnerable to any other third-party include changing its own check order. Yes, or add `sys/endian.h` regardless of `endian.h` presence -...

I dug a bit and found that [this is what boost does](https://github.com/boostorg/predef/blob/9aca7f5b609a731106a6d70e8dca9a4196dca968/include/boost/predef/other/endian.h#L57-L67). In short: ```cobol if gnu or android or openbsd then endian.h else if macOS then machine/endian.h else if...