detechs
Newbie

Activity: 12
Merit: 0
|
 |
July 28, 2026, 02:39:23 PM |
|
open btckeygen.com "MrFreeDragon visualbtc tool" tick "visualize my own hex private key"
paste known puzzle keys and look at the 16 by 16 pattern
puzzle 1 key is 0x0000...0001 - single bit in bottom right corner puzzle 2 key is 0x0000...0003 - two bits puzzle 66 key reveals a pattern
what pattern does each key form on the grid which rows and columns are filled do the patterns follow a sequence compare the pattern of puzzle 66 to puzzle 1 can you predict the pattern for puzzle 71 without knowing the key?
every 5th puzzle keys. 8 out of 8 testable pairs share the same LSB. probability 1/256 = 0.39%.
vigintillion clue. base36 to base9 digit sum = 71. also "puzzle" = 42
|
|
|
|
|
sxiclub
Newbie

Activity: 26
Merit: 0
|
 |
July 28, 2026, 03:22:52 PM |
|
Puzzle 135 was solved today 
|
|
|
|
|
crytoestudo
Newbie

Activity: 42
Merit: 0
|
 |
July 28, 2026, 03:27:54 PM |
|
yes. Was RetiredC Puzzle 135 was solved today 
|
|
|
|
|
Denis_Hitov
Newbie

Activity: 51
Merit: 0
|
 |
July 28, 2026, 06:41:21 PM |
|
yes. Was RetiredC Puzzle 135 was solved today  He could have shared some of the Bitcoin. All my efforts were in vain...
|
|
|
|
|
crytoestudo
Newbie

Activity: 42
Merit: 0
|
 |
July 28, 2026, 06:50:26 PM |
|
He said he's going to do a mini-challenge. But it wasn't just you, buddy—I also tried 825,121,596,147,455,100,000,000 without success, lol. yes. Was RetiredC Puzzle 135 was solved today  He could have shared some of the Bitcoin. All my efforts were in vain...
|
|
|
|
|
Worker_puzzle_135
Newbie

Activity: 1
Merit: 0
|
 |
July 28, 2026, 06:55:00 PM |
|
What was the key? I am curious if i was close or not.
|
|
|
|
|
crytoestudo
Newbie

Activity: 42
Merit: 0
|
 |
July 28, 2026, 06:58:09 PM |
|
was not revealedWhat was the key? I am curious if i was close or not.
|
|
|
|
|
SRG02289
Newbie

Activity: 25
Merit: 0
|
 |
July 28, 2026, 07:58:23 PM Last edit: July 28, 2026, 09:03:28 PM by SRG02289 |
|
If a user is asking for a simple information, why you give more that he asked? At least if you give the private key, give also the address...he needs now to scan again and again wasting power and money....sometimes is a joke for everyone...
There is only 2 addresses with form 1PWo3JeB9jrG for puzzle 71. If the first one is on 4, the second one should be on 60-68.
1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx SRG02289, please don't feint the comunity. There are only 2 addresses betweeen puzzle 71's gap 0x400..0x7fff. One of the is solution and another one is 0x4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB. Other 2 addresses(1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH - 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx) aren't between the gap 0x400..0x7fff. How do you like the disclosure of one address in the 7xxxx range? I can throw dust on another address in the 7xxxx range that hasn't yet been published in this thread. Three addresses with the prefix 1PWo3JeB9jrG have already been found in the 6xxxx range... One address in the 5xxxx range... I feel better SRG02289. Thank a lot! Could you please share other prefixed addresses and private keys? 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp in 6xxxx 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 in 7xxxx So, they seems like that? 4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 5xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 6xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp 75dfb41bc502e1cf50 = 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx 7xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 ? = 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU NO! 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 79B5402CAD2BBA4D17 1PWo3JeB9jrGAPqRCdeFghiJkMmigGBGmV 5A.... - 5FFF....
|
|
|
|
|
jasperr
Newbie

Activity: 9
Merit: 0
|
 |
July 28, 2026, 08:28:24 PM |
|
Guyzzz, #135 has been swept 😔
To: 1Prestige1zSYorBdz94KA2UbJW3hYLTn4.
I suspect this is even the creator because 125, 130 and now 135 could all be traced to the non-prestigious owner of this address. What is funnier is that all this dough is just sited, unspent largely.
I think the creator decided after some timeline, they would be sweeping the prizes 😭
|
|
|
|
|
eggsylacer
Newbie

