Bitcoin puzzle transaction ~32 BTC prize to who solves it

[zahid888]

LIVE ON SCREEN DRAMA: 

- Every Prefix address in the range flashes LIVE 

- Viewers can SPOT THE KEY in real-time! 

- Your Lucky hex + GPU POWER = PURE THRILL & SUSPENSE!

https://t.me/funwithpuzzle71/129

[analyticnomad]

LIVE ON SCREEN DRAMA: 

- Every Prefix address in the range flashes LIVE 

- Viewers can SPOT THE KEY in real-time! 

- Your Lucky hex + GPU POWER = PURE THRILL & SUSPENSE!

https://t.me/funwithpuzzle71/129

You spelled "Towards" wrong in your bio and have it as "the right steps Towerds the goal".

also not clicking on that link.

[fecell]

Code:

[+] [18,067] 0.00% S: 331895.0 p/s, E: 18:19:32, TE: 16d 11:59:41, ETA: 1623936135880879259797946368y 5m 23d 17:21:04
255215748667055164621267256750573
---
[+] [18,068] 0.00% S: 331860.1 p/s, E: 18:20:48, TE: 16d 12:00:57, ETA: 1623933104747034416043261952y 3m 24d 20:39:28
143991517358151100293789707953175
---
[+] [18,069] 0.00% S: 331802.2 p/s, E: 18:22:09, TE: 16d 12:02:18, ETA: 1623935310097885652527874048y 8m 28d 09:18:56
32767286049247035966312159155777
---
[+] [18,070] 0.00% S: 331762.4 p/s, E: 18:23:27, TE: 16d 12:03:35, ETA: 1623933431784606125021724672y 5m 8d 16:40:32
246061608398769734450787649898602
---
[+] [18,071] 0.00% S: 331735.1 p/s, E: 18:24:41, TE: 16d 12:04:50, ETA: 1623928731610614548238696448y 9m 18d 04:11:44
134837377089865652108911591619220
---
[+] [18,072] 0.00% S: 331691.1 p/s, E: 18:25:59, TE: 16d 12:06:08, ETA: 1623927852853047085750026240y 6d 07:38:40
23613145780961605795832552303806
---
[+] [18,073] 0.00% S: 331644.7 p/s, E: 18:27:18, TE: 16d 12:07:27, ETA: 1623927559057088759526850560y 4m 20d 16:21:20
236907468130484250237112514600679
---
[+] [18,074] 0.00% S: 331586.9 p/s, E: 18:28:39, TE: 16d 12:08:48, ETA: 1623929873722913526030270464y 6m 12d 00:23:28
125683236821580203924033475285265
---
[+] [18,075] 0.00% S: 331558.6 p/s, E: 18:29:54, TE: 16d 12:10:03, ETA: 1623925481386162456780341248y 4m 20d 07:36:32
14459005512676139596555926487867

is a statistic well?

[zahid888]

LIVE ON SCREEN DRAMA: 

- Every Prefix address in the range flashes LIVE 

- Viewers can SPOT THE KEY in real-time! 

- Your Lucky hex + GPU POWER = PURE THRILL & SUSPENSE!

https://t.me/funwithpuzzle71/129

You spelled "Towards" wrong in your bio and have it as "the right steps Towerds the goal".

also not clicking on that link.

Thanks for catching that typo, fixed "Towerds" to "Towards" in my bio
No worries about the link at all, totally get the caution.

I’ve already scanned millions of PVK suffix, using completely random Python/C++ generation.
Now I’ve opened the exact same tool to the public so anyone can drop in their own hand-picked 8 hex characters.
Just a simple experiment: let’s see how much difference there really is between pure machine randomness and a human going “yeah this one feels lucky”,
And whether people end up clustering in the same spots.

Basically turning the unsolved Puzzle 71 into a behavioral crypto experiment and Fun.

Anyway tool is live now...

[HoMLoL]

Hello everyone!

For those looking for puzzles 71, 72, 73, etc., I have finally completed the development of a project that can unite us all in an honest search.
An honest pool with an open API.

