Factor Improved Node

This is the last release with the factorn name in the binaries in the code. Future releases will use simply factor. A bug introduced in the last release due to a missing return statement has been fixed, a typo fix for a by-one-error and some updates to the readme.

1629e9fc74e8fe39ac2c3e8bdc3426934dd6c2a5ae707cd44d2dde23f78cb0bd  factorn-cli
eb426b669fd9628f602218fdb0a5f0a4891d66630d2f82ca70c148dcc1995b4b  factornd
13ea866158ac02cfddfd37aa335514bb11bc5399a0f60bee1d28b4d8ac0dc0fe  factorn-tx
751d329dccd7c5ebe33d65a2a23f2846f5bccc55e0916c0ae1f45ec86199ee0a  factorn-util
9b2578d9bf189aa331b213332f1dc8701c7b28d6002f994762b01ec65b410be6  factorn-wallet
763466d134f5bf509ef352f8bbe3ca13faf653db3d51d37930a7bb998bbe0759  test_factorn

Full Changelog: v5.2.69...v5.2.69

Difficulty Mechanism Update

This is a hard fork implemented as a soft-fork. 95% adoption required for activation.

An IFaaS client requested some features be added to our IFaaS service on the blockchain. Research will be conducted to determine the feasibility of adding those features. Homomorphic Encryption will be used for this. In particular, how to claim a bounty in such a way that only the person who placed the bounty can see the result even if its "public" on the blockchain; there are several variations of this situation, but this is the simplest one and is provided here for context of the requested features.

SHA256 hash of the files.

04a6e88c96f2ed64833467ffd6275f812e5f42bbe68b460b95c7bf57d0589044  factorn-cli
4cf11de3d51e7be9e3b5d0a5f31caf787b857201456829fa19d0159d0b67f33c  factornd
0917164869a65ec310ab6559cbc1a264189502110b4ef1b4a1d23742507c1cf0  factorn-tx
76260bcc5c2f0ccd055a49028efe557691ba7ed85f18d202baae6e403314a0d0  factorn-util
5e84d81983a3ede25564aad81001491399d5ae7ab2022276b7b36418c671b6ea  factorn-wallet
41499fcdf96f7d8e763c18d03acf4ead60f60355e186eb4fada14f60a5f785ba  test_factorn

What's Changed

• Define and implement hard diff removal hardfork by @NyanCatTW1 in #41
  Full Changelog: v5.0.70...v5.1.42

v5.0.70 Bug fix (getblocktemplate) .

What's Changed

• Fix deadpool announcement transaction selection + other fixes by @NyanCatTW1 in #39
• depends: boost 1_86_0 by @patricklodder in #40

New Contributors

• @NyanCatTW1 made their first contribution in #39

Full Changelog: v5.0.69...v5.0.70

V5.0.69 Integer Factorization As a Service (aka The Deadpool)

Included in this release are:

1. The deadpool feature. ( Integer-Factorization-As-a-Service, IFAaS)
2. Bitcoin vulnerability patches that apply to Bitcoin v22.0, where we fork from.
3. Several new RPC calls for the deadpool.
4. 100x speedup in loading the node in subsequent node runs after a complete sync for the first time.

Articles about the deadpool feature:

1. Fact0rn's Integer-Factorization As a Service: The Deadpool (https://x.com/FACT0RN/status/1873393861701120300 )
2. Fact0rn's Deadpool RPCs: An introduction ( https://x.com/FACT0RN/status/1874078627421192700 )
3. Fact0rn's Deadpool RPCs: placing and claiming bounties. (https://x.com/FACT0RN/status/1874245689406087267)

Thank you. To everyone who made this possible by dedicating their time and resources to building this. And most importantly, for believing in my ideas.

e8eff8684c19b022c2777e63e481a973a564abe35323133a6068789ba55d15cf factorn-0ef5e69971ad-x86_64-linux-gnu-debug.tar.gz
db995427920f25256798fb935be67678cb8190b6eee5ee32a0a826de66ae1b8e factorn-0ef5e69971ad-x86_64-linux-gnu.tar.gz
4f7b8d0ffb39cfa687b6c65075c52f506093a8ca87a0108f815930060550ea3a SHA256SUMS.part

v4.23.69