Activity: 31
Merit: 0
|
 |
July 28, 2026, 09:54:59 PM |
|
Guyzzz, #135 has been swept 😔
To: 1Prestige1zSYorBdz94KA2UbJW3hYLTn4.
I suspect this is even the creator because 125, 130 and now 135 could all be traced to the non-prestigious owner of this address. What is funnier is that all this dough is just sited, unspent largely.
I think the creator decided after some timeline, they would be sweeping the prizes 😭
https://bitcointalk.org/index.php?topic=5517607.msg66986617#msg66986617
|
|
|
|
|
OzBtcOz
Newbie

Activity: 25
Merit: 0
|
 |
Today at 05:35:17 AM |
|
If a user is asking for a simple information, why you give more that he asked? At least if you give the private key, give also the address...he needs now to scan again and again wasting power and money....sometimes is a joke for everyone...
There is only 2 addresses with form 1PWo3JeB9jrG for puzzle 71. If the first one is on 4, the second one should be on 60-68.
1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx SRG02289, please don't feint the comunity. There are only 2 addresses betweeen puzzle 71's gap 0x400..0x7fff. One of the is solution and another one is 0x4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB. Other 2 addresses(1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH - 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx) aren't between the gap 0x400..0x7fff. How do you like the disclosure of one address in the 7xxxx range? I can throw dust on another address in the 7xxxx range that hasn't yet been published in this thread. Three addresses with the prefix 1PWo3JeB9jrG have already been found in the 6xxxx range... One address in the 5xxxx range... I feel better SRG02289. Thank a lot! Could you please share other prefixed addresses and private keys? 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp in 6xxxx 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 in 7xxxx So, they seems like that? 4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 5xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 6xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp 75dfb41bc502e1cf50 = 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx 7xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 ? = 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU NO! 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 79B5402CAD2BBA4D17 1PWo3JeB9jrGAPqRCdeFghiJkMmigGBGmV 5A.... - 5FFF.... Good Job SRG02289, But I wondered that how it is possible ? 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 - PQrSTUVWxyZ part is serried. If it is in 71 bit gap, it is very rare address.
|
|
|
|
|
adamclassic
Newbie

Activity: 1
Merit: 0
|
 |
Today at 06:48:33 AM |
|
Interesting how any of these guys haven’t tried getting in touch with someone who has already a client code since they are so worried about Mara
Could I borrow your client code to test transactions in Slipstream?
|
|
|
|
|
puzzle_72_worker
Newbie

Activity: 2
Merit: 0
|
 |
Today at 06:54:02 AM |
|
Hello everyone. I am reading and reading and i do not understand something. If everybody is saying that there is no pattern, so even if you knowsome keys you cannot find the key based on findings, what is with this secret? If you say is in 7xxx and have the keys why not sharing? You have it or not? Or you affraid that if you share a key with a prefix someone is smarter than you guys and get the prize?
|
|
|
|
|
SRG02289
Newbie

Activity: 25
Merit: 0
|
 |