The puzzle range is divided into 67,108,864 parts, each part being 2^44.
It uses open-source software: https://github.com/FixedPaul/VanitySearch-Bitcrack. Its source code is unmodified; you can download it directly from its repository and use it.

All automation and server interaction are handled by a Python script. In general, I have described everything in more detail on Git: https://github.com/homlol/honestpool.

Website: https://honestpool.ru 
GIT: https://github.com/homlol/honestpool 
API: https://github.com/homlol/honestpool?tab=readme-ov-file#api 
TG Group: @homlol_pool 

Good luck to everyone

[fecell]

Code:

[+] [18,067] 0.00% S: 331895.0 p/s, E: 18:19:32, TE: 16d 11:59:41, ETA: 1623936135880879259797946368y 5m 23d 17:21:04
255215748667055164621267256750573
---
[+] [18,068] 0.00% S: 331860.1 p/s, E: 18:20:48, TE: 16d 12:00:57, ETA: 1623933104747034416043261952y 3m 24d 20:39:28
143991517358151100293789707953175
---
[+] [18,069] 0.00% S: 331802.2 p/s, E: 18:22:09, TE: 16d 12:02:18, ETA: 1623935310097885652527874048y 8m 28d 09:18:56
32767286049247035966312159155777
---
[+] [18,070] 0.00% S: 331762.4 p/s, E: 18:23:27, TE: 16d 12:03:35, ETA: 1623933431784606125021724672y 5m 8d 16:40:32
246061608398769734450787649898602
---
[+] [18,071] 0.00% S: 331735.1 p/s, E: 18:24:41, TE: 16d 12:04:50, ETA: 1623928731610614548238696448y 9m 18d 04:11:44
134837377089865652108911591619220
---
[+] [18,072] 0.00% S: 331691.1 p/s, E: 18:25:59, TE: 16d 12:06:08, ETA: 1623927852853047085750026240y 6d 07:38:40
23613145780961605795832552303806
---
[+] [18,073] 0.00% S: 331644.7 p/s, E: 18:27:18, TE: 16d 12:07:27, ETA: 1623927559057088759526850560y 4m 20d 16:21:20
236907468130484250237112514600679
---
[+] [18,074] 0.00% S: 331586.9 p/s, E: 18:28:39, TE: 16d 12:08:48, ETA: 1623929873722913526030270464y 6m 12d 00:23:28
125683236821580203924033475285265
---
[+] [18,075] 0.00% S: 331558.6 p/s, E: 18:29:54, TE: 16d 12:10:03, ETA: 1623925481386162456780341248y 4m 20d 07:36:32
14459005512676139596555926487867

is a statistic well?

current state:

Code:

[+] [19,979] 0.00% S: 324569.5 p/s, E: 06:26:12, TE: 18d 04:45:24, ETA: 1619688167311456692992999424y 9m 16d 13:30:40
154138132311997239066806131546382

it was 2 days and 4237314074705763787341824 years reduce.

[Poopari]

I have been playing around EC math for some time that i don't remember. But may be I am crazy or lost my analytical acuman or whatever you call it you are free to do so. I have reached a juncture that I have two scalar values and two points one of the point being puzzle public key point. Here is explanation.

Scalar_S1
Scalar_S2

Mataphor_Point_P1
Puzzle_Point_P2


S1*P1= P3
S2*P3= P2

It also works either way as well.
S2*P1= P4
S1*P4= P2

Now either this is a step towards something or may be I lost my energy to call it something anyhow.

[kTimesG]

I have two scalar values and two points one of the point being puzzle public key point.

S1*P1= P3
S2*P3= P2

Why so many words for "I have the private key"?

Sweep the puzzle or end the trolling, these are pretty much your two options.

Or, if you don't have P1's scalar, then you can simply generate whatever P1 you want out of P2, G, S1 and S2, to simply transfer the ECDLP(P2) to a different point.

[fecell]