This releases fixes a template block bug. There was a logic error in the left shift function of the uint1024 class that only shows up when the difficulty level is +1/+2 more than a multiple of 64. Currently the difficulty is 257. The template block function creates a place holder number of the right expected bitsize for any prime factor that solves the block so that miners are rewarded accordingly after they solve the block. Should this number not have the expected bitsize for any reason, the blockchain will reward zero coins as a defensive mechanism (See #23 ).

The bug was in the left shift operator performed on this place holder number to get the right bitsize. This bug was observed yesterday afternoon, but it began yesterday morning at block height 18144 where the first block of difficulty 257 was mined. The expected prime factor size of 129 for the place holder number was observed to have a value of 193. Here are all the values for which this bug would occur:

 Expected: 1   Actual: 65    <- Below lowest difficulty of mainnet
 Expected: 1   Actual: 65    <- Below lowest difficulty of mainnet
 Expected: 65  Actual: 129   <- Below lowest difficulty of mainnet
 Expected: 65  Actual: 129   <- Below lowest difficulty of mainnet
 Expected: 129 Actual: 193   <- Observed yesterday
 Expected: 129 Actual: 193
 Expected: 193 Actual: 257
 Expected: 193 Actual: 257
 Expected: 257 Actual: 321
 Expected: 257 Actual: 321
 Expected: 321 Actual: 385
 Expected: 321 Actual: 385
 Expected: 385 Actual: 449
 Expected: 385 Actual: 449
 Expected: 449 Actual: 513
 Expected: 449 Actual: 513
 Expected: 513 Actual: 577
 Expected: 513 Actual: 577
 Expected: 577 Actual: 641
 Expected: 577 Actual: 641
 Expected: 641 Actual: 705
 Expected: 641 Actual: 705
 Expected: 705 Actual: 769
 Expected: 705 Actual: 769
 Expected: 769 Actual: 833
 Expected: 769 Actual: 833
 Expected: 833 Actual: 897
 Expected: 833 Actual: 897
 Expected: 897 Actual: 961
 Expected: 897 Actual: 961
 Expected: 961 Actual: 965
 Expected: 961 Actual: 965

This issue has been corrected and tested for all the expected bitsizes at every level. All miners who mine blocks at difficulty level 257 before it gets to 258 will be rewarded the coins they have earned unless they waived this right. So far, the breakdown is as follows:

fact1qrq9jz638mrxlucludwa8jj4rgg0l85au6x0dd8 :  32.89946079258

Sometime next week this wallet (plus any other that show up at this difficulty level affected by this bug), which received 0 coins as rewards, will be rewarded what they should have been rewarded by the system from coins I have mined myself.

Note 1: This will only be done for blocks mined at difficulty level 257 before it gets to 258. You should nonetheless update to the latest node version.

Note 2: For miners who do not update you will continue to receive 0 rewards for difficulty level 258 but will start getting the rewards as they should be beginning on difficulty level 259.

File hashes:

f6b5592e5e98b6bab5d92c31c9f6c8a64cab56cc71455332357cf2fba8778f05  factorn-f597273f3bdc-x86_64-linux-gnu-debug.tar.gz
de8f42d2d481aa3711f4a4e23c17b2c334e4e63ccd2a6be8046d1ffedd6f5bd1  factorn-f597273f3bdc-x86_64-linux-gnu.tar.gz
0b9361d52dcf0d4be791cb8e56deb450861d954b9d4c8f8e5180a6f3e11d3188  SHA256SUMS.part

FACT0RN v4.22.69

The big update here is the fix for the SQLite wallet's key path derivation and the addition of a node. As always, thanks to all the folks who have made this possible. Especial thanks to the person who donated hardware for a node for a full year.

Changes:

• Fixed SQLite wallet key path derivation to be 42069 (https://github.com/satoshilabs/slips/pull/1310/files). Missed it first time around.
• Added new node seed.
• Added checkpoint at height 14000.
• Clang-format pow.cpp and removed unused variable.

a9d46588dbf6fea02dfc138c23e7d6f1ef30ed38c08b822745ae1bc212d09405   factorn-878ad324e33b-x86_64-linux-gnu-debug.tar.gz
724a9cb81e3253a4456d366cb2844dc90b9688a8e6a95356a76eec9433ac3824   factorn-878ad324e33b-x86_64-linux-gnu.tar.gz
561a5056e1d42a73eec4dd4bea4869edd613df7c6f221005e669aa3fff60a176   x86_64-linux-gnu/SHA256SUMS.part

FACT0RN v4.21.69: Chain Restart From Lessons Learned in 24 Hours.

See #19 for lessons learned.

Hashes:

0ff675ce95ce4be8ca7b3696ec15cb618a6b1c3b9e142fe8c86c8dba4a510356  SHA256SUMS.part
8206fb9301a3a5ae9426cc70178bf0a7b7811ceb0e35412b0397253dd3b10424  factorn-437bf800d75d-x86_64-linux-gnu.tar.gz
eb0ffbddf6ff11538e4549e33c98afcd95c934e546092931e04c01aa527e3b79  factorn-437bf800d75d-x86_64-linux-gnu-debug.tar.gz

FACT0RN Launch v4.20.69

FACT0RN introduces factoring integers as a replacement for hashing in Proof-of-Work (PoW). A big and deep thank you to all who have and continue to support me, my crazy ideas and my work.

Some new features will be introduced as we get to them in the form of soft forks. Should any idea merit it hard forks will be considered if the changes will significantly improve the networks' computational efficiency and/or the community deems it necessary.

Happy factoring!