 Show Posts
|
|
Pages: [1] 2 3 »
|
This is my hardware  2 x AMD EPYC 64 cores each 1.5 T RAM -n 0x1000000000000 -k 16384 I think you might be able to squeeze a little bit more speed using -n 0x4000000000000 -k 8192. If you saved your 1TB bloom filter using -S, you can re-use it with the different -n and -k values. You have another 0.5 TB ram available, have you tried -n 0x4000000000000 -k 12000 so you can max out your RAM? Even then, you'll run out of money or die before 135 is found. |
|
|
|
trust me bro  The Bitcoin puzzle could be a CIA honeypot to catch hackers brute-forcing keys. Trust me bro Hmm, I'd say that's highly unlikely. However, it's possible that it's a conglomerate of server-hosting companies. It makes more money than it gives away, I'm certain of that. This might 😅. Create puzzle and make gpu rent servce ? Such a good idea 🙃 Wrote this almost 1 year ago I wouldn't be surprised if the puzzle creator was also the owner or investor vast.ai.
1. Set up GPU renting service that is very good for BTC puzzle solving, and other stuff too like machine learning etc. Requires not much capital to do this. Some servers, software engineers, etc.
2. Start a btc puzzle which you know requires a massive amount of gpu resources, magnitudes of order than whatever you spent on funding the btc puzzles in the first place
3. Find a bunch of hosts with their own gpu rigs/machines they rent out to people trying to solve these crazy puzzles
4. Charge your hosts 25% commission on the fees they earn from renting out their machines on your platform. Remember, you put up no capital at all for all of the hardware, electricity, storage of these very expensive gpu rigs
5. Laugh all the way to the bank for the next several decades or longer
Wish I could have thought of that
|
|
|
|
|
Roughly how long would it take to solve puzzle 135 with 8 x RTX-5090 using RCKangaroo, or something similar?
|
|
|
|
The way 69 was solved still feels suspicious to me, but I haven’t had time to fully investigate.
The finder of 69 decided to start off by scanning every 11th range, beginning with 10000000, then 1000000B, 10000016, 10000021, 1000002C ... kept doing that until while scanning the 175,830th range, found the key in 101D8327. Aware of the risk of broadcasting directly to the mempool, the finder opened up an outdated version of Electrum to craft the transaction which would be sent to Mara Slipstream. A prompt to update Electrum to its newest version appeared, which the finder chose to update, and that "update" was malware that then broadcast a transaction directly to the mempool. Pretty much the same story that happened to one guy in 2020: https://www.coolwallet.io/blogs/blog/1400-bitcoins-btc-stolen-from-an-outdated-electrum-wallet |
|
|
|
Need multiple pubkeys load by file and search...
Why I never add a list of targets in any of my apps ? I have a list of about 1000 public keys. All are above 2BTC  You should add Satoshi's 34k public keys to your list, each one with 50BTC. Maybe someone can calculate how many RTX-5090's you'd need to crack just one of those wallets in 24 hours?  https://bitcoin.oni.su/satoshi_public_keys/34K_2009_50.html |
|
|
|
For all the prefix people, I found these. HEX Decimal Address H160
1154CCBF7A8E9B19F5 319705118580596742645 19vkiEajfho62cVxE3R3wivybRRtKt9RW3 61EB8A50C86B02D483247F3B1BB9F755AF42F595
1163A1676EF65022F5 320773782260344169205 19vkiEajfhwvzzTeAZ1q8uZvgcQdzGtpS6 61EB8A50C86B0681AFCAD8F56DF969B7E1263285
138730FAC832E011B7 360229699132237812151 19vkiEajfhDY2ZnjKANWyFM7P3tAvDtzAz 61EB8A50C86AF4E2175D5457091F70CEA754DC8B
138F7C0E525C61AD45 360827291991917309253 19vkiEajfhREjN9kbfLEky7yWXLPvJJHMo 61EB8A50C86AF9BF574CB5C599A6EFA23FC531B9
1393282966BD3D1380 361091908244363613056 19vkiEajfhrHfSABZF92u4MMKBcJXfRq3s 61EB8A50C86B04291AFED3DE34084A271CC75749
1393283E97485C7F8D 361091931542600318861 19vkiEajfhHUS1SnHGY3Qy738NLPsnnZLf 61EB8A50C86AF68527C633D33486658E3CDE9BBA
16F80BAB573D337528 423701937558937367848 19vkiEajfhxLcT6TvwMLwvTCdPZgVGgKNY 61EB8A50C86B06AD01F1B450703B1F15A6F621EF
16F935E0D179D2F244 423785875901116510788 19vkiEajfhaiqD9xo4kksNMAWJbXi9VTxH 61EB8A50C86AFDB0A3253B382E60E71264D16BF5
1731880A5C5928CB7A 427844227791759919994 19vkiEajfhgVqSvSGPxChSEHNC9sj6Nso3 61EB8A50C86B0017490D78C6B576DD57488E0824
17353DBA52F00471D3 428111541018286125523 19vkiEajfhi9pMP9v4vtttK8BtkwqLjafX 61EB8A50C86B00C762F2651A575C9ACDD552FA41
1737C3370BE4A1E636 428293229512084284982 19vkiEajfhJw2Fq21uXVgrom56rz3eiusg 61EB8A50C86AF7205B8A95C5EBCF5E27743AC4AA
1763DBA723550745E5 431470642295166420453 19vkiEajfhUQshinAktSdQpgSJZcDvwK2M 61EB8A50C86AFB1132C915827AA6FC6EFA468A17
176973534AE4643614 431873622272748303892 19vkiEajfhYCuAK3WD8Lt2iA89oqNdkRZo 61EB8A50C86AFCA4E399FA755D5E84B62F2DFC35
1772135EF22291F338 432495131834256061240 19vkiEajfhdmDPYo7JCktYiLLjr6EXZVij 61EB8A50C86AFEF441293B67FDFC47336F38A5B6
17724AFA4320DAF4A7 432510783730141033639 19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiS 61EB8A50C86B027FAB6396B89DD3098DF212756B
17724F1F4C6A6B6752 432511950351867012946 19vkiEajfhs3KBqvZ2Rg9q2HqoJoU6cVqv 61EB8A50C86B047931A23FE63F530497A09FCBEC
1772513996EF5A0D7A 432512542209180568954 19vkiEajfhqSoL2Em8tjDikiizHvfEwkKD 61EB8A50C86B03CF73D881A7538C570AF83B2B4C
17741661AB270C0457 432640094440929363031 19vkiEajfhdyGj7sVP9uiK5uFB25P7D76T 61EB8A50C86AFF0A6088ABA861BDA16754D19E18
1774C3D566860AAE42 432688916860490133058 19vkiEajfhCKvYXsyNasbLit68d7HXv3wq 61EB8A50C86AF46177EAA4601BE1B76521107EE7
1775CF3EF478D259C1 432764186737656355265 19vkiEajfhSccouvafPu7EjJTjnM7CmwYh 61EB8A50C86AFA51E9D8F024BE2F5AC8256C4E33
18FF0C40A2F61344D1 461099993017078727889 19vkiEajfhroTfr8pYUYw6gFoEhZvJathE 61EB8A50C86B045FC697B90EDDDA96CC43FD813E
19170258BF723DFD83 462826587034843217283 19vkiEajfhgpgBGd2rH3CKYEW6gyfQpK6a 61EB8A50C86B0039DA32911101D584602491B5AF
1917047641DBEA705A 462827182430752501850 19vkiEajfhMWvT19gHtXfHFEgrHhBqSv7a 61EB8A50C86AF83362D58545CB6642BE49B9AFBF
191AA0DF9C6169E70A 463087381146740844298 19vkiEajfh45w3gbSESgoAxAAKANjujCPX 61EB8A50C86AF0F4798C5F63CEBB7D0C08B63F82
191B87C398558AA3DB 463152371062656377819 19vkiEajfhdSnETiLsrKZdwVDZDFNBgCrg 61EB8A50C86AFED26EEB2DB8A220DB0559D33897
1AA842CA1E2B7EE96A 491739821294210705770 19vkiEajfhTs1KLh7dEugXg7Jded3NjHnk 61EB8A50C86AFAD6BA30DDA11F4E12D60DF92B34
1B93E3F633F4DF594C 508718721836458662220 19vkiEajfhPJdWaJgiPQBiCrigbxQHzphB 61EB8A50C86AF8F1A9FE39739243677920E34EA2
1B94576788D9C7B643 508751216068212012611 19vkiEajfhSurPzkC94gq1No9dmx4YUeW1 61EB8A50C86AFA7188B4B7F2DB8976411474CEC9
1B945B8B3872FAEEF5 508752381205215375093 19vkiEajfhcKrFbaP9rtzVffAAHSNq3eok 61EB8A50C86AFE5B4D43930E62A8F5D47E4F4928
1B9875B6858F6FB3B4 509047977540951454644 19vkiEajfhCa9oMk6tbjJ6YAuhvsq3pNNL 61EB8A50C86AF47B92FFF260AF619F7030794845
1B9879DA20A615A252 509049142589865173586 19vkiEajfh9EBTHLMVistknEBBxZb4kBeM 61EB8A50C86AF317AF786DD8B89D956A67F048E6
1B9BD6B1A6CA4D3D1F 509291448040969551135 19vkiEajfhPNBwBHvqV7paNjzf1vzmsuPJ 61EB8A50C86AF8F831A8334932D7EC08AE69F797
1BB457575848064F61 511057041276635860833 19vkiEajfhKpQNib7DcSJkMB7K8fiDKUCm 61EB8A50C86AF77EA1220931D1D43ED06866E077
1BC5B9916D40CC58F3 512309668784745765107 19vkiEajfh4yDtURYZnQoR7NhPqBN53pBU 61EB8A50C86AF1529466B119B23B7CF5B8B51611
1BC96F4198EFDEB313 512576982239311475475 19vkiEajfhn8Pb6bdjnfGxXQwFqBuy2kMu 61EB8A50C86B026E6E0FE7866D732FED5C9398E1
Obviously this is just a tiny fraction of prefixes, I only scanned 0.0022% of the keyspace. But sort the decimal differences between them and you get 23298236705805
591857313556008
595395909284567
1165048913718942
1165137003362482
1166621725979307
15651895884972399
28260317185531498
32494231753350391
48822419560770027
64989915915533521
75269877166222207
83938342179142940
99291914563262579
181688493798159459
242305451104377549
260198715988342448
264616252446303803
267313226526205529
267313454565710368
295596335736079551
301804398966676909
319705162541080439
402979977581883439
597592859679497102
1068663679747426560
1252627508109904274
1726594017764489394
1765593235666309698
3177412783082135471
4058351890643409206
16978900542247956450
28335806279422372624
28587450231554327951
39455916871893642946
62610006016337048987
Patterns/coincidences? |
|
|
|
|
Nice to see the bots battling it out for 69.
Did anyone even get close? I scanned 101C76FE and 101E4D0B...
|
|
|
|
The pubkey is there so the private key can be found in a few seconds.
How? 000000000000000000000000000000000000000000000017724AFA4320DAF4A7 He assumed the address was within 69. Good morning, but how did you get the private key for address 19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiS, having only the public key? Correct, I made the assumption that the private key for that wallet was in range 69. Since that address has 1 outgoing transaction, it's public key is shown. I ran RCKangaroo with the public key and got the hex private key under 5 seconds, with an RTX4070. $ time ./rckangaroo -dp 14 -range 68 -start 100000000000000000 -pubkey 03f5c18f93f837065c3673b64f0426d08283d5097c54c465af92a399a017ddebc7
********************************************************************************
* RCKangaroo v3.0 (c) 2024 RetiredCoder *
********************************************************************************
This software is free and open-source: https://github.com/RetiredC
It demonstrates fast GPU implementation of SOTA Kangaroo method for solving ECDLP
Linux version
CUDA devices: 1, CUDA driver/runtime: 12.7/12.8
GPU 0: NVIDIA GeForce RTX 4070, 11.99 GB, 46 CUs, cap 8.9, PCI 1, L2 size: 36864 KB
Total GPUs for work: 1
MAIN MODE
Solving public key
X: F5C18F93F837065C3673B64F0426D08283D5097C54C465AF92A399A017DDEBC7
Y: 0C5EBEFBB70A7D8F266754279ECF093963B644D47C49B09B9D4107A051660F27
Offset: 0000000000000000000000000000000000000000000000100000000000000000
Solving point: Range 68 bits, DP 14, start...
SOTA method, estimated ops: 2^34.202, RAM for DPs: 0.232 GB. DP and GPU overheads not included!
Estimated DPs per kangaroo: 4.267. DP overhead is big, use less DP value if possible!
GPU 0: allocated 868 MB, 282624 kangaroos. OldGpuMode: No
GPUs started...
Stopping work ...
Point solved, K: 0.757 (with DP and GPU overheads)
PRIVATE KEY: 000000000000000000000000000000000000000000000017724AFA4320DAF4A7
real 0m4.444s
user 0m2.720s
sys 0m1.805s |
|
|
|
I found this exact prefix '19vkiEajfhu' within the 69-bit range, but from what I've read from more knowledgeable people on the forum, it may not have much significance idk. I'm just a hobbyist  You need to prove the 19vkiEajfhu prefix you found. Otherwise, you won't be listened to much.  Edit; After scanning 9000 trillion keys for the actual address (the good hash) of Puzzle 69, there was still no 53 bits or larger prefix found.
61eb8a50c86b0584bb727dd65bed8d2400d6d5aa H160 - Is the first 61eb8a50c86b0 the one you mentioned as 53 bits? If that's what you mean, I have it. Freebie for all you prefix hunters. While you guys were scanning hundreds of trillions of keys for a 53 bit prefix match, I found one using grep on the Loyce Club All BTC addresses list. Used by someone on Nov 20, 2024, a few days after 66 was solved. The pubkey is there so the private key can be found in a few seconds. https://mempool.space/address/19vkiEajfhnHnZjGpogP6Rv8sUQFvF7PiSNewbie Disclaimer: This information is for entertainment purposes only, and cannot and will not aid you in your search for the prize, no matter how strongly you believe so. |
|
|
|
The puzzles had stalled because of the bots, but once it was made public Mara via Wp, the search resumed. So, it was just a matter of low time.
I think they stalled because, computational power was too slow and expensive for the puzzle rewards, given that they were 1/10th of what they are now. And the BTC price was much lower as well, so anyone going after the unsolved puzzles would spend magnitudes of order more money than what the puzzle rewards were worth at the time. After the unsolved puzzle rewards became 10x and the price of BTC price went way up, and GPU's became much faster and cheaper to rent, it was now possible to solve a puzzle and come out ahead. Didn't have anything to do with bots, they have been around since the early days of Bitcoin. Nothing to do with MARA either, they just started their Slipstream service not very long ago. Based on some quick math, puzzle 68 got solved after scanning 18-20% of the keyspace! Let's see if Bram will share this info with us later. |
|
|
|
|
Grats!
Closest I got was:
BEB4F17D7F675DD5C 1MVDYgVaSNXtr34anQEPicNVrSnyUdNpAA
BEB4F2D9F65D87F04 1MVDYgVaSNMpE4wHjAYS7UqhBs9wKLwg1p
Since those two were so close together, I was searching the keyspace around those, but got beat to it!
I bet Bram will go on to solve all of the remaining puzzles, lol.
|
|
|
|
Actually is there a fully random scanning software for GPU ? Tools like keyhunt cuda or rotor they are not fully random...
What do you understand by "fully random scanning"? I hope it's not "hey, let's test a new random key at every step" lol. That would be dumb to do. I mean fully random within range - not pseudorandom or rekey every x mkeys. If you've got idle CPU's... root@C.18837889:~/keyhunt$ ./keyhunt -m address -b 68 -l compress -s 10 -t 196 -n 0x10000 -f tests/68.txt -R
[+] Version 0.2.230519 Satoshi Quest, developed by AlbertoBSD
[+] Mode address
[+] Search compress only
[+] Stats output every 10 seconds
[+] Threads : 196
[+] Random mode
[+] Setting search for btc adddress
[+] N = 0x10000
[+] Bit Range 68
[+] -- from : 0x80000000000000000
[+] -- to : 0x100000000000000000
[+] Allocating memory for 1 elements: 0.00 MB
[+] Bloom filter for 1 elements.
[+] Loading data to the bloomfilter total: 0.03 MB
[+] Sorting data ... done! 1 values were loaded and sorted
Base key: b0f4506ed92386fc5 Total 50727256064 keys in 120 seconds: ~422 Mkeys/s (422727133 keys/s) |
|
|
|
|
Feb 27 2025
Puzzle 68 progress
Bram: 3% scanned
btc-hunters 0.11% scanned
btcpuzzle: 0.10% scanned
ttdpool: 0.04% scanned
|
|
|
|
Guys, stop trying to pressure the solver into doing anything. If you're nice, maybe he will stay and you can learn something from him.
We are all grateful for WP's post, sharing a method to securely withdraw a puzzle prize. Nobody is obligated to tip anyone just because you used MARA. You can always show your appreciation for what you've learned by directly sending a tip yourself.
It is not about a donation; that is up to each person if they feel like donating or not. It is more about valuing the contributions and not undermining them. He talks as if it were a 100% original milestone. It is obvious that his solution is just a method already exposed here, and its only advantage was great computing power. So, unless it is something else, the answer is simple: he has nothing to teach us that we do not already know. From what he says, random method with thousands of GPUs are things we already know. I suppose the most he could have added to the software is a database that records already scanned sectors to skip them later. Did you read his methodology? It wasn't only random scanning and lots of GPU's. The method was: Break up puzzle 67's keyspace into 256 sub-ranges each with 2^58 keys In each sub range, save every private key that generates an address starting with 48 zero's Statistically there are 1024 proofs in each subrange If an average of 1024 proofs are found in a sub-range, it statistically guarantees the whole sub-range has been scanned What software are you talking about? He used custom software. I'm sure he'd like to keep his competitive advantage to himself.
It was found after scanning 57% of the keyspace in 67 days. Which works out to over 7 trillion keys per second. Which, my napkin math says is around 1600 x RTX4090's.
Several thousand
Pretty close. Would need more than 1600 GPU's if they were not all RTX-4090s. And right now, ~4 days and 2 hours since puzzle 67 was solved, assuming the same scanning speed, he's already scanned almost 2% of puzzle 68. |
|
|
|
Guys, stop trying to pressure the solver into doing anything. If you're nice, maybe he will stay and you can learn something from him. We are all grateful for WP's post, sharing a method to securely withdraw a puzzle prize. Nobody is obligated to tip anyone just because you used MARA. You can always show your appreciation for what you've learned by directly sending a tip yourself. Over the past few months, despite multiple tests of the reliability of MARA's service being successful in safely transferring funds from one wallet to another, people repeatedly continued to cast doubt about MARA. Everything from them having "rogue" employees to hackers having SSH backdoor access to MARA. That was all just a bunch of nonsense. MARA is a publicly traded US company, listed on the NASDAQ stock exchange, with a real board of directors, accountable to their shareholders and clients, and probably with US regulators breathing down their necks, making sure they comply with demands from the SEC, IRS, OFAC, and various law enforcement agencies. There has not been a single instance of a transaction submitted to MARA's Slipstream service being compromised in any way. So give them some credit. Not too long ago, I used MARA to send my own bitcoin to perhaps the most compromised wallet in the universe (hex private key 0000000000000000000000000000000000000000000000000000000000000001, WIF: KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qYjgd9M7rFU73sVHnoWn, compressed address 1BgGZ9tcN4rm9KBzDn7KprQz87SZ26SAMH) and then successfully sent it back to myself. I even enabled RBF for both transactions. Any bitcoin that is normally sent to this address gets instantly snatched up by bots. If MARA was compromised in any way, bots would have stolen my coins. But that didn't happen. Tx from me to address #1: https://mempool.space/tx/bab4b7409ee1955bda0e20e6777ebc9d108a38a987f234e99b97cc0c7c97a019Tx from address #1 back to me: https://mempool.space/tx/52a62d981c3ca21af5529eaed25599e515c2d5f26a549448e1743b966995df59 |
|
|
|
It seems that the solvers do not disclose the paths they followed, especially for searching addresses without exposed public keys, thus the "Large Bitcoin Collider" does not maintain its course. Nowadays, we only see developers omitting to share their information, as the current era is all about criticizing everything, being rude, and unproductive. Each time, the end draws closer, the day when this post will be buried forever. However, I keep hope in those closed circles, where the few members have a respectful approach to sharing ideas.
They did share how 67 was solved. Even shared their proof of work. Just do a little research It was found after scanning 57% of the keyspace in 67 days. Which works out to over 7 trillion keys per second. Which, my napkin math says is around 1600 x RTX4090's. If you haven't noticed, its pretty much impossible to buy a 5090 right now. Maybe that's why. |
|
|
|
Puzzle: 67 Solved as we know:
1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9
Private Key = 00000000000000000000000000000000000000000000000730fc235c1942c1ae
Something to note for another Address with private key next to puzzle 67:
Address nearly next to puzzle 67's private key:
1NpqfKpfpRHajrXKV4FEj7zCheYirjZV8j
Private Key = 00000000000000000000000000000000000000000000000730fc235c1942c1b4
Do you think someone was testing out MARA or something on this address next to the puzzle first before attempting the puzzle 67's sweep?
Interesting find. But no, this wallet was first used 2 days after 67 was found, and wasn't mined by Mara. Probably just someone messing around or doing some other testing. |
|
|
|
|
Well, 67 was just solved.
730fc235c1942c1ae
|
|
|
|
Imagine a big bag full of green beans and only one red bean (the private key we're looking for).
Interesting thought experiment. I did some calculations to help visualize the size of puzzle 67's keyspace. There are 73786976294838206464 possible keys in puzzle 67. Some may look at the number "73786976294838206464" or at the hex range of 40000000000000000:7FFFFFFFFFFFFFFFF and think, well that number doesn't really look that big. Now let's take a look at the Great Pyramid of Giza, in Egypt. It is the largest pyramid in Egypt, with an original height of around 146.6 meters (480.6 feet) and a base length of about 230.4 meters (756 feet) on each side. Next, imagine you have 73786976294838206463 grains of just average, white, sand, and just 1 grain of black sand (representing all of puzzle 67's possible keys, and the 1 private key). You would fill the volume of the Great Pyramid of Giza with sand ~370 times. Try to picture 370 of these pyramids, all of white sand, and inside one of them somewhere is 1 individual grain of black sand. If you took a typical US 5 Gallon bucket, and could check 1 bucket per second, looking for that 1 black grain of sand (and hopefully not miss it), that's about 1.5 billion grains of sand per second. It would take you 1560 years to check all of the sand, assuming you were checking nonstop, 24/7/365. Maybe a little bit longer, if you took a few breaks to eat some yogurt. |
|
|
|
Hello friends, Based on what I have followed and read, I have not found any safe and guaranteed solution for withdrawing funds from any wallet whose private key has been solved. I kindly ask you, my friends, to share with us what you believe to be the best and safest way to withdraw funds and manage them later in case any puzzle is solved. It is extremely disheartening for someone to exhaust their energy, resources, and intelligence to solve a puzzle, only for their efforts to be stolen in the blink of an eye. I believe such an experience would leave someone in lifelong shock.   This has been exhaustively discussed in the previous pages of this this forum thread, but to sum it all up: There is no guaranteed way to withdraw the funds, given that the private key is low entropy. Your best interest would be to not participate, quit while you still can, abandon ship. Would you work a job where you had to show up every day, putting in all of your energy and resources and intelligence into the job for every shift, day after day, week after week, month after month, perhaps even years, with no guarantee that when the job is actually done, that you might or might not finally get paid? Hope that answers your question. On the day that puzzle 66 was solved, bitcoin's price was $58,000. Today it's $102,000. If you want to get rich quick, just buy some bitcoin. If you want to become poor quick, keep searching for the keys to the puzzle wallets |
|
|
|
|