Today at 07:29:00 AM |
|
If a user is asking for a simple information, why you give more that he asked? At least if you give the private key, give also the address...he needs now to scan again and again wasting power and money....sometimes is a joke for everyone...
There is only 2 addresses with form 1PWo3JeB9jrG for puzzle 71. If the first one is on 4, the second one should be on 60-68.
1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx SRG02289, please don't feint the comunity. There are only 2 addresses betweeen puzzle 71's gap 0x400..0x7fff. One of the is solution and another one is 0x4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB. Other 2 addresses(1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH - 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx) aren't between the gap 0x400..0x7fff. How do you like the disclosure of one address in the 7xxxx range? I can throw dust on another address in the 7xxxx range that hasn't yet been published in this thread. Three addresses with the prefix 1PWo3JeB9jrG have already been found in the 6xxxx range... One address in the 5xxxx range... I feel better SRG02289. Thank a lot! Could you please share other prefixed addresses and private keys? 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp in 6xxxx 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 in 7xxxx So, they seems like that? 4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 5xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 6xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp 75dfb41bc502e1cf50 = 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx 7xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 ? = 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU NO! 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 79B5402CAD2BBA4D17 1PWo3JeB9jrGAPqRCdeFghiJkMmigGBGmV 5A.... - 5FFF.... Good Job SRG02289, But I wondered that how it is possible ? 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 - PQrSTUVWxyZ part is serried. If it is in 71 bit gap, it is very rare address. 1PWo3JeB9jFd82FngRKLPXcEpEea3F49cJ 739267A2B8FF58F7D8 1PWo3JeB9jFd82FngRKLPXcEpEea3F49cJ 739267A2B8FF58F7D8 1PWo3JeB9dbFMo9AXH94uJnDTM4fMTMnh7 739267B9C89B85DA73 1PWo3JeB967sD7rSuCkEoSrDgrnzDQzXex 7392680229B95C8D3E 1PWo3JeB9YGqzN3a7wFXRdidqbe33m23sJ 73926817BFD985F89C 1PWo3JeB9kAp4U2q1LV1BRZ92sRQ46DKjR 739268352223EFFA76 1PWo3JeB9oircsgK4DmwTAeMDjPq7fZwk4 73926861755EDF274E 1PWo3JeB9HV7PFQKe6qkYjQJrXJrvTEaaM 7392690981FB5C7BF4 1PWo3JeB9QcogGY6TJAXHu37oe6EWzgDXQ 7392692B11B1953592 1PWo3JeB9cB1aVRhbNEL4GajpRtX3xKFmL 7392696986BF7AD171 1PWo3JeB9Jv3TMbrxZGtqid4Q9Hz1V9Jy3 739269F867429AE7B5 1PWo3JeB9jFxfs63GrMQpsdp1cGBRd1CAS 739269FCC1F78092EF 1PWo3JeB9jFxfs63GrMQpsdp1cGBRd1CAS 739269FCC1F78092EF
Are you analyzing this? I gave an example 1PWo3JeB9jF
|
|
|
|
|
detechs
Newbie

Activity: 12
Merit: 0
|
 |
Today at 08:33:37 AM |
|
Hello everyone. I am reading and reading and i do not understand something. If everybody is saying that there is no pattern, so even if you knowsome keys you cannot find the key based on findings, what is with this secret? If you say is in 7xxx and have the keys why not sharing? You have it or not? Or you affraid that if you share a key with a prefix someone is smarter than you guys and get the prize?
There is 100% patterns everywhere. Just most people want to brute force it. This onion has so many layers it's not funny anymore. I have opened up so many layers of the BTC puzzle and Bitcoin genesis block and satoshi, saatoshi, patoshi etc. right now I'm only a couple layers from unlocking all puzzles at once. That's what it looks like but there's probably a million more layers underneath. That's the prize. Once u go far down and look u see the bip39 word wheel, the osculation, the binary maths, the heart beat. Following the dust trail. Finding out the truth of life and all the different cycles and time frames and zoom levels. If you're interested pm me I'm thinking of making a discord to share everything I learned so we can group force the logic puzzle side
|
|
|
|
|
puzzle_72_worker
Newbie

Activity: 2
Merit: 0
|
 |
Today at 08:53:02 AM |
|
I cannot give you any message because of rule of forum. I have developed 500+ scripts and multiple platforms for tracking, storing keys,predictions models and much more. For me is a hobby and not really the prizes. The real prizes are dormand wallets and distribution of addresses.
|
|
|
|
|
simonmales
Newbie

Activity: 5
Merit: 1
|
 |
