Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 63.

nomachine

member

Activity: 503

Merit: 38

Quote from: mcdouglasx on September 15, 2024, 05:43:59 PM

Is it considered the one who uses bots as a thief? Very little ethical, yes, but they are the rules, I think RBF is poorly implemented, it should be an irrevocable choice of those who send the funds and not depend on the configuration of each node.

I don't know. But I know that I will send at least 45% to the winner address if my bot succeeds. I guess THAT will be a fair enough to prevent the winner from having a heart attack (or suicide) due to losing everything. It's one thing to be a thief and another to be a murderer. Grin

citb0in

hero member

Activity: 630

Merit: 731

Bitcoin g33k

Quote from: COBRAS on September 15, 2024, 01:56:00 PM

...
Make a transaction fee in 5% of 1btc and more ballance, for any of ballance transfer transactions ! Robot have no so many money for fee

Quote from: ?? on ??

...
why all try gake 130, but not 110 for ex ? need only 2^20 pubketxs of 2^110 crack, or make a pool for crack 2^50 keys in 2^80.

you have already been warned countless times to create consecutive posts. You ignore the warnings. Comply or there will be consequences.

AndrewWeb

jr. member

Activity: 56

Merit: 2

Quote from: WanderingPhilospher on September 15, 2024, 08:37:07 PM

No bot was used in the taking of 66's funds.

It was all a "deep fake" spoof. It's like the shell game...trying to shift and trick your eyes to what's really going on.

On to 67 for most and continuing with 130 for a small few...

So what really happened?

As for 130, I am finally moving into the exa keys/s sphere a couple of weeks from now.

WanderingPhilospher

full member

Activity: 1232

Merit: 242

Shooters Shoot...

No bot was used in the taking of 66's funds.

It was all a "deep fake" spoof. It's like the shell game...trying to shift and trick your eyes to what's really going on.

On to 67 for most and continuing with 130 for a small few...

kTimesG

member

Activity: 165

Merit: 26

Quote from: CY4NiDE on September 15, 2024, 06:30:54 PM

Quote from: ?? on ??

Quote from: Kelvin555 on September 15, 2024, 02:48:56 PM

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole Roll Eyes

.

If that was the case it would have taken much less than 45s to replace the original tx, as once you have the key it might take less than 1 second to relay the first replacement.

WTF? Yes, any 66 bit private key can be cracked in less than 1 second and replaced in the next second, if you have some precomputed data which takes somewhere like just a few hours to create, not years. Guess what? The same thing applies to bits 67, 68, 69, etc ... But come on, anyone serious in here already knows this, or at least they should. Maybe it was a manner of tens of seconds or minutes for someone who's still in 2019.

And experimenting for a higher purpose is not "preparing to steal a transaction", it's called progress towards solving higher bits. I think I went through at least 500 versions of precomputed DBs for bits in the 50 80 range, and this just for testing that my own code actually works. One of the reasons I didn't care to leave some bot running, but what went down with 66 is a good reminder that only the universe is greater than human stupidity.

Kelvin555

newbie

Activity: 8

Merit: 0

Quote from: Feron on September 15, 2024, 06:38:16 PM

I wouldn't follow the time, it's never exact, every region has a different time, blockchain goes with its specific time
example I have time 1:40 ... blockchain has 23:40 for example

I think mempool.space shows the user's local time, so you can check there.

Quote from: ApePunk on September 15, 2024, 07:00:09 PM

He did not timeline is wrong.

He is way off by 1 hour 57 minutes from the time the transaction was made to the time he posted the key.

Quote from: mcdouglasx on September 15, 2024, 05:43:59 PM

Quote from: ?? on ??

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole Roll Eyes

.

Is it considered the one who uses bots as a thief? Very little ethical, yes, but they are the rules, I think RBF is poorly implemented, it should be an irrevocable choice of those who send the funds and not depend on the configuration of each node.

RBF is not poorly implemented, remember everything about Bitcoin transactions is intended for 256 bits range not 66 bits range, if this transaction was made in 256 bits range, then no matter whatever you try about RBF, you can't steal the coins.

