Bitcoin Forum
February 06, 2025, 05:17:35 PM *
News: Community Awards voting is open
 
   Home   Help Search Login Register More  
Pages: « 1 ... 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 [212] 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 ... 368 »
  Print  
Author Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it  (Read 252333 times)
mcdouglasx
Full Member
***
Offline Offline

Activity: 546
Merit: 147



View Profile WWW
December 24, 2023, 06:50:14 PM
 #4221


Using Kangaroo i can solve every puzzle till 100 bit in very short time (of course im talking about puzzles where public key is available). Till 70 bit it's almost immediatley.

The problem is the range is getting exponetnially bigger to the extent it's just too big for current hardware (at least available for home users).



If you can handle 100 bits, why don't you solve puzzle #130? If I had that power I would have already found it.

Cause estimated time for solving 100bit i have in DAYS while estimated time for 130bit i have in HUNDREDS OF YEARS. This shows how massive is the gap between these two ranges. People seems to not realize that.

That's assuming you unlock directly using the publickey of puzzle #130, but certain techniques allow you to go from 130 to 100 or less.

WanderingPhilospher
Sr. Member
****
Offline Offline

Activity: 1288
Merit: 253

Shooters Shoot...


View Profile
December 24, 2023, 07:01:14 PM
Last edit: May 01, 2024, 08:29:12 PM by Mr. Big
 #4222


Using Kangaroo i can solve every puzzle till 100 bit in very short time (of course im talking about puzzles where public key is available). Till 70 bit it's almost immediatley.

The problem is the range is getting exponetnially bigger to the extent it's just too big for current hardware (at least available for home users).



If you can handle 100 bits, why don't you solve puzzle #130? If I had that power I would have already found it.

Cause estimated time for solving 100bit i have in DAYS while estimated time for 130bit i have in HUNDREDS OF YEARS. This shows how massive is the gap between these two ranges. People seems to not realize that.

That's assuming you unlock directly using the publickey of puzzle #130, but certain techniques allow you to go from 130 to 100 or less.

You can go to 80, 64, 52, 12 or 1. Doesn't mean it's faster.

Just by reducing the bit range doesn't make it faster, without new code being able to run multiple pub keys at once, etc.



I really find it hard to believe, actually, I don't find it hard to believe, that within this community of people who follow these posts, we can't get enough people, that have a combined total of 500 GPUs, whether it's 500 people with 1 GPU each or 100 people with 5 GPUs each, or a mixture of people and GPU quantities...
But we can't get 500 GPUs to crack #66 in less than a year, if we had 1,000 GPUs, right at 6 months.
It's kind of funny, but not Smiley

The current 66 bit pool, that is running, is doing double the work.

I may do some tinkering over the next few weeks and set up some sort of pool, more than likely just keep it personal, because exposing servers to the public, there's always those 1 or 2 peeps who spend time trying to hack it lol.

Anywho, 500 GPUs = #66 found in less than a year.
AlanJohnson
Member
**
Offline Offline

Activity: 126
Merit: 11


View Profile
December 24, 2023, 07:13:53 PM
 #4223

I really find it hard to believe, actually, I don't find it hard to believe, that within this community of people who follow these posts, we can't get enough people, that have a combined total of 500 GPUs, whether it's 500 people with 1 GPU each or 100 people with 5 GPUs each, or a mixture of people and GPU quantities...
But we can't get 500 GPUs to crack #66 in less than a year, if we had 1,000 GPUs, right at 6 months.
It's kind of funny, but not Smiley

The current 66 bit pool, that is running, is doing double the work.

I may do some tinkering over the next few weeks and set up some sort of pool, more than likely just keep it personal, because exposing servers to the public, there's always those 1 or 2 peeps who spend time trying to hack it lol.

Anywho, 500 GPUs = #66 found in less than a year.

There is massive lack of trust in crypro sphere. Why should i trust anybody that he will pay me anything in case of solving puzzle or even my part for scanning some ranges ?
WanderingPhilospher
Sr. Member
****
Offline Offline

Activity: 1288
Merit: 253

Shooters Shoot...


View Profile
December 24, 2023, 08:04:07 PM
 #4224

The moment you send out puzzle 66 and reveal it's public key, some looter will double spend your 1 year effort in a few seconds, so there is a reason why nobody joins you, they want it for free.

Even if using the do not RBF option?
WanderingPhilospher
Sr. Member
****
Offline Offline

Activity: 1288
Merit: 253

Shooters Shoot...


View Profile
December 24, 2023, 08:22:22 PM
 #4225

Doesn't matter RBF or not, you could still double spend the tx, that's why nobody is solving it, unless someone gives the transaction to a miner and they include the whole balance as fee in a block they mine, you could also sign a message with some undeniable proof that you have found the key sooner than anyone else in order to provide it to the pool which mines the tx if you are going to fight the looters until the whole balance is spent as fee.

Ok, walk me through this.

I thought if a transaction was broadcast with do not RBF, do not Replace By Fee (higher transaction fee), then it could not be double spent.

Not true?
3dmlib
Jr. Member
*
Offline Offline

Activity: 45
Merit: 2


View Profile
December 24, 2023, 09:38:10 PM
 #4226

That depends which nodes and pools honor that protocol, you could simply be tricked by a pool operator, they could solve the key and include the tx in a block, there are many ways to double spend it. Unless every single node, miner, pool honors the RBF disabled flag. There is no guarantee for your puzzle 66, 67, 68 etc to be safe from looters.

Hello. Can RBF transaction be on different receiver address or only fee can be increased for faster processing, but receiver address should be same as in initial first transaction? Thanks.
CY4NiDE
Member
**
Offline Offline

Activity: 63
Merit: 14


View Profile
December 25, 2023, 12:02:03 AM
Last edit: December 25, 2023, 09:45:39 AM by CY4NiDE
 #4227

If normally it would not be safe, imagine now with the mempool being congested as it is. It would not be wise to transfer anything out of the lower range wallets for a while if you manage to open one.

1CY4NiDEaNXfhZ3ndgC2M2sPnrkRhAZhmS
WanderingPhilospher
Sr. Member
****
Offline Offline

Activity: 1288
Merit: 253

Shooters Shoot...


View Profile
December 25, 2023, 12:13:00 AM
 #4228

Quote
There are no limits on changing the address or fees, those limits are only on some wallets, otherwise you can change the fee, and receiving address by default as many times. If you are fighting a looter by double spending, it's better that you send the new tx to the initially intended address, but things like that should be automated.

If normally it would not be safe, imagine now with the mempool being congested as it is. It would not be wise to transfer anything out of the lower range wallets for a while if you manage to open one.

Yet someone snuck out #64....

It really makes no sense, I guess all that reading I did was wrong, about not using the RBF option, etc.

I guess I'll just have to take my chances.
CY4NiDE
Member
**
Offline Offline

Activity: 63
Merit: 14


View Profile
December 25, 2023, 12:52:29 AM
 #4229


Yet someone snuck out #64....

It really makes no sense, I guess all that reading I did was wrong, about not using the RBF option, etc.

I guess I'll just have to take my chances.


I've read that most wallets are dropping the option to disable RBF, it's usually on by default now.

One can no longer find this option in the newest Electrum versions for example. Would need a version older than 4.4.0 to get that option back.

Also, #64 had 0.6 BTC back in 2022 when it was cracked.

While I don't consider that to be no little amount, the stakes are much higher now at 6.6 BTC for wallet #66.

I guess the solver would need to wait for the Russians to go to sleep before sneaking out those funds.  Cheesy

1CY4NiDEaNXfhZ3ndgC2M2sPnrkRhAZhmS
citb0in
Hero Member
*****
Offline Offline

Activity: 896
Merit: 782


Bitcoin g33k


View Profile
December 25, 2023, 07:05:06 AM
Last edit: December 25, 2023, 07:35:21 AM by citb0in
 #4230

Take your chances by deploying a bot to compete with the looter, otherwise you can kiss your coins good bye. Or just talk  with a large pool beforehand, you could offer them $10,000 bonus and if they include the tx in their block, other pools won't dare to mine that block again just to take those extra coins.

So you are claiming that any Bitcoin transaction could be double-spended and therefore all Bitcoin transactions are insecure. Makes sense ?

What do you think of a challenge? I transfer an amount of x coins, you only know the source address, which I will publish here. Its private key will be in the range of 66bit just like the mentioned puzzle. Then you siphon off the coins and transfer them to another address before I receive them just like you described the looter would. If the coins end up at your freely chosen address, you can keep them. If they end up with me, you have lost and made a fool of yourself. Deal ?

  _      _   _       __  _          _  _   __
 |_) |  / \|/   (_  / \ | \  / |_ |_) (_ 
 |_) |_ \_/ \_ |\   __) \_/ |_ \/  |_ | \ __)
--> citb0in Solo-Mining Group <--- low stake of only 0.001 BTC. We regularly rent about 5 PH/s hash power and direct it to SoloCK pool. Wanna know more? Read through the link and JOIN NOW
WanderingPhilospher
Sr. Member
****
Offline Offline

Activity: 1288
Merit: 253

Shooters Shoot...


View Profile
December 25, 2023, 07:23:03 AM
 #4231

Take your chances by deploying a bot to compete with the looter, otherwise you can kiss your coins good bye. Or just talk  with a large pool beforehand, you could offer them $10,000 bonus and if they include the tx in their block, other pools won't dare to mine that block again just to take those extra coins.

So you are claiming that any Bitcoin transaction could be double-spended and therefore all Bitcoin transactions are insecure. Makes sense ?

What do you think of a challenge? I transfer an amount of x coins, you only know the source address, which I will publish here. Then you siphon off the coins and transfer them to another address before I receive them just like you described the looter would. If the coins end up at your freely chosen address, you can keep them. If they end up with me, you have lost and made a fool of yourself. Deal ?

I am pretty sure he's only talking about the low bit challenge/puzzles, like #66.
citb0in
Hero Member
*****
Offline Offline

Activity: 896
Merit: 782


Bitcoin g33k


View Profile
December 25, 2023, 07:35:45 AM
 #4232

I forgot to mention that I will use a private within the 66bit key range, I edited my post above.

  _      _   _       __  _          _  _   __
 |_) |  / \|/   (_  / \ | \  / |_ |_) (_ 
 |_) |_ \_/ \_ |\   __) \_/ |_ \/  |_ | \ __)
--> citb0in Solo-Mining Group <--- low stake of only 0.001 BTC. We regularly rent about 5 PH/s hash power and direct it to SoloCK pool. Wanna know more? Read through the link and JOIN NOW
Venus Blue
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 25, 2023, 08:06:19 AM
Last edit: December 25, 2023, 08:26:33 AM by Venus Blue
 #4233

Take your chances by deploying a bot to compete with the looter, otherwise you can kiss your coins good bye. Or just talk  with a large pool beforehand, you could offer them $10,000 bonus and if they include the tx in their block, other pools won't dare to mine that block again just to take those extra coins.

So you are claiming that any Bitcoin transaction could be double-spended and therefore all Bitcoin transactions are insecure. Makes sense ?

What do you think of a challenge? I transfer an amount of x coins, you only know the source address, which I will publish here. Then you siphon off the coins and transfer them to another address before I receive them just like you described the looter would. If the coins end up at your freely chosen address, you can keep them. If they end up with me, you have lost and made a fool of yourself. Deal ?

I am pretty sure he's only talking about the low bit challenge/puzzles, like #66.


Yeah... #66, #67, #68 and so on can be cracked within seconds using Kangaroo. I'm pretty sure there are bots watching those addresses. As soon as those pubkeys go live people will be warned and they'll have at least a 5-10 minutes window to solve the key and RBF. Right now with the Ordinals situation that window could be greater, specially if the solver decides to cheap out with the fees...
3dmlib
Jr. Member
*
Offline Offline

Activity: 45
Merit: 2


View Profile
December 25, 2023, 08:17:50 AM
 #4234