I have been playing around EC math for some time that i don't remember. But may be I am crazy or lost my analytical acuman or whatever you call it you are free to do so. I have reached a juncture that I have two scalar values and two points one of the point being puzzle public key point. Here is explanation.

Scalar_S1
Scalar_S2

Mataphor_Point_P1
Puzzle_Point_P2


S1*P1= P3
S2*P3= P2

It also works either way as well.
S2*P1= P4
S1*P4= P2

Now either this is a step towards something or may be I lost my energy to call it something anyhow.

of coz. its simple math.
>> S2*P1= P4
>> S1*P4= P2
so, S2*S1*P1=P2.

>> S1*P1= P3
>> S2*P3= P2
so, S2*S1*P1 = P2

and all other P's well.

[cctv5go]

A crash test:
Hash160☞Public key☞Private key

[brainless]

A crash test:
Hash160☞Public key☞Private key

Try first
Public key☞Private key

[farou9]

i dont remember where but i have seen someone talking about if we have k1 and k1 * g = p1 then we have p1.y=p2.x  how can we get k2 in this case ?

[Poopari]

Why so many words for "I have the private key"?

Sweep the puzzle or end the trolling, these are pretty much your two options.

Or, if you don't have P1's scalar, then you can simply generate whatever P1 you want out of P2, G, S1 and S2, to simply transfer the ECDLP(P2) to a different point.

First of all thank you for your reply. Secondly, I am not trolling anyone here neither I have the private key of puzzle 134. I don't know whether you've said it due to mathematical juncture that I posted or for the sake of having a laugh on it. But I am serious here. I don't have kP and I don't understood your suggestion either how to manipulate this in our favor.

[Garys27]

Why so many words for "I have the private key"?

Sweep the puzzle or end the trolling, these are pretty much your two options.

Or, if you don't have P1's scalar, then you can simply generate whatever P1 you want out of P2, G, S1 and S2, to simply transfer the ECDLP(P2) to a different point.

First of all thank you for your reply. Secondly, I am not trolling anyone here neither I have the private key of puzzle 134. I don't know whether you've said it due to mathematical juncture that I posted or for the sake of having a laugh on it. But I am serious here. I don't have kP and I don't understood your suggestion either how to manipulate this in our favor.

I will help you for half of the puzzle loot 

[Tony8989]

1PWo3JeB9SyEuPyjoqKm2Ur6xUNJigqkmF

1PWo3JeB9d5CYrv5dzc4P8cr59ibFRMZMf

1PWo3JeB9sYfCE3gqL4LADHDLuhtr3kFH3

1PWo3JeB9Xa4x6UjH5tqGTkb8WE6H9MJuv

1PWo3JeB9UnXe1CR3K7rEt9te92E6SBH5p

1PWo3JeB9HvP415UbBEyMW9VEkUj619KGD

1PWo3JeB9NmXAKPPnPLNnuEo5pLCKASzs9

1PWo3JeB9JykV7ixxyAr8QfTQWFRN7THDJ

1PWo3JeB9tWXkfLAyxnnq6ykiBXAv4g5nc

still nothing guys

[E36cat]

1PWo3JeB9SyEuPyjoqKm2Ur6xUNJigqkmF

1PWo3JeB9d5CYrv5dzc4P8cr59ibFRMZMf

1PWo3JeB9sYfCE3gqL4LADHDLuhtr3kFH3

1PWo3JeB9Xa4x6UjH5tqGTkb8WE6H9MJuv

1PWo3JeB9UnXe1CR3K7rEt9te92E6SBH5p

1PWo3JeB9HvP415UbBEyMW9VEkUj619KGD

1PWo3JeB9NmXAKPPnPLNnuEo5pLCKASzs9

1PWo3JeB9JykV7ixxyAr8QfTQWFRN7THDJ

1PWo3JeB9tWXkfLAyxnnq6ykiBXAv4g5nc

still nothing guys

1PWo3JeB9jakyr87nZvq34SGhWNMvDbay4

[kTimesG]

I don't know whether you've said it due to mathematical juncture that I posted or for the sake of having a laugh on it. But I am serious here. I don't have kP and I don't understood your suggestion either how to manipulate this in our favor.

There's nothing to manipulate that helps with anything, you can choose whatever scalars S1 and S2 (and S3 and S4 up to whatever), and simply compute inv(S1*S2*...) * P2 to get a P1. This works for all the points on the curve. So, zero useful extra information to help you retrieve the unknown scalar (which needs to be relative to the generator, not to what is basically one and the same point). It's not like you have some sort of solvable system of independent equations there, if they are derivable one from another.

[optioncmdPR]

Puzzle 71 will be solved within next week, stay tuned.I am confident that I have found mathematical magic.

 curious , if your mathematical magic always seems to take a dive about halfway through the integer. I ask because this happens to me, regardless of approach angle.

🎯 REVISED P71 POSITIONING:
✅ Position:  77.3%  ( Success Probability 88.0% )
📍 Target Range: 0x7174 area
🔬 Improved Calibration: Enhanced mathematical modeling
📊 Confidence: Higher precision positioning
🎯 Search Strategy: COVERAGE deployment recommended
Reason for sharing this update:

"The mathematical positioning keeps evolving as I refine the φ-based calculations. This has higher success probability."

So anyone want too hash this ? 😅🤔

🚀 ADAPTIVE AI RANGE DEPLOYMENT:
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
📦 PRECISION: 717BF1E8E60C65E698 → 717D955714BE2A1968
              Width:  0.01% (118,059,162,071,741,136 keys)
              Surgical precision + AI

📦  BALANCED: 717B2D02DED7C1B1E0 → 717E5A3D1BF2CE4E20
              Width:  0.02% (228,903,190,186,990,656 keys)
              Optimal balance + AI

📦    SAFETY: 7178CB173103783CC0 → 7180BC28C9C717C340
              Width:  0.05% (572,257,975,467,476,608 keys)
              Enhanced safety + AI

📦  COVERAGE: 7174D28E64A1A87980 → 7184B4B19628E78680
              Width:  0.10% (1,144,515,950,934,953,216 keys)
              Maximum coverage + AI

Seems pi theory not so bad hmmmm. I predict also near here.. let see 😅

           I took the first 65536 decimals of pi and with it made a 256 x 256 grid, then rotated the grid 90 degrees, therebye transposing the digits that were verticle into horizonal rows, 256 per line. When you take this matrix and resize its  containment box, very very interesting results appear at the edges. Then it will piss you off because this method, just like any others its so close to matching known values but not enough to accurately predict. As usual.

[fecell]

Rhetorical question:
Why use sha256 multiple times after secp256k1?

Code:

[+] [18,067] 0.00% S: 331895.0 p/s, E: 18:19:32, TE: 16d 11:59:41, ETA: 1623936135880879259797946368y 5m 23d 17:21:04
255215748667055164621267256750573
---
[+] [18,068] 0.00% S: 331860.1 p/s, E: 18:20:48, TE: 16d 12:00:57, ETA: 1623933104747034416043261952y 3m 24d 20:39:28
143991517358151100293789707953175
---
[+] [18,069] 0.00% S: 331802.2 p/s, E: 18:22:09, TE: 16d 12:02:18, ETA: 1623935310097885652527874048y 8m 28d 09:18:56
32767286049247035966312159155777
---
[+] [18,070] 0.00% S: 331762.4 p/s, E: 18:23:27, TE: 16d 12:03:35, ETA: 1623933431784606125021724672y 5m 8d 16:40:32
246061608398769734450787649898602
---
[+] [18,071] 0.00% S: 331735.1 p/s, E: 18:24:41, TE: 16d 12:04:50, ETA: 1623928731610614548238696448y 9m 18d 04:11:44
134837377089865652108911591619220
---
[+] [18,072] 0.00% S: 331691.1 p/s, E: 18:25:59, TE: 16d 12:06:08, ETA: 1623927852853047085750026240y 6d 07:38:40
23613145780961605795832552303806
---
[+] [18,073] 0.00% S: 331644.7 p/s, E: 18:27:18, TE: 16d 12:07:27, ETA: 1623927559057088759526850560y 4m 20d 16:21:20
236907468130484250237112514600679
---
[+] [18,074] 0.00% S: 331586.9 p/s, E: 18:28:39, TE: 16d 12:08:48, ETA: 1623929873722913526030270464y 6m 12d 00:23:28
125683236821580203924033475285265
---
[+] [18,075] 0.00% S: 331558.6 p/s, E: 18:29:54, TE: 16d 12:10:03, ETA: 1623925481386162456780341248y 4m 20d 07:36:32
14459005512676139596555926487867

