Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 51. (Read 245154 times)
No attacks here, just lonely elliptic curves in a world that never understood them. 😢
chatGPT bab, then talk about brute or secp246k1, not answer about attack....
unless it's bragging about how 'brute' it is! 😜 But don't worry, no attacks here
I am sure many of us have read the exact same ChatGPT answer
Yes, hahaha! I even have version 3.0 of the puzzle exponential prediction script created by ChatGPT. That silicon brain even suggested I try a magic circle with colors in Python. I think 90% of the ideas here came from ChatGPT.
chatGPT bab, then talk about brute or secp246k1, not answer about attack....
I am sure many of us have read the exact same ChatGPT answer
Yes, hahaha! I even have version 3.0 of the puzzle exponential prediction script created by ChatGPT. That silicon brain even suggested I try a magic circle with colors in Python. I think 90% of the ideas here came from ChatGPT.
Someone has to sit down and write a completely new kangaroo.
Shouldn't we be looking at FPGAs by now?
I'm actually working on a little project to get me started with Verilog.
It is a simple xpoint-only bruteforcer for now. The design works fine, but I couldn't fit it on the target chip yet.
The main goal is to get to the level where I can create a HDL Kangaroo implementation as there are none out there.
You can check with monitoring tools on your system OS.
Yes exactly. It's not worth it.. Someone has to sit down and write a completely new kangaroo.
Just to be quick so it's not too late.
Interesting find! It seems the private keys for these addresses are likely generated using a deterministic formula based on a sequence number. The increasing decimal values you've observed (3, 7, 8, 21...) suggest a simple mathematical progression.
Here's what I can analyze:
The pattern seems to be an increasing sequence, possibly exponential.
The provided examples show a clear relationship between the address number and the private key value.
Unfortunately, without knowing the exact formula or a starting point, it's difficult to predict the private keys for addresses 15 and beyond.
Here's what I can analyze:
The pattern seems to be an increasing sequence, possibly exponential.
The provided examples show a clear relationship between the address number and the private key value.
Unfortunately, without knowing the exact formula or a starting point, it's difficult to predict the private keys for addresses 15 and beyond.
If you think there's a simple mathematical pattern, you should team up with the guy who's trying to solve it with Photoshop charts and have digiran oversee you both. I am sure many of us have read the exact same ChatGPT answer, typed verbatim:
Quote
The pattern seems to be an increasing sequence, possibly exponential.
The provided examples show a clear relationship between the address number and the private key value.
Unfortunately, without knowing the exact formula or a starting point, it's difficult to predict the private keys for addresses 15 and beyond.
The provided examples show a clear relationship between the address number and the private key value.
Unfortunately, without knowing the exact formula or a starting point, it's difficult to predict the private keys for addresses 15 and beyond.
lmao you didn't analyze squat.
Interesting find! It seems the private keys for these addresses are likely generated using a deterministic formula based on a sequence number. The increasing decimal values you've observed (3, 7, 8, 21...) suggest a simple mathematical progression.
Here's what I can analyze:
The pattern seems to be an increasing sequence, possibly exponential.
The provided examples show a clear relationship between the address number and the private key value.
Unfortunately, without knowing the exact formula or a starting point, it's difficult to predict the private keys for addresses 15 and beyond.
Here's what I can analyze:
The pattern seems to be an increasing sequence, possibly exponential.
The provided examples show a clear relationship between the address number and the private key value.
Unfortunately, without knowing the exact formula or a starting point, it's difficult to predict the private keys for addresses 15 and beyond.
yeah, I already looked at all the diffs (git diff with git-delta) so you see it like shown on your screenshots. Very neat tool to get the data displayed in linux CLI. However the program does not work as intended, GPU is not utilized at all, only CPU works. The performance counter (rate) shows unreliable and unrealistic high values (trillions and billions of MKeys/sec) depending on the grid size you choose. But most important part is that the GPU is not utilized at all. You can check with monitoring tools on your system OS.
sad we cannot see the diff to JLP's original kangaroo tool. Anyone dived into mikorists' code and can share some thoughts about the changes and implementation routines ?
I didn't have time to go through all the files, but I did go through the SECPK1 folder. Everything has been changed to work for 256bit if the CPU is used. Looking at the counter this version is about 15-20% faster than the original in CPU mode. I didn't look at how the GPU is used. This is a mixed code between ZenulAbidin & AlbertTajuelo. There is nothing new here.
120, 125 and 130.
captured by hacker ? because this address is 1DiegoU6ETJXK9hNWVTeuK4Y8fkksPnEnK seem fishy with 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs
and he's announce this "https://www.blockchain.com/explorer/transactions/btc/69888f5e55d414b8de65f3a9307a1f414d7035cf9142239045300ce018984bd4"
the next target to take and spend.
{
"address": "1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9",
"pkscript": "76a914739437bb3dd6d1983e66629c5f08c70e5276937188ac",
"value": 1231,
"spent": false,
"spender": null
},
it's 67, anyone who can find even 67, the transactions will be attacked by this person.
ngl, this guy very smart and genius build the transaction and from the number of transactions increasing slowly and rhythmically.
captured by hacker ? because this address is 1DiegoU6ETJXK9hNWVTeuK4Y8fkksPnEnK seem fishy with 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs
and he's announce this "https://www.blockchain.com/explorer/transactions/btc/69888f5e55d414b8de65f3a9307a1f414d7035cf9142239045300ce018984bd4"
the next target to take and spend.
{
"address": "1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9",
"pkscript": "76a914739437bb3dd6d1983e66629c5f08c70e5276937188ac",
"value": 1231,
"spent": false,
"spender": null
},
it's 67, anyone who can find even 67, the transactions will be attacked by this person.
ngl, this guy very smart and genius build the transaction and from the number of transactions increasing slowly and rhythmically.
You are right about the attack. However about 3Emi, I do not think so, that transaction you shared does not belong to 3Emi, it belongs to a lamer, a noob, a very beginner who does not know anything.
And for you guys, I shared in older posts a script where you can immediately move BTC from one wallet to another. Use those kind of proper and reliable script to move when you solve any puzzle. Also, move whole balance all in once, because while waiting small amount of transfer to be moved (testing if btc is going), hackers start slowing and solves the private key from the exposed public key in 4-5 minutes for the small numbers like the puzzle #67.
python scans 50,000 addresses per second
Just to add... Rust is about 10-15 times faster than python, depending on which Crates are used on which hardware and how it is compiled. So for those who don't have a GPU, they also have a solution together with standard C++ scripts.
120, 125 and 130.
captured by hacker ? because this address is 1DiegoU6ETJXK9hNWVTeuK4Y8fkksPnEnK seem fishy with 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs
and he's announce this "https://www.blockchain.com/explorer/transactions/btc/69888f5e55d414b8de65f3a9307a1f414d7035cf9142239045300ce018984bd4"
the next target to take and spend.
{
"address": "1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9",
"pkscript": "76a914739437bb3dd6d1983e66629c5f08c70e5276937188ac",
"value": 1231,
"spent": false,
"spender": null
},
it's 67, anyone who can find even 67, the transactions will be attacked by this person.
ngl, this guy very smart and genius build the transaction and from the number of transactions increasing slowly and rhythmically.
captured by hacker ? because this address is 1DiegoU6ETJXK9hNWVTeuK4Y8fkksPnEnK seem fishy with 3Emiwzxme7Mrj4d89uqohXNncnRM15YESs
and he's announce this "https://www.blockchain.com/explorer/transactions/btc/69888f5e55d414b8de65f3a9307a1f414d7035cf9142239045300ce018984bd4"
the next target to take and spend.
{
"address": "1BY8GQbnueYofwSuFAT3USAhGjPrkxDdW9",
"pkscript": "76a914739437bb3dd6d1983e66629c5f08c70e5276937188ac",
"value": 1231,
"spent": false,
"spender": null
},
it's 67, anyone who can find even 67, the transactions will be attacked by this person.
ngl, this guy very smart and genius build the transaction and from the number of transactions increasing slowly and rhythmically.
Holy snappers, guys! How could we forget about this?
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
Now we can officially transition to #67.
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
Now we can officially transition to #67.
for real, i forgot who's make that wheel of fortune HAHAHAH.
Maybe bitcoin key generation cypher technique use to genrate these address still searching the method to solve this problem.
No, I don't have enough XP to meddle with the Wheel of Fortune. This thing is just too powerful.
Just by making this simple edit it took me so much mana and HP that will take me weeks to recover.
Just by making this simple edit it took me so much mana and HP that will take me weeks to recover.
Holy snappers, guys! How could we forget about this?
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
Can you round your circle more ? to 160
))) This is you try to sell python scrypt for brute 130 puzzle some posts ago ?)))
Holy snappers, guys! How could we forget about this?
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
Now we can officially transition to #67.
We did not write #66 off our bingo cards. Here, let me sort this out real quick:
Now we can officially transition to #67.
Let me fix that graph for you
Before judging, note that all your % and etc. are inside the red line and even if it weren't it would need a very high amount of zoom-in in to actually be noticeable.
% is basicly following from web privatekeys, and for the rest is just for description what the lines do on that box graph.
okay bro, thankyou for sharing your thoughts.
Let me fix that graph for you
Before judging, note that all your % and etc. are inside the red line and even if it weren't it would need a very high amount of zoom-in in to actually be noticeable.
Jump to: