Search content
Sort by
Showing 20 of 369 results by zahid888
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
what is the most basic puzzle i can start with?
You can start with 71, but please be aware that ALL PUZZLES UNTIL ABOUT 86-87 SHOULD BE WITHDRAWN WITHOUT USING PUBLIC BTC MEMPOOL. USE SLIPSTREAM SERVICE OF MARA POOL TO WITHDRAW SUCCESSFULLY.
And what's the plan for your $100 challenge? Gonna play it with MaraPool's slipstream, or rolling the dice with a regular mempool transaction?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
And this is not so powerful CPU Ryzen 7 5800H
I recently forked your Cyclone and added a couple of tweaks Now with -bit and -subzeros for Fine-Grained Private Key Range Control.
-bit – lets you select the bit length for the random private key range (e.g. -bit 71)
-subzeros – lets you define how many trailing hex characters (zeroes) the range should have.
Code:
-bit 71 -subzeros 8
This will generate a key range like:
Code:
4ec00159ac00000000 : 4ec00159acffffffff
You can adjust the number of zeroes based on your CPU thread count and brute-force capability.
I’m planning to build or buy a more powerful CPU setup (under $2k), and I’d love some suggestions from the community on CPUs with strong multi-core performance suitable for this kind of workload.
Any recommendations are appreciated!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
the key was found after 0.7206% of the range.
So someone solved puzzle 69 using a modified Cyclone in 20 days?
Try your luck:)
With a small tweak 😉. I'm still a bit confused about how the jump function works, so I avoided using it. Interestingly, it seems to take the same amount of time with or without it.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Seems like another stolen reward.
The original TX: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827
Which was replaced by: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827 ($1000 in fees)
And that was replaced again by: https://mempool.space/tx/6102b9d3c9a8e40c16ef6eab8c5c8a6819ffac8fc0d22fc850c674863ae5e65c ($1120 in fees)
And again: https://mempool.space/tx/a52c5046f3097a8c2bd3b9889df2fb47b104d47a16cc679d3357feec003db753 ($1130 in fees using Binance pool)
The original TX: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827
Which was replaced by: https://mempool.space/tx/65f5f2c358651ee12c983051423f9925e1339b8ef52b93e23943e26e80609827 ($1000 in fees)
And that was replaced again by: https://mempool.space/tx/6102b9d3c9a8e40c16ef6eab8c5c8a6819ffac8fc0d22fc850c674863ae5e65c ($1120 in fees)
And again: https://mempool.space/tx/a52c5046f3097a8c2bd3b9889df2fb47b104d47a16cc679d3357feec003db753 ($1130 in fees using Binance pool)
It’s hard to believe people are still making such mistakes. I honestly feel terrible for that guy.
For all the prefix people, I found these.
Code:
19vkiEajfho62cVxE3R3wivybRRtKt9RW3 61eb8a50c86b02d483247f3b1bb9f755af42f595 1154CCBF7A8E9B19F5 b8b33164
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhwvzzTeAZ1q8uZvgcQdzGtpS6 61eb8a50c86b0681afcad8f56df969b7e1263285 1163A1676EF65022F5 91093953
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^^^ ^ ^ ^ ^
19vkiEajfhDY2ZnjKANWyFM7P3tAvDtzAz 61eb8a50c86af4e2175d5457091f70cea754dc8b 138730FAC832E011B7 5103a1df
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^
19vkiEajfhREjN9kbfLEky7yWXLPvJJHMo 61eb8a50c86af9bf574cb5c599a6efa23fc531b9 138F7C0E525C61AD45 80449cce
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^
19vkiEajfhrHfSABZF92u4MMKBcJXfRq3s 61eb8a50c86b04291afed3de34084a271cc75749 1393282966BD3D1380 3ba07c06
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhHUS1SnHGY3Qy738NLPsnnZLf 61eb8a50c86af68527c633d33486658e3cde9bba 1393283E97485C7F8D b0211b0c
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^ ^ ^ ^^
19vkiEajfhxLcT6TvwMLwvTCdPZgVGgKNY 61eb8a50c86b06ad01f1b450703b1f15a6f621ef 16F80BAB573D337528 c6421cb1
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^^^ ^ ^ ^ ^ ^ ^ ^
19vkiEajfhaiqD9xo4kksNMAWJbXi9VTxH 61eb8a50c86afdb0a3253b382e60e71264d16bf5 16F935E0D179D2F244 6750152e
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^
19vkiEajfhgVqSvSGPxChSEHNC9sj6Nso3 61eb8a50c86b0017490d78c6b576dd57488e0824 1731880A5C5928CB7A c1e61fce
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^^^ ^ ^ ^ ^ ^ ^ ^
19vkiEajfhi9pMP9v4vtttK8BtkwqLjafX 61eb8a50c86b00c762f2651a575c9acdd552fa41 17353DBA52F00471D3 3822d31e
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^^^ ^ ^ ^ ^ ^ ^
19vkiEajfhJw2Fq21uXVgrom56rz3eiusg 61eb8a50c86af7205b8a95c5ebcf5e27743ac4aa 1737C3370BE4A1E636 51973983
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^ ^^^^^^^^^^^ ^ ^ ^ ^^ ^ ^ ^
19vkiEajfhUQshinAktSdQpgSJZcDvwK2M 61eb8a50c86afb1132c915827aa6fc6efa468a17 1763DBA723550745E5 e1c132d6
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^ ^ ^ ^
19vkiEajfhYCuAK3WD8Lt2iA89oqNdkRZo 61eb8a50c86afca4e399fa755d5e84b62f2dfc35 176973534AE4643614 29a98ce6
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhdmDPYo7JCktYiLLjr6EXZVij 61eb8a50c86afef441293b67fdfc47336f38a5b6 1772135EF22291F338 0ac33d24
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiS 61eb8a50c86b027fab6396b89dd3098df212756b 17724AFA4320DAF4A7 afb4346b
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhs3KBqvZ2Rg9q2HqoJoU6cVqv 61eb8a50c86b047931a23fe63f530497a09fcbec 17724F1F4C6A6B6752 a2efdfad
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^^^ ^ ^ ^ ^
19vkiEajfhqSoL2Em8tjDikiizHvfEwkKD 61eb8a50c86b03cf73d881a7538c570af83b2b4c 1772513996EF5A0D7A cdcebf6c
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^^^ ^ ^ ^^
19vkiEajfhdyGj7sVP9uiK5uFB25P7D76T 61eb8a50c86aff0a6088aba861bda16754d19e18 17741661AB270C0457 8dff9d94
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhCKvYXsyNasbLit68d7HXv3wq 61eb8a50c86af46177eaa4601be1b76521107ee7 1774C3D566860AAE42 23abbf5c
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^^ ^ ^ ^
19vkiEajfhSccouvafPu7EjJTjnM7CmwYh 61eb8a50c86afa51e9d8f024be2f5ac8256c4e33 1775CF3EF478D259C1 82544496
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^
19vkiEajfhroTfr8pYUYw6gFoEhZvJathE 61eb8a50c86b045fc697b90eddda96cc43fd813e 18FF0C40A2F61344D1 1b5d63a1
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^ ^ ^^^^^^^^^^^^^ ^
19vkiEajfhgpgBGd2rH3CKYEW6gyfQpK6a 61eb8a50c86b0039da32911101d584602491b5af 19170258BF723DFD83 815957d3
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^^^ ^ ^ ^^ ^ ^ ^ ^
19vkiEajfhMWvT19gHtXfHFEgrHhBqSv7a 61eb8a50c86af83362d58545cb6642be49b9afbf 1917047641DBEA705A 99f10019
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfh45w3gbSESgoAxAAKANjujCPX 61eb8a50c86af0f4798c5f63cebb7d0c08b63f82 191AA0DF9C6169E70A d9343d76
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^ ^ ^ ^ ^ ^
19vkiEajfhdSnETiLsrKZdwVDZDFNBgCrg 61eb8a50c86afed26eeb2db8a220db0559d33897 191B87C398558AA3DB 6f0c6e25
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhTs1KLh7dEugXg7Jded3NjHnk 61eb8a50c86afad6ba30dda11f4e12d60df92b34 1AA842CA1E2B7EE96A 4010f83d
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^ ^ ^ ^ ^
19vkiEajfhPJdWaJgiPQBiCrigbxQHzphB 61eb8a50c86af8f1a9fe39739243677920e34ea2 1B93E3F633F4DF594C 7e9061be
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^ ^^^^^^^^^^^ ^ ^ ^ ^ ^ ^
19vkiEajfhSurPzkC94gq1No9dmx4YUeW1 61eb8a50c86afa7188b4b7f2db8976411474cec9 1B94576788D9C7B643 53dbde8e
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^
19vkiEajfhcKrFbaP9rtzVffAAHSNq3eok 61eb8a50c86afe5b4d43930e62a8f5d47e4f4928 1B945B8B3872FAEEF5 7e1dfd7b
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhCa9oMk6tbjJ6YAuhvsq3pNNL 61eb8a50c86af47b92fff260af619f7030794845 1B9875B6858F6FB3B4 f43b2f41
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^ ^ ^ ^
19vkiEajfh9EBTHLMVistknEBBxZb4kBeM 61eb8a50c86af317af786dd8b89d956a67f048e6 1B9879DA20A615A252 cd571a86
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^^ ^ ^ ^^
19vkiEajfhPNBwBHvqV7paNjzf1vzmsuPJ 61eb8a50c86af8f831a8334932d7ec08ae69f797 1B9BD6B1A6CA4D3D1F 8ea756cd
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^
19vkiEajfhKpQNib7DcSJkMB7K8fiDKUCm 61eb8a50c86af77ea1220931d1d43ed06866e077 1BB457575848064F61 e8a5cca6
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^ ^^
19vkiEajfh4yDtURYZnQoR7NhPqBN53pBU 61eb8a50c86af1529466b119b23b7cf5b8b51611 1BC5B9916D40CC58F3 fb0ebb2b
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^ ^ ^ ^
19vkiEajfhn8Pb6bdjnfGxXQwFqBuy2kMu 61eb8a50c86b026e6e0fe7866d732fed5c9398e1 1BC96F4198EFDEB313 a9b53070
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^ ^^^^^^^^^^^^^ ^ ^
19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiS 61eb8a50c86b027fab6396b89dd3098df212756b 17724AFA4320DAF4A7 afb4346b
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^ ^^^^^^^^^^^^^ ^ ^ ^ ^ ^
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG 61eb8a50c86b0584bb727dd65bed8d2400d6d5aa 101D83275FB2BC7E0C cd3204bb
19vkiEajfhuZ8bs8Zu2jgmC6oqZbWqhxhG_61eb8a50c86b0584bb727dd65bed8d2400d6d5aa_101D83275FB2BC7E0C_cd3204bb
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^ ^^^^^^^^
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Hahaha, take it easy... It’s not that simple... But... Every member in this topic will get 0.2 BTC—if they have a BTC address in their signature. Satisfied? 
Are you talking about that key?
Code:
KyDi5tDzUCEN5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tFNbmN45bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tJzYm5M5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk1GeGqp5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk2nLZCk5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk377UHr5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L2Die4KeEMng5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L3DiBgEqot9K5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
That’s probably a scam. I’ve bunch of WIFs with partial matches in sequence, be careful not to waste your time there.
For those who think searching for WIF has some magical twist—let me tell you, it's much slower compared to generating an address directly from a private key (hex, bytes or dec).
@nomachine, maybe let the curious minds DM you directly -: this thread’s starting to feel like a rerun marathon.
Let’s save the scrolls for fresh stuff!-- Sim results
If you sum the number of checks over 10k simulations you get this :
Code:
=== FINAL RESULTS ===
Sequential: 495816995
Prefix: 496059807
WHICH IS ALMOST 50-50!
And maybe I have conducted the most experiments on prefixes, whether it be in the form of base58 or hash160.
Through these experiments, I have consistently encountered a 50-50 probability of outcomes.
Through these experiments, I have consistently encountered a 50-50 probability of outcomes.
but the basic aspect has already been demonstrated, which was the probabilistic success rate.
Well done! But let’s be real—if we’re talking probabilities, I Still remember, how you got yourself stuck in this argument when you trying to defend someone. Your heroic moment, huh? Maybe now’s a good time to snap out of that mess and chase some actual probability breakthroughs.
=== Configuration ===
Total numbers: 2,097,152
Block size: 4,096
Prefix: 3 characters (16^3 combinations)
Simulations: 10000
=== FINAL RESULTS ===
Wins:
Sequential: 3736 (Average Win Margin: 42.57%)
Prefix: 6244 (Average Win Margin: 36.55%)
Ties: 20
Total Checks:
Sequential: 10,472,126,509
Prefix: 10,548,477,557
Total numbers: 2,097,152
Block size: 4,096
Prefix: 3 characters (16^3 combinations)
Simulations: 10000
=== FINAL RESULTS ===
Wins:
Sequential: 3736 (Average Win Margin: 42.57%)
Prefix: 6244 (Average Win Margin: 36.55%)
Ties: 20
Total Checks:
Sequential: 10,472,126,509
Prefix: 10,548,477,557
Bro demonstration is over now! lets reduce the talk in this forum that we can easily read important posts
And thanks for searching all 10 digit seeds for me 
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
It doesn't use my cores. I only have 4% out of 100!!!
(4% out of 100%)
, may i know how many core you have ?The modification I suggested, which limits the multiprocessing.Pool to 60 workers, was necessary to avoid the ValueError: need at most 63 handles caused by the Windows API’s limitation of 63 simultaneous processes.
Try this:
Code:
with multiprocessing.Pool(min(cpu_count, cpu_count - 2), initializer=init_globals,
initargs=(shared_counter, shared_found_counter, total_seeds)) as pool:
initargs=(shared_counter, shared_found_counter, total_seeds)) as pool:
Or try experimenting with a smaller chunk size, like 1 million or 100,000, to see if it improves utilization,, Smaller chunks allow more frequent task distribution to workers, which can help keep all cores busy
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Exception in thread Thread-1 (_handle_workers):
Traceback (most recent call last):
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "\Python\Python311\Lib\threading.py", line 1045, in _bootstrap_inner
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 self.run()
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "\Python\Python311\Lib\threading.py", line 982, in run
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 self._target(*self._args, **self._kwargs)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "Python\Python311\Lib\multiprocessing\pool.py", line 522, in _handle_workers
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 cls._wait_for_updates(current_sentinels, change_notifier)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "rograms\Python\Python311\Lib\multiprocessing\pool.py", line 502, in _wait_for_updates
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 wait(sentinels, timeout=timeout)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "ograms\Python\Python311\Lib\multiprocessing\connection.py", line 896, in wait
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 ready_handles = _exhaustive_wait(waithandle_to_obj.keys(), timeout)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "ms\Python\Python311\Lib\multiprocessing\connection.py", line 828, in _exhaustive_wait
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 res = _winapi.WaitForMultipleObjects(L, False, timeout)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0ValueError: need at most 63 handles, got a sequence of length 74
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 1
Traceback (most recent call last):
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "\Python\Python311\Lib\threading.py", line 1045, in _bootstrap_inner
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 self.run()
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "\Python\Python311\Lib\threading.py", line 982, in run
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 self._target(*self._args, **self._kwargs)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "Python\Python311\Lib\multiprocessing\pool.py", line 522, in _handle_workers
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 cls._wait_for_updates(current_sentinels, change_notifier)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "rograms\Python\Python311\Lib\multiprocessing\pool.py", line 502, in _wait_for_updates
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 wait(sentinels, timeout=timeout)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "ograms\Python\Python311\Lib\multiprocessing\connection.py", line 896, in wait
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 ready_handles = _exhaustive_wait(waithandle_to_obj.keys(), timeout)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 File "ms\Python\Python311\Lib\multiprocessing\connection.py", line 828, in _exhaustive_wait
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 res = _winapi.WaitForMultipleObjects(L, False, timeout)
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 0ValueError: need at most 63 handles, got a sequence of length 74
Progress: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0.00% | Found_Seed: 1
ValueError: need at most 63 handles, got a sequence of length 74 on Windows systems with high core counts due to a limitation in the Windows, which can handle only 63 processes at a time. To resolve this, I recommend modifying the line that initializes the multiprocessing.Pool to limit the number of worker processes.
Modified Line :
Code:
with multiprocessing.Pool(min(cpu_count, 60), initializer=init_globals,
initargs=(shared_counter, shared_found_counter, total_seeds)) as pool:
initargs=(shared_counter, shared_found_counter, total_seeds)) as pool:
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Hey everyone, If you have a high-core CPU (e.g., 16 cores or more), could you kindly run this script for me and send me back the generated found_seeds.txt file?.. Thanks
Code:
import random
import multiprocessing
import sys
# Shared counter and total for progress
counter = None
found_counter = None
total = None
def init_globals(shared_counter, shared_found_counter, total_count):
global counter, found_counter, total
counter = shared_counter
found_counter = shared_found_counter
total = total_count
def check_seed(a):
random.seed(a)
b = random.randrange(2**31, 2**32)
target_values = {
int('b862a62e', 16), int('9de820a7', 16), int('e9ae4933', 16),
int('e02b35a3', 16), int('ade6d7ce', 16), int('efae164c', 16),
int('9d18b63a', 16), int('fc07a182', 16), int('f7051f27', 16),
int('bebb3940', 16)}
match = b in target_values
if match:
with found_counter.get_lock():
found_counter.value += 1
with open("found_seeds.txt", "a") as f:
f.write(f"seed: {a} - FOUND! {hex(b)}\n")
with counter.get_lock():
counter.value += 1
percent = counter.value / total
bar_length = 30
filled = int(bar_length * percent)
bar = '█' * filled + '░' * (bar_length - filled)
print(f"\rProgress: [{bar}] {percent * 100:.2f}% | Found_Seed: {found_counter.value}", end='', flush=True)
def chunked_range(start, end, chunk_size):
for i in range(start, end, chunk_size):
yield range(i, min(i + chunk_size, end))
if __name__ == '__main__':
start = 1706200000
end = 10_000_000_000
chunk_size = 100_000_0
cpu_count = multiprocessing.cpu_count()
total_seeds = end - start
shared_counter = multiprocessing.Value('i', 0)
shared_found_counter = multiprocessing.Value('i', 0)
with multiprocessing.Pool(cpu_count, initializer=init_globals,
initargs=(shared_counter, shared_found_counter, total_seeds)) as pool:
for subrange in chunked_range(start, end, chunk_size):
pool.map(check_seed, subrange)
print(input("\nDone."))
import multiprocessing
import sys
# Shared counter and total for progress
counter = None
found_counter = None
total = None
def init_globals(shared_counter, shared_found_counter, total_count):
global counter, found_counter, total
counter = shared_counter
found_counter = shared_found_counter
total = total_count
def check_seed(a):
random.seed(a)
b = random.randrange(2**31, 2**32)
target_values = {
int('b862a62e', 16), int('9de820a7', 16), int('e9ae4933', 16),
int('e02b35a3', 16), int('ade6d7ce', 16), int('efae164c', 16),
int('9d18b63a', 16), int('fc07a182', 16), int('f7051f27', 16),
int('bebb3940', 16)}
match = b in target_values
if match:
with found_counter.get_lock():
found_counter.value += 1
with open("found_seeds.txt", "a") as f:
f.write(f"seed: {a} - FOUND! {hex(b)}\n")
with counter.get_lock():
counter.value += 1
percent = counter.value / total
bar_length = 30
filled = int(bar_length * percent)
bar = '█' * filled + '░' * (bar_length - filled)
print(f"\rProgress: [{bar}] {percent * 100:.2f}% | Found_Seed: {found_counter.value}", end='', flush=True)
def chunked_range(start, end, chunk_size):
for i in range(start, end, chunk_size):
yield range(i, min(i + chunk_size, end))
if __name__ == '__main__':
start = 1706200000
end = 10_000_000_000
chunk_size = 100_000_0
cpu_count = multiprocessing.cpu_count()
total_seeds = end - start
shared_counter = multiprocessing.Value('i', 0)
shared_found_counter = multiprocessing.Value('i', 0)
with multiprocessing.Pool(cpu_count, initializer=init_globals,
initargs=(shared_counter, shared_found_counter, total_seeds)) as pool:
for subrange in chunked_range(start, end, chunk_size):
pool.map(check_seed, subrange)
print(input("\nDone."))
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Right now I am doing GPU Cyclone version, it has hashing and comparing to target hash160, on rtx 4060 it has 4.3 Ghash/s, that faster than bitcrack, vanity, etc.
Hey, I’ve got the SHA-256 part nailed down in sha256_gpu.cu, but I’m hitting a wall with RIPEMD-160 in ripemd160_gpu.cu.
Right now, my RIPEMD-160 code outputs 499d42dd5724b7522a1c4bd895876e1232957cbe for SHA-256("abc"), but it should be 8eb208f7e05d987a9b044a8e98c6b087f15a0bfc. I’ve been digging into BitCrack’s ripemd160.cuh for clues—tweaking byte orders and round functions—but I’m still stuck.
Would you be willing to share how you’ve implemented RIPEMD-160 in CUDA? I’d love to see a working ripemd160_gpu.cu
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Can I use it ? Encrypted or Normal doesn't matter!
or Normal doesn't matter!Lol.. No worries — I’ll be posting the clean version with source code on GitHub soon. After all, the puzzle journey has already come to an end.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Where to rent CPU ?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Doubts about what ?
My Honest Doubts About the Puzzle Solutions – A Response to @Bram24732’s Claims on Puzzle #67 and #68
In recent weeks, the Bitcoin puzzle-solving community has been buzzing about @Bram24732 — the individual who claims to have solved Puzzle #67 and #68 back to back in just 67 days for #P67 and 46 days for #P68, using 2,000+ GPUs. Now, he's also encouraging others to join a crowd-funded GPU pool, claiming that even higher puzzles can be cracked this way.
Let’s entertain this hypothesis:
The puzzles were originally created by someone with long-term foresight and significant resources.
That person seeded the puzzles with real Bitcoin, perhaps as a clever marketing stunt or social experiment.
Years later, that same person (or group) resurfaces, pretending to “solve” the harder puzzles, when in reality they are simply revealing private keys they already have.
Why?..........
............. To build credibility — and convince the community to join their GPU crowd-fund effort.The crowd-fund ends up renting vast GPU fleets, possibly tied to their own interests or hardware partners — all while not actually scanning the keyspace, but instead using pre-held keys to simulate “success.”
Could This Be a Hidden Marketing Tactic?
This could be a strategic move by:
A GPU manufacturer trying to drive demand for high-end cards
A mining hardware reseller(ETH shifted to staking
)Or simply the original puzzle creator who now wants to profit from the community's belief that these puzzles can be cracked with brute force.
Why We Should Be Skeptical
Solving Puzzle 67 in 67 days is mathematically implausible with 2,000 GPUs.
Solving Puzzle 68 just days later makes it even less believable.
Pushing for crowd-funding and renting GPUs after these “successes” looks like a classic setup:
First, show fake success → then sell the dream → finally monetize the crowd’s hope.
@Bram24732 You openly asked the community to share any doubts, and I’m simply responding with an honest, analytical perspective based on the facts and numbers available.These questions and theories are already circulating within the community, and rather than letting them grow in silence, I believe it's better to express them openly and constructively.
Regards:
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Congratulations!! @Bram24732 for Puzzle 68!
Huge respect for cracking it—amazing work!
To the entire community: as we all know, there are no magic tricks, shortcuts, or secret exploits here. It’s now clear that pure brute force is the only way forward.
With that in mind, it feels like the puzzle journey has reached its end for many of us. Competing against someone with over 2,000+ powerful GPUs (and counting!) just isn't realistic.
Still, it’s been an incredible ride. Much love to everyone who participated, explored, shared ideas, and pushed the limits.
#Puzzle68 #EndOfTheJourney #RespectTheGrind
Huge respect for cracking it—amazing work!
To the entire community: as we all know, there are no magic tricks, shortcuts, or secret exploits here. It’s now clear that pure brute force is the only way forward.
With that in mind, it feels like the puzzle journey has reached its end for many of us. Competing against someone with over 2,000+ powerful GPUs (and counting!) just isn't realistic.
Still, it’s been an incredible ride. Much love to everyone who participated, explored, shared ideas, and pushed the limits.
#Puzzle68 #EndOfTheJourney #RespectTheGrind
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
GPU-accelerated version will be available soon, with multi-GPU support for enhanced performance!
This fresh repository is built from the ground up, under a new license, terms, and policies.
Expect a more user-friendly interface and an easy-to-use experience!
No source code will be provided. Encrypted functions are enabled, and decryption access is available only upon request.
I’m not here to hold anyone’s hand — either you use it, or you don’t. Simple! If you’re not interested, feel free to move on and add me in your ignore list.
Supports Both CPU & GPU Users – Choose what works best for you.
Before using, make sure to read the terms and policy. Don’t come asking later!
Take it or leave it – your choice!
A huge thank you to those who patiently helped me understand my mistakes and guided me toward moving forward the right way, legally and ethically.
I also want to sincerely apologize for any harsh language I may have used. If my words hurt anyone, please know it was never my intention. I truly regret it.
Kind regards
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
snip
It is possible to upload executables (.exe) to GitHub (closed source) if they are 100% your own work. Encrypting the private key (pk) also infringes the license because, in a way, you are indirectly profiting from it. In short, if all the code were yours, you could do it without any problem. However, if you include third-party code or libraries, check their licenses to understand what you can and cannot do.Thanks.. that is what i want to know... you are saying that if i wrote 100% of the code myself, then i could legally upload an .exe and even encrypt private keys function. However, if i used third-party code or libraries, i need to follow their license terms.
I understand your point. I did write the majority of the code from scratch, but I used several dependencies and repositories from him for faster address generation, such as
"sha256_avx2.h", "ripemd160_avx2.h" and "SECP256K1.h"... etc, The rest of the code is entirely mine.
Given this, what would be the proper way to proceed? Should I remove the repository entirely, or is there a way to comply with the license while keeping my work available?
You just need to make the repository private, remove the .exe file, and rebuild from scratch the files that are not part of your audit. After all, what truly matters is the logic, and ideas like "sha256_avx2.h," "ripemd160_avx2.h," and "SECP256K1.h" are not protected by patents safeguarding their logic. Simply rewrite anything protected based on your understanding of the idea and in accordance with the licenses. Some of these may simply require proper attribution to use without modification, depending on the license terms. However, another option would be to give up and simply delete everything, as the culture of donations has practically disappeared (99% dead), leaving only criticism alive.
I understand your point, and I appreciate the guidance. Making the repository private, removing the .exe, and rewriting the necessary parts is something I can consider.
But honestly, it’s disheartening. The fact that the culture of donations is '99% dead' while only criticism thrives speaks volumes about how things have changed. Maybe that’s what pushed me toward the encryption function in the first place—though I now realize it was the wrong approach.
At this point, deleting everything might be the only real option. There’s no point in dragging this conversation any further. Let’s just end it here.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
snip
It is possible to upload executables (.exe) to GitHub (closed source) if they are 100% your own work. Encrypting the private key (pk) also infringes the license because, in a way, you are indirectly profiting from it. In short, if all the code were yours, you could do it without any problem. However, if you include third-party code or libraries, check their licenses to understand what you can and cannot do.That is what i want to know... you are saying that if i wrote 100% of the code myself, then i could legally upload an .exe and even encrypt private keys function. However, if i used third-party code or libraries, i need to follow their license terms.
I understand your point. I did write the majority of the code from scratch, but I used several dependencies and repositories from him for faster address generation, such as
"sha256_avx2.h", "ripemd160_avx2.h" and "SECP256K1.h"... etc, The rest of the code is entirely mine.
Given this, what would be the proper way to proceed? Should I remove the repository entirely, or is there a way to comply with the license while keeping my work available?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
And before some random keyboard warrior jumps in with their detective skills, let me make one thing crystal clear—there’s no source code available for any of them. So, if you have a problem with that… well, you know what? F*ck off! 
I hope you're aware you are breaking the GPL license of the JLP projects, making your software illegal to distribute in binary form.
In short, you're the one who should f*ck off, since you have a problem with intellectual property.
https://www.gnu.org/licenses/gpl-faq.html#ModifiedJustBinary
Quote
Can I release a modified version of a GPL-covered program in binary form only? (#ModifiedJustBinary)
No. The whole point of the GPL is that all modified versions must be free software—which means, in particular, that the source code of the modified version is available to the users.
No. The whole point of the GPL is that all modified versions must be free software—which means, in particular, that the source code of the modified version is available to the users.
Seriously, I had no idea about this. I honestly don’t know what I’m doing wrong legally, what the consequences are, and how I can correct it. As a long-time member of this community, I genuinely want to fix my mistake—so if I’m in the wrong, I’d appreciate some guidance.
Is it really unfair to upload only .exe files on GitHub? I’ve seen many repositories without source code, and I’ve even used some of them myself. Also, is it wrong to encrypt private keys for solved puzzles as a way to earn a small reward for the effort we put in? just help me understand the right way to go about this.
Man, it's a bit contradictory to ask for free help and then try to monetise what's been openly shared. The whole point of public repositories is collaboration and transparency. If you're thinking about encrypting private keys or keeping only executables private for profit, you might want to rethink your approach. Open source communities thrive on trust and the sharing of knowledge for the common good, and monetising that in a closed way can really go against the spirit of things. Perhaps try to find a balance or explore ways to give back before turning things into a money-making scheme.
f*ck of these puzzles........ Years of hard work, countless sleepless nights... and what did I get? Not success, not respect—just legal troubles and a whole lot of stress. Truly living the dream!......... Built castles in the air for years, only to be handed a demolition notice.
And you call this an open-source program? What do you say about that—is it fair enough?
I just saw this in the original Git repository from the Cyclone author:
This code sets up the necessary includes for network programming. With these headers, you can create programs that send and receive data over a network using sockets.
What is the purpose of this setup? Is it for sending keys over a network or something else?
Code:
#ifdef _WIN32
#include <windows.h>
#include <winsock2.h>
#include <ws2tcpip.h>
#pragma comment(lib, "ws2_32.lib")
#define close closesocket
#else
#include <unistd.h>
#include <arpa/inet.h>
#include <sys/socket.h>
#endif
#include <windows.h>
#include <winsock2.h>
#include <ws2tcpip.h>
#pragma comment(lib, "ws2_32.lib")
#define close closesocket
#else
#include <unistd.h>
#include <arpa/inet.h>
#include <sys/socket.h>
#endif
This code sets up the necessary includes for network programming. With these headers, you can create programs that send and receive data over a network using sockets.
What is the purpose of this setup? Is it for sending keys over a network or something else?
I don’t know… We will see.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
And before some random keyboard warrior jumps in with their detective skills, let me make one thing crystal clear—there’s no source code available for any of them. So, if you have a problem with that… well, you know what? F*ck off!
I hope you're aware you are breaking the GPL license of the JLP projects, making your software illegal to distribute in binary form.
In short, you're the one who should f*ck off, since you have a problem with intellectual property.
https://www.gnu.org/licenses/gpl-faq.html#ModifiedJustBinary
Quote
Can I release a modified version of a GPL-covered program in binary form only? (#ModifiedJustBinary)
No. The whole point of the GPL is that all modified versions must be free software—which means, in particular, that the source code of the modified version is available to the users.
No. The whole point of the GPL is that all modified versions must be free software—which means, in particular, that the source code of the modified version is available to the users.
Seriously, I had no idea about this. I honestly don’t know what I’m doing wrong legally, what the consequences are, and how I can correct it. As a long-time member of this community, I genuinely want to fix my mistake—so if I’m in the wrong, I’d appreciate some guidance.
Is it really unfair to upload only .exe files on GitHub? I’ve seen many repositories without source code, and I’ve even used some of them myself. Also, is it wrong to encrypt private keys for solved puzzles as a way to earn a small reward for the effort we put in? just help me understand the right way to go about this.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I already mentioned this on GitHub, and today I Gonna revealing it but i am too late. I sincerely apologize for not disclosing it from day one.
There’s just one thing I did—if a full match is found, you receive an encrypted private key that requires a password to decrypt. In return for providing the password, I only ask for a small appreciation fee. Is that really unfair? You guys can tell me. Many kind-hearted people would definitely share something, but not everyone does.
From my experience, once people succeed, many forget everyone who helped them along the way. They don’t mention you in their success, and that’s just the reality. Still, I truly apologize if this has broken anyone’s trust. It’s not about deception—it’s about the hard work we put in, only to end up with nothing when the final moment arrives. #WP
You’re free to use it if you like, or let me know what I should do. Should I just delete my repo?
There’s just one thing I did—if a full match is found, you receive an encrypted private key that requires a password to decrypt. In return for providing the password, I only ask for a small appreciation fee. Is that really unfair? You guys can tell me. Many kind-hearted people would definitely share something, but not everyone does.
From my experience, once people succeed, many forget everyone who helped them along the way. They don’t mention you in their success, and that’s just the reality. Still, I truly apologize if this has broken anyone’s trust. It’s not about deception—it’s about the hard work we put in, only to end up with nothing when the final moment arrives. #WP
You’re free to use it if you like, or let me know what I should do. Should I just delete my repo?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
In this benchmark, you get an average of 4 Mkeys/s per core, possibly because this version uses a fully random approach, which impacts the speed.
The biggest performance gain comes from generating eight random numbers simultaneously using AVX-512.
Code:
__m512i randVec = _mm512_set_epi64x(rng1, rng2, rng3, rng4, rng5, rng6, rng7, rng8);
Of course, I won't publicly disclose the exact details of how this works.
You know what? My system said, 'Let’s try it!'
… And guess what? It’s running absolutely fine. But me? I’m the one getting hanged multiple times while playing around with Cyclone. 
Forked this repo 4 times, applied my 4 favorite logics, and everything is working perfectly!
In these processes, I faced tons of bugs, challenges, endless AI conversations, and way too many forum posts—seriously, that stuff sucked the life out of me!
One of my forks includes stride logic—I saw you mention somewhere that stride doesn’t work properly above 32-bit or something like that… Well, My stride version is unlimited and working flawlessly with zero issues.
Anyway… no more stress—I’m just gonna chill now. And as you said, I’m off for some fishing too!
Oh, and just a heads-up—soon, all 4 forks will be available on GitHub, so get ready because you guys are gonna love this!
And before some random keyboard warrior jumps in with their detective skills, let me make one thing crystal clear—there’s no source code available for any of them. So, if you have a problem with that… well, you know what? F*ck off!
If you wanna use it, great! If not, here’s a complimentary finger from my side.
/"\
|\./|
| |
| |
| |
| |
/'\| |/'\
/'\| | | |
| | | | |\
| | | | | \
| * * * * |> > ALL YOURS!
| /
| /
| /
\ |
| |
I ain’t your babysitter, and I definitely don’t have time to argue with those saying, 'OMG, you put viruses in your .exe!' or 'You're trying to steal our few satoshis from our wallet!' 🤦♂️ Bruh… take it or leave it—I’m just here having fun!
Best Wishes to Every One