#66, #67, #68 and so on can be cracked within seconds using Kangaroo. I'm pretty sure there are bots watching those addresses.


Is placing transaction (with transaction fee enough to be included in next block) in the last second before new block will be mined will help?
Venus Blue
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
December 25, 2023, 08:23:14 AM
 #4235


#66, #67, #68 and so on can be cracked within seconds using Kangaroo. I'm pretty sure there are bots watching those addresses.


Is placing transaction (with transaction fee enough to be included in next block) in the last second before new block will be mined will help?

I'm not sure, someone else with more knowledge than I will be able to better answer you. Although that's something I also thought of doing...  
AlanJohnson
Member
**
Offline Offline

Activity: 126
Merit: 11


View Profile
December 25, 2023, 08:40:02 AM
 #4236

I don't why out of sudden doublespend or replacemant is a problem with puzzle 66 but wasn't before with other puzzles ...
zahid888
Member
**
Offline Offline

Activity: 287
Merit: 21

the right steps towerds the goal


View Profile
December 25, 2023, 09:18:36 AM
 #4237

Take your chances by deploying a bot to compete with the looter, otherwise you can kiss your coins good bye. Or just talk  with a large pool beforehand, you could offer them $10,000 bonus and if they include the tx in their block, other pools won't dare to mine that block again just to take those extra coins.

So you are claiming that any Bitcoin transaction could be double-spended and therefore all Bitcoin transactions are insecure. Makes sense ?

What do you think of a challenge? I transfer an amount of x coins, you only know the source address, which I will publish here. Its private key will be in the range of 66bit just like the mentioned puzzle. Then you siphon off the coins and transfer them to another address before I receive them just like you described the looter would. If the coins end up at your freely chosen address, you can keep them. If they end up with me, you have lost and made a fool of yourself. Deal ?

He is speaking quite accurately. I have witnessed numerous instances where some private keys which have been compromised. Many individuals have set up auto-send bots with those compromised keys. If any funds accidentally land there, they are immediately transferred, and it waits for confirmation. Suddenly, a miner arrives and brings 1 confirmation with him. Before the individuals transaction is confirmed, it conflicts with the 1 confirmation, and the funds are transferred to the miner who broadcasts the tx_hash with The hellll Angry Angry 1 confirmation with his pocket Shocked. I watch such cases about 4 or 5 times in a month. 1 ex: below



I urge Satoshi Nakamoto to promptly close this loophole. Only then will it be enjoyable to take on the challenge of this puzzle. Otherwise, it would be better for all of us to gracefully withdraw from this challenge. The one who has the private key and has signed the first transaction with sufficient fees, until that transaction is confirmed, no other tx_hash related to that address should be submitted in the mempool. Implementing this much is not a difficult task.

1BGvwggxfCaHGykKrVXX7fk8GYaLQpeixA
nomachine
Member
**
Offline Offline

Activity: 506
Merit: 38


View Profile
December 25, 2023, 10:32:37 AM
 #4238

I don't why out of sudden doublespend or replacemant is a problem with puzzle 66 but wasn't before with other puzzles ...

Or 67, 68, 69?   Grin

bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
Kamoheapohea
Jr. Member
*
Offline Offline

Activity: 48
Merit: 12


View Profile
December 25, 2023, 06:08:34 PM
Last edit: December 25, 2023, 06:25:43 PM by Kamoheapohea
 #4239

The solution is "exclusive mining".

As a "proof of solution" you create a hash of the privatekey (or publickey), your username and bitcoin address and post the hash here and/or other services where you have a (more or less) trusted timestamp.
This is your evidence that you solved the key before any other person.

You create your transaction locally and pick one of the big (and trusted) miningpools and send your transaction directly to the pool (contact them via E-Mail or maybe they have a preferred way of contacting). This way the public-key will never get into the mempool.
modma
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
December 25, 2023, 06:26:08 PM
 #4240

But couldn't disabling rbf and banning the use of wallets for change solve this problem?
Pages: « 1 ... 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 [212] 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 ... 368 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!