Bitcoin puzzle transaction ~32 BTC prize to who solves it

[Shelby0901]

Hello guys.. My cousin leads a research team and they have a huge set up.. They have about 900 rtx4090 gpus for research.. I have been trying to convince him to grant me permission to use the set for 12 hours straight.. And finally did... Now I need a strategy to figure out the puzzle 135 or 67 which one would work fastest? I need someone to give me a plan and once it's solved I will give the person  who gave me a solid plan a reward.. I need someone who is just as passionate as I am so work with in solving atleast one puzzle...

[gygy]

Hello guys.. My cousin leads a research team and they have a huge set up.. They have about 900 rtx4090 gpus for research.. I have been trying to convince him to grant me permission to use the set for 12 hours straight.. And finally did... Now I need a strategy to figure out the puzzle 135 or 67 which one would work fastest? I need someone to give me a plan and once it's solved I will give the person  who gave me a solid plan a reward.. I need someone who is just as passionate as I am so work with in solving atleast one puzzle...

1. This is steeling and your cousin can get into trouble.
2. With a single rtx4090 you can achieve about 4000MKey/sec. So with 900 GPUs in 12 hour you have one in 2**66/4_000_000_000/900/3600/12 = 474.45 chance to solve Puzzle 67. That is about 0.21% chance.

[Shelby0901]

Hello guys.. My cousin leads a research team and they have a huge set up.. They have about 900 rtx4090 gpus for research.. I have been trying to convince him to grant me permission to use the set for 12 hours straight.. And finally did... Now I need a strategy to figure out the puzzle 135 or 67 which one would work fastest? I need someone to give me a plan and once it's solved I will give the person  who gave me a solid plan a reward.. I need someone who is just as passionate as I am so work with in solving atleast one puzzle...

1. This is steeling and your cousin can get into trouble.
2. With a single rtx4090 you can achieve about 4000MKey/sec. So with 900 GPUs in 12 hour you have one in 2**66/4_000_000_000/900/3600/12 = 474.45 chance to solve Puzzle 67. That is about 0.21% chance.

What about 135 puzzle? I have managed to reduce 135 bits down to 120 bits how long would it take?.

[nomachine]

Haha, well, let's just say that 12 hours is like giving a Kangaroo a rocket boost but asking it to hop across the Sahara Desert! There's a chance we could hit the target, but the odds are a bit like finding a needle in the multiverse – still, we’ll have the universe’s fastest Kangaroo on our side.

Let's go for it, and if we solve it, it'll be legendary. And if not? We'll have an epic tale of trying to tame the impossible with 900 GPUs. Either way, it’s going to be one wild hop about 1.7% of the total search space of puzzle 135!

[Shelby0901]

Haha, well, let's just say that 12 hours is like giving a Kangaroo a rocket boost but asking it to hop across the Sahara Desert! There's a chance we could hit the target, but the odds are a bit like finding a needle in the multiverse – still, we’ll have the universe’s fastest Kangaroo on our side.

Let's go for it, and if we solve it, it'll be legendary. And if not? We'll have an epic tale of trying to tame the impossible with 900 GPUs. Either way, it’s going to be one wild hop about 1.7% of the total search space of puzzle 135!

Any chance people have tried using point division? I mean how effectively can it be used?
I have a way to reduce the bit size using point division I need a partner team work will definitely pay off and i have the resources so when we know we are at the right place we can use the resources.. I really want someone to work with..

[kTimesG]

What about 135 puzzle? I have managed to reduce 135 bits down to 120 bits how long would it take?.

Why did you stop the reducing at 120 bits? I'd go full-blown to 1 bit. Let us know if it's a zero or not.

[nomachine]

I really want someone to work with..

Ask @kTimesG for that. He has the software, and you have the hardware. Good luck!

[Shelby0901]

What about 135 puzzle? I have managed to reduce 135 bits down to 120 bits how long would it take?.

Why did you stop the reducing at 120 bits? I'd go full-blown to 1 bit. Let us know if it's a zero or not.

The possible public keys exponentially grow.. By the time i reduce 3 digits from the end if have 1 trillion plus possible public keys

[kTimesG]

What about 135 puzzle? I have managed to reduce 135 bits down to 120 bits how long would it take?.

Why did you stop the reducing at 120 bits? I'd go full-blown to 1 bit. Let us know if it's a zero or not.

The possible public keys exponentially grow.. By the time i reduce 3 digits from the end if have 1 trillion plus possible public keys

Really? That's a lot of keys. So let me formulate the question another way: once you reduce 135 to 120 bits, is that equivalent or not to having 32768 public keys, of which one of them corresponds to a 120-bit key, while the rest of 32767 correspond to 256-bit keys?

If so, how do you pick the one public key to search for, to have a good reason of calling this as a "reduction" and not an "expansion"?

I really want someone to work with..

Ask @kTimesG for that. He has the software, and you have the hardware. Good luck!

Using 900 RTX 4090, it will take 583 days to break 135, using my software (~ 5.6 Gk/s on a single 4090). It was worth it for 130, but 135, not so much, costs are higher than the reward. We need either much higher computing power, or some advancements in EC math (some fast parallel XGCD would help, since this is the current bottleneck - all threads except one are idle, waiting for a batched inversion to finish). Doing multiple XGCD in parallel (like what JLP version does) is actually a lot slower than doing one "master" batched inversion. Ehm...