I am not sure if any one in this thread is the thief because when WanderingPhilosopher introduced Mara's slipstream almost everyone turned off their bots...... All I hope is the real solver is still alive and not try anything stupid, maybe he invested a lot in buying or hiring GPUs and has been searching for months or years(electricity bills), then this happened to him.

ApePunk

newbie

Activity: 7

Merit: 0

Quote from: COBRAS on September 15, 2024, 05:56:47 PM

jiHe is steal 66

https://bitcointalksearch.org/topic/m.64536611

He did not timeline is wrong.

Feron

jr. member

Activity: 67

Merit: 1

I wouldn't follow the time, it's never exact, every region has a different time, blockchain goes with its specific time
example I have time 1:40 ... blockchain has 23:40 for example

CY4NiDE

member

Activity: 63

Merit: 14

Quote from: ?? on ??

Quote from: Kelvin555 on September 15, 2024, 02:48:56 PM

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole Roll Eyes

.

I'm tending to think it wasn't any of the usuals in this thread 'cause we all thought the solver would go through MARA. For this very reason I didn't even bother to finish developing mine.

Also, I don't think anyone would bother to precompute against 66 in this scenario as the key can be cracked in mere seconds anyways.

If that was the case it would have taken much less than 45s to replace the original tx, as once you have the key it might take less than 1 second to relay the first replacement.

I was also thinking.... What if the creator himself triggered the first attempted withdraw?

Reason: To officially embed this event in the challenge's timeline at the cost of 6.6 BTC, as now "puzzle #66" will be notoriously known to have been hijacked by a bot in the proposed scenario.

The bot scenario is now undeniably part of this puzzle's history. Am I making any sense here or am I just hitting my bong too much? Cheesy

COBRAS

member

Activity: 873

Merit: 22

$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk

Quote from: mcdouglasx on September 15, 2024, 05:43:59 PM

Quote from: ?? on ??

Quote from: Kelvin555 on September 15, 2024, 02:48:56 PM

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole Roll Eyes

.

Is it considered the one who uses bots as a thief? Very little ethical, yes, but they are the rules, I think RBF is poorly implemented, it should be an irrevocable choice of those who send the funds and not depend on the configuration of each node.

jiHe is steal 66

https://bitcointalksearch.org/topic/m.64536611

mcdouglasx

member

Activity: 239

Merit: 53

New ideas will be criticized and then admired.

Quote from: ?? on ??

Quote from: Kelvin555 on September 15, 2024, 02:48:56 PM

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

kTimesG bragged about having a very fast setup and also started precalculating tames for 66bit, 67bit... Preparations you would only need if you plan to steal the transaction sitting in the mempool.
Every other user that took part in the stealing-bot-script discussions a few pages ago is suspicious.
The thief likely active here but would never confess because of repercussions...and well he would unmask as an asshole Roll Eyes

.

Is it considered the one who uses bots as a thief? Very little ethical, yes, but they are the rules, I think RBF is poorly implemented, it should be an irrevocable choice of those who send the funds and not depend on the configuration of each node.

Kelvin555

newbie

Activity: 8

Merit: 0

Quote from: nomachine on September 15, 2024, 05:30:09 AM

I even turned off the bot, thinking that the winner would go through Mara's slipstream.

We’ll see next time if that person is mocking anyone. Next time, all my bots will be ON.

Me too, I thought whoever found the private key would go through Mara's slipstream, that no one would dare go through mempool directly but how wrong I was.

The thief who stole the coins must have a nice setup, it took his bot 45 seconds to replace the transaction, I assume whether he used BSGS or Kangaroo, it took 30 seconds to find the private key and the remaining 15 seconds for opening and shutting down apps.

gygy

newbie

Activity: 20

Merit: 0

Quote from: zhengxingshui123 on September 15, 2024, 01:15:54 PM

I am a fool, and the 66 puzzle seems to have been taken away by a robot. I have no idea why this happened. Please tell me how to avoid being snatched away by robots if I crack the private key.

Yes, unfortunately it seems it has been snatched. At least https://privatekeys.pw/puzzles/bitcoin-puzzle-tx directly states that. I don't know if they have proofs. And based on that, the original address is one of that was the target of the mocking transaction.