Today at 12:10:49 PM |
|
I built a browser WebGPU brute-forcer for Puzzle 71. Free, no backend, and here is exactly where the money goes.The money part first, since this thread has seen plenty of tools that bury it: if the app ever finds the key, the signed tx pays 6 BTC to an address you enter and the remainder to me, the developer. That split sits on the page before the Start button does anything, and I'm stating it here too so nobody has to dig for it later. The found key itself stays in your browser. Signing happens locally with @scure/btc-signer, and since there's no backend, nothing gets uploaded anywhere. You don't make an account and there's no pool to join. The app is krackpot.io. It does secp256k1, SHA-256 and RIPEMD-160 in WGSL compute shaders and searches Puzzle 71's range right in the browser. The search path has zero dependencies, and the whole site is a static PWA that keeps working offline. Two updates on Krackpot, the browser WebGPU brute-forcer for Puzzle 71 I posted here last week.1. NVIDIA on Linux works. In the launch post I said I hadn't tested NVIDIA under Linux at all. A user has since run it on a GTX 1060 6GB (Linux, Chromium, proprietary NVIDIA driver) and reported 15.3 MK/s. I haven't verified that run, and the number surprised me: it beats my measured RTX 2070 (13.2 MK/s) and GTX 1660 Super (8.2 MK/s) on far less silicon. Either the proprietary-driver Vulkan path suits this integer-heavy workload unusually well, or the run conditions differed. If anyone here has an NVIDIA card on Linux, I'd like a second data point before that number goes in the comparison table. Intel on Linux is still unconfirmed. 2. The front-running hole is closed: Krackpot no longer touches the public mempool. In the launch post I said the auto-broadcast went through public explorers and didn't defend against claim-time front-running, the way Puzzles 66 and 69 were lost: the winning tx exposes the public key, Kangaroo recovers a 71-bit-range key from it in seconds, and a mempool bot rebroadcasts at a higher fee. I didn't want to leave it at a warning, so I rebuilt the claim path: - On a hit, the browser submits the signed tx straight to Rebar Shield's private-mempool RPC. It goes from your browser to mining pools without ever entering the public mempool, so the public key stays hidden until the tx is in a block.
- As a backup, an encrypted copy of the same signed tx reaches me over Nostr and I submit it privately too (Slipstream or Shield). It's the identical tx with your 6 BTC output already signed in, so I can't redirect anything, and whichever submission confirms first wins. The found key stays in your browser the whole time. The only thing that travels is the signed tx.
- If the Shield call fails, the UI shows manual Slipstream instructions. In every case you see the recovered key and the full signed hex first, so the do-it-yourself route stays open.
Before anyone calls this bulletproof: it closes the public-mempool exposure window, which is how 66 and 69 died. It does not make theft impossible. You're trusting the private-submission service and its pools not to leak the tx before a block, and a malicious miner inside that set could still extract the key. If you see a hole in this design, I want to hear about it. Updated write-up, including the new claim path: krackpot.io/blog/how-it-works
|
|
|
|
|
|
kTimesG
|
 |
Today at 12:33:06 PM |
|
- As a backup, an encrypted copy of the same signed tx reaches me over Nostr and I submit it privately too (Slipstream or Shield). It's the identical tx with your 6 BTC output already signed in, so I can't redirect anything, and whichever submission confirms first wins. The found key stays in your browser the whole time. The only thing that travels is the signed tx.
Except any kind of signed data (TX, message, r and s on a napkin) instantly derives the public key. Unless you're cooking up stuff using some dumb LLM you should have known this is obvious and is the reason why absolutely no one should ever touch up on anything you share.
|
|
|
|
simonmales
Newbie

Activity: 5
Merit: 1
|
 |
Today at 01:49:53 PM |
|
- As a backup, an encrypted copy of the same signed tx reaches me over Nostr and I submit it privately too (Slipstream or Shield). It's the identical tx with your 6 BTC output already signed in, so I can't redirect anything, and whichever submission confirms first wins. The found key stays in your browser the whole time. The only thing that travels is the signed tx.
Except any kind of signed data (TX, message, r and s on a napkin) instantly derives the public key. Unless you're cooking up stuff using some dumb LLM you should have known this is obvious and is the reason why absolutely no one should ever touch up on anything you share. Fair point, but if I wanted to scam it, I would just push the private key to me.
|
|
|
|
|
OzBtcOz
Newbie

Activity: 25
Merit: 0
|
 |