is a statistic well?

current state:

Code:

[+] [19,979] 0.00% S: 324569.5 p/s, E: 06:26:12, TE: 18d 04:45:24, ETA: 1619688167311456692992999424y 9m 16d 13:30:40
154138132311997239066806131546382

it was 2 days and 4237314074705763787341824 years reduce.

it's one thread test python script.
I'm shocked.

Code:

---
[+] [23,071] 0.00% S: 284020.6 p/s, E: 08:11:16, TE: 20d 20:46:44, ETA: 1608218584649767732054589440y 10m 8d 07:21:36
238481803112972095737066543953970
---
[+] [23,072] 0.00% S: 283910.9 p/s, E: 08:12:49, TE: 20d 20:48:16, ETA: 1608231297785976453800656896y 9m 18d 20:30:56
127257571804068049423987504638556
---
[+] [23,073] 0.00% S: 283839.8 p/s, E: 08:14:17, TE: 20d 20:49:45, ETA: 1608240481529862446628470784y 5m 20d 11:48:16
16033340495163967082111446359174
---
[+] [23,074] 0.00% S: 283801.5 p/s, E: 08:15:42, TE: 20d 20:51:10, ETA: 1608246644233578118603866112y 6m 11d 15:32:16
229327662844686647552188427620015
---
[+] [23,075] 0.00% S: 283790.8 p/s, E: 08:17:04, TE: 20d 20:52:32, ETA: 1608250225446504813796786176y 9m 2d 01:57:20
118103431535782583224710878822617
---
[+] [23,076] 0.00% S: 283786.7 p/s, E: 08:18:26, TE: 20d 20:53:53, ETA: 1608253203113222630635732992y 6m 29d 02:40:00
6879200226878518897233330025219
---
[+] [23,077] 0.00% S: 283800.3 p/s, E: 08:19:45, TE: 20d 20:55:13, ETA: 1608254515208766918852870144y 1m 6d 04:09:36
220173522576401181352911801804076
---
[+] [23,078] 0.00% S: 283814.7 p/s, E: 08:21:05, TE: 20d 20:56:32, ETA: 1608255732800132037635735552y 5m 24d 07:00:16
108949291267497117025434253006678
---
[+] [23,079] 0.00% S: 283798.3 p/s, E: 08:22:28, TE: 20d 20:57:55, ETA: 1608259876753818796962086912y 5m 3d 18:42:08
322243613617019779481112724785535
---

reduce 15669300082259363815751680 years within 3 days.



seems best DLP solve algo. but hidden for anyone exept me, as U know.
'cuze me. must complete research B4 share all iИf0

[teguh54321]

Code:

[+] [18,067] 0.00% S: 331895.0 p/s, E: 18:19:32, TE: 16d 11:59:41, ETA: 1623936135880879259797946368y 5m 23d 17:21:04
255215748667055164621267256750573
---
[+] [18,068] 0.00% S: 331860.1 p/s, E: 18:20:48, TE: 16d 12:00:57, ETA: 1623933104747034416043261952y 3m 24d 20:39:28
143991517358151100293789707953175
---
[+] [18,069] 0.00% S: 331802.2 p/s, E: 18:22:09, TE: 16d 12:02:18, ETA: 1623935310097885652527874048y 8m 28d 09:18:56
32767286049247035966312159155777
---
[+] [18,070] 0.00% S: 331762.4 p/s, E: 18:23:27, TE: 16d 12:03:35, ETA: 1623933431784606125021724672y 5m 8d 16:40:32
246061608398769734450787649898602
---
[+] [18,071] 0.00% S: 331735.1 p/s, E: 18:24:41, TE: 16d 12:04:50, ETA: 1623928731610614548238696448y 9m 18d 04:11:44
134837377089865652108911591619220
---
[+] [18,072] 0.00% S: 331691.1 p/s, E: 18:25:59, TE: 16d 12:06:08, ETA: 1623927852853047085750026240y 6d 07:38:40
23613145780961605795832552303806
---
[+] [18,073] 0.00% S: 331644.7 p/s, E: 18:27:18, TE: 16d 12:07:27, ETA: 1623927559057088759526850560y 4m 20d 16:21:20
236907468130484250237112514600679
---
[+] [18,074] 0.00% S: 331586.9 p/s, E: 18:28:39, TE: 16d 12:08:48, ETA: 1623929873722913526030270464y 6m 12d 00:23:28
125683236821580203924033475285265
---
[+] [18,075] 0.00% S: 331558.6 p/s, E: 18:29:54, TE: 16d 12:10:03, ETA: 1623925481386162456780341248y 4m 20d 07:36:32
14459005512676139596555926487867

is a statistic well?

current state:

Code:

[+] [19,979] 0.00% S: 324569.5 p/s, E: 06:26:12, TE: 18d 04:45:24, ETA: 1619688167311456692992999424y 9m 16d 13:30:40
154138132311997239066806131546382

it was 2 days and 4237314074705763787341824 years reduce.

it's one thread test python script.
I'm shocked.

Code:

---
[+] [23,071] 0.00% S: 284020.6 p/s, E: 08:11:16, TE: 20d 20:46:44, ETA: 1608218584649767732054589440y 10m 8d 07:21:36
238481803112972095737066543953970
---
[+] [23,072] 0.00% S: 283910.9 p/s, E: 08:12:49, TE: 20d 20:48:16, ETA: 1608231297785976453800656896y 9m 18d 20:30:56
127257571804068049423987504638556
---
[+] [23,073] 0.00% S: 283839.8 p/s, E: 08:14:17, TE: 20d 20:49:45, ETA: 1608240481529862446628470784y 5m 20d 11:48:16
16033340495163967082111446359174
---
[+] [23,074] 0.00% S: 283801.5 p/s, E: 08:15:42, TE: 20d 20:51:10, ETA: 1608246644233578118603866112y 6m 11d 15:32:16
229327662844686647552188427620015
---
[+] [23,075] 0.00% S: 283790.8 p/s, E: 08:17:04, TE: 20d 20:52:32, ETA: 1608250225446504813796786176y 9m 2d 01:57:20
118103431535782583224710878822617
---
[+] [23,076] 0.00% S: 283786.7 p/s, E: 08:18:26, TE: 20d 20:53:53, ETA: 1608253203113222630635732992y 6m 29d 02:40:00
6879200226878518897233330025219
---
[+] [23,077] 0.00% S: 283800.3 p/s, E: 08:19:45, TE: 20d 20:55:13, ETA: 1608254515208766918852870144y 1m 6d 04:09:36
220173522576401181352911801804076
---
[+] [23,078] 0.00% S: 283814.7 p/s, E: 08:21:05, TE: 20d 20:56:32, ETA: 1608255732800132037635735552y 5m 24d 07:00:16
108949291267497117025434253006678
---
[+] [23,079] 0.00% S: 283798.3 p/s, E: 08:22:28, TE: 20d 20:57:55, ETA: 1608259876753818796962086912y 5m 3d 18:42:08
322243613617019779481112724785535
---

reduce 15669300082259363815751680 years within 3 days.



seems best DLP solve algo. but hidden for anyone exept me, as U know.
'cuze me. must complete research B4 share all iИf0

Need comment from KtimesG 😅