To avoid this you need to keep the public key (of this low range keys) in secret. Unfortunately public key is designed to be public, so it is not so easy to transact without making them public.
Option 1: Mine your own block or have a deal with a mining pool.
Option 2: Mara Slipstream. But Mara still can stole it in this case.

random3425

newbie

Activity: 4

Merit: 0

Quote from: albert0bsd on July 29, 2024, 03:19:57 PM

Quote from: 1princess4 on July 29, 2024, 02:24:37 PM

Hey,

hypothetically i find the key, submit tx transaction with 0.1BTC going to my address and pay fee of 6.5 BTC. How do you steal my transaction ?

Thank you!

It is a lose-lose example in my case the bot will keep increment 1sat/vB more than your or anyone else TX.

In the final round in case to reach the limit of the input balance it will append an extra input to the TX and send 100% of the puzzle address as fee.

cant understand is worth or not to try for puzzle 67,68,69??

Baskentliia

jr. member

Activity: 65

Merit: 1

34Sf4DnMt3z6XKKoWmZRw2nGyfGkDgNJZZ

Quote from: nomachine on September 15, 2024, 09:09:36 AM

Quote from: gygy on September 15, 2024, 08:39:08 AM

🔮🔮🔮

Exactly. However, if I happen to succeed in any way, I will donate to everyone in this thread. I will definitely not send any mocking messages in addresses. Grin

It's a 100% successful prediction, rest assured. Thank you. Puzzle 130

COBRAS

member

Activity: 873

Merit: 22

$$P2P BTC BRUTE.JOIN NOW ! https://uclck.me/SQPJk

Quote from: zhengxingshui123 on September 15, 2024, 01:15:54 PM

I am a fool, and the 66 puzzle seems to have been taken away by a robot. I have no idea why this happened. Please tell me how to avoid being snatched away by robots if I crack the private key.

Make a transaction fee in 5% of 1btc and more ballance, for any of ballance transfer transactions ! Robot have no so many money for fee

Quote from: nomachine on September 15, 2024, 07:53:43 AM

Quote from: Baskentliia on September 15, 2024, 06:58:13 AM

Quote from: nomachine on September 14, 2024, 09:05:27 AM

The more private keys we have, the smaller the error would be....5% deviation on puzzle 130 is too big.

Hello, can you share the guess range or decimal number of puzzle 130

python3 predict.py 130
Puzzle 130 Predicted Value: 794791040024653568798270036743662075904.00

why all try gake 130, but not 110 for ex ? need only 2^20 pubketxs of 2^110 crack, or make a pool for crack 2^50 keys in 2^80.

zhengxingshui123

newbie

Activity: 1

Merit: 0

I am a fool, and the 66 puzzle seems to have been taken away by a robot. I have no idea why this happened. Please tell me how to avoid being snatched away by robots if I crack the private key.

nomachine

member

Activity: 503

Merit: 38

Quote from: gygy on September 15, 2024, 08:39:08 AM

🔮🔮🔮

Exactly. However, if I happen to succeed in any way, I will donate to everyone in this thread. I will definitely not send any mocking messages in addresses. Grin

gygy

newbie

Activity: 20

Merit: 0

Quote from: nomachine on September 15, 2024, 07:53:43 AM

Quote from: Baskentliia on September 15, 2024, 06:58:13 AM

Quote from: nomachine on September 14, 2024, 09:05:27 AM

The more private keys we have, the smaller the error would be....5% deviation on puzzle 130 is too big.

Hello, can you share the guess range or decimal number of puzzle 130

python3 predict.py 130
Puzzle 130 Predicted Value: 794791040024653568798270036743662075904.00

🔮🔮🔮

nomachine

member

Activity: 503

Merit: 38

Quote from: Baskentliia on September 15, 2024, 06:58:13 AM

Quote from: nomachine on September 14, 2024, 09:05:27 AM

The more private keys we have, the smaller the error would be....5% deviation on puzzle 130 is too big.

Hello, can you share the guess range or decimal number of puzzle 130

python3 predict.py 130
Puzzle 130 Predicted Value: 794791040024653568798270036743662075904.00

Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 63. (Read 245054 times)