Today at 02:09:17 PM |
|
If a user is asking for a simple information, why you give more that he asked? At least if you give the private key, give also the address...he needs now to scan again and again wasting power and money....sometimes is a joke for everyone...
There is only 2 addresses with form 1PWo3JeB9jrG for puzzle 71. If the first one is on 4, the second one should be on 60-68.
1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx SRG02289, please don't feint the comunity. There are only 2 addresses betweeen puzzle 71's gap 0x400..0x7fff. One of the is solution and another one is 0x4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB. Other 2 addresses(1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH - 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx) aren't between the gap 0x400..0x7fff. How do you like the disclosure of one address in the 7xxxx range? I can throw dust on another address in the 7xxxx range that hasn't yet been published in this thread. Three addresses with the prefix 1PWo3JeB9jrG have already been found in the 6xxxx range... One address in the 5xxxx range... I feel better SRG02289. Thank a lot! Could you please share other prefixed addresses and private keys? 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp in 6xxxx 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 in 7xxxx So, they seems like that? 4da0aa7f285f61b1c5 = 1PWo3JeB9jrGMLiH83vD775NRqHZMR2hHB 5xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 6xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGWfHDnpdGk54CRaRcbvZeYp 75dfb41bc502e1cf50 = 1PWo3JeB9jrGFsveoYdzAukjcwp645X7Zx 7xxxxxxxxxxxxxxxxx = 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 ? = 1PWo3JeB9jrGwfHDNpdGK54CRas7fsVzXU NO! 1PWo3JeB9jrGLDTmsp45h1pDXXtb7zisQH 79B5402CAD2BBA4D17 1PWo3JeB9jrGAPqRCdeFghiJkMmigGBGmV 5A.... - 5FFF.... Good Job SRG02289, But I wondered that how it is possible ? 1PWo3JeB9jrGwPQrSTUVWxyZAARjU29VG2 - PQrSTUVWxyZ part is serried. If it is in 71 bit gap, it is very rare address. 1PWo3JeB9jFd82FngRKLPXcEpEea3F49cJ 739267A2B8FF58F7D8 1PWo3JeB9jFd82FngRKLPXcEpEea3F49cJ 739267A2B8FF58F7D8 1PWo3JeB9dbFMo9AXH94uJnDTM4fMTMnh7 739267B9C89B85DA73 1PWo3JeB967sD7rSuCkEoSrDgrnzDQzXex 7392680229B95C8D3E 1PWo3JeB9YGqzN3a7wFXRdidqbe33m23sJ 73926817BFD985F89C 1PWo3JeB9kAp4U2q1LV1BRZ92sRQ46DKjR 739268352223EFFA76 1PWo3JeB9oircsgK4DmwTAeMDjPq7fZwk4 73926861755EDF274E 1PWo3JeB9HV7PFQKe6qkYjQJrXJrvTEaaM 7392690981FB5C7BF4 1PWo3JeB9QcogGY6TJAXHu37oe6EWzgDXQ 7392692B11B1953592 1PWo3JeB9cB1aVRhbNEL4GajpRtX3xKFmL 7392696986BF7AD171 1PWo3JeB9Jv3TMbrxZGtqid4Q9Hz1V9Jy3 739269F867429AE7B5 1PWo3JeB9jFxfs63GrMQpsdp1cGBRd1CAS 739269FCC1F78092EF 1PWo3JeB9jFxfs63GrMQpsdp1cGBRd1CAS 739269FCC1F78092EF
Are you analyzing this? I gave an example 1PWo3JeB9jF Not exactly SRG I am analyzing disturbution of 1PWo3JeB9jG WIF keys in which gap in WIF format like as below Zi3q x = 0x400000000000000000 Zi3q y = 0x42002abcaa097b510a Zi3q z = 0x44b882fda626e59915
Zi3r 1 = 0x4770db3ea2444fe120 Zi3r 2 = 0x4a29337f9e61ba292b Zi3r 3 = 0x4ce18bc09a7f247136 Zi3r 4 = 0x4f99e401969c8eb941 Zi3r 5 = 0x52523c4292b9f9014c Zi3r 6 = 0x550a94838ed7634957 Zi3r 7 = 0x57c2ecc48af4cd9162 Zi3r 8 = 0x5a7b4505871237d96c Zi3r 9 = 0x5d339d46832fa22177 Zi3r A = 0x5febf5877f4d0c6982 Zi3r B = 0x62a44dc87b6a76b18d Zi3r C = 0x655ca6097787e0f998 Zi3r D = 0x6814fe4a73a54b41a3 Zi3r E = 0x6acd568b6fc2b589ae Zi3r F = 0x6d85aecc6be01fd1b9 Zi3r G = 0x703e070d67fd8a19c4 Zi3r H = 0x72f65f4e641af461cf Zi3r J = 0x75aeb78f60385ea9da Zi3r K = 0x78670fd05c55c8f1e4 Zi3r L = 0x7b1f681158733339ef Zi3r M = 0x7dd7c05254909d81fa As you know beginnings of WIFs are same and there should be only 47-48 addresses with 1PWo3JeB9jG prefixed statiscally, if they distrubited correctly and we have enough prefixed addresses, we can find the solutions gap. This is just about statistic and theoric, not proved thing.
|
|
|
|
|
|