Grzegorz2022
Newbie

Activity: 11
Merit: 0
|
 |
April 27, 2026, 03:15:09 AM |
|
Hello everyone, I wanted to ask you what speeds do you get in EC, and what search speeds do you have? In sequential BSGS, if anyone still does it that way. 
|
|
|
|
|
|
nomachine
|
 |
April 27, 2026, 03:15:36 AM |
|
I found a security vulnerability , and to solve puzzle 71.........
Fascinating. . . So I’m guessing that “security vulnerability” lives in the same alternate universe where Puzzle 71 just casually folds if you stare at it hard enough. Any ETA on merging that branch into reality, or are we still in fantasy beta? Humans been chasing patterns since we were banging rocks together. It’s in the DNA. You see noise, your brain goes “nah, that’s a signal.” You see randomness, your brain goes “nah, that’s a message.” Tools turn into magic wands, and patterns turn into prophecies. Same old story, just with GPUs now. What’s happening here, 95% of the time? Pure, unfiltered pattern-chasing in places where structure straight-up does not exist... Folks out here drawing sacred geometry over random hex like it’s gonna whisper secrets back. You got people circling digits like they’re summoning something. Slicing decimals, nudging exponents, sprinkling constants like seasoning. Then hitting us with “look at the precision” like that means anything. That’s not math. That’s numerology wearing a hoodie. Let’s recap the greatest hits: Texas sharpshooter fallacy, center stage Formulas reverse-engineered after the answer’s known Random constants pulled out of thin air Overinterpreting precision like it’s divine intent And every now and then, some “advanced alien method” that somehow only works in a Reddit comment.... At some point this stops being math and turns into straight-up crystal ball territory.  Every third key? Start from f6f5431d because… vibes? Zig-zag through the keyspace like it’s a damn side-scroller? Shuffle first, then pretend it was intentional? Come on. Like… what are we even doing here? This whole thing runs on two fuels: misunderstanding how cryptographic hashing works, and the hope (the desperate hope) that there’s a hidden shortcut nobody else saw. There isn’t.  And if someone’s out here claiming they’ve “basically cracked it” because they found a cute pattern in randomness… they didn’t crack anything. They just proved how easy it is to see shapes in static. 
|
BTC: bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
ldabasim
Newbie

Activity: 18
Merit: 0
|
 |
April 27, 2026, 05:10:27 AM |
|
No way to reliably claim the reward currently even if you did crack it unfortunately  I suppose the vulnerability you're talking about is related to some range pattern you think you discovered, but you're probably wrong. Wait for 71 to be really solved and observe the key being in a completely different range than the one you are currently confident is the correct one.
|
|
|
|
|
NUCLEAR7.1
Jr. Member

Activity: 42
Merit: 1
|
 |
April 27, 2026, 05:20:17 AM Last edit: April 27, 2026, 09:42:22 PM by Mr. Big |
|
I found a security vulnerability , and to solve puzzle 71.........
Fascinating. . . So I’m guessing that “security vulnerability” lives in the same alternate universe where Puzzle 71 just casually folds if you stare at it hard enough. Any ETA on merging that branch into reality, or are we still in fantasy beta? Humans been chasing patterns since we were banging rocks together. It’s in the DNA. You see noise, your brain goes “nah, that’s a signal.” You see randomness, your brain goes “nah, that’s a message.” Tools turn into magic wands, and patterns turn into prophecies. Same old story, just with GPUs now. What’s happening here, 95% of the time? Pure, unfiltered pattern-chasing in places where structure straight-up does not exist... Folks out here drawing sacred geometry over random hex like it’s gonna whisper secrets back. You got people circling digits like they’re summoning something. Slicing decimals, nudging exponents, sprinkling constants like seasoning. Then hitting us with “look at the precision” like that means anything. That’s not math. That’s numerology wearing a hoodie. Let’s recap the greatest hits: Texas sharpshooter fallacy, center stage Formulas reverse-engineered after the answer’s known Random constants pulled out of thin air Overinterpreting precision like it’s divine intent And every now and then, some “advanced alien method” that somehow only works in a Reddit comment.... At some point this stops being math and turns into straight-up crystal ball territory.  Every third key? Start from f6f5431d because… vibes? Zig-zag through the keyspace like it’s a damn side-scroller? Shuffle first, then pretend it was intentional? Come on. Like… what are we even doing here? This whole thing runs on two fuels: misunderstanding how cryptographic hashing works, and the hope (the desperate hope) that there’s a hidden shortcut nobody else saw. There isn’t.  And if someone’s out here claiming they’ve “basically cracked it” because they found a cute pattern in randomness… they didn’t crack anything. They just proved how easy it is to see shapes in static.  I almost lost a cell in my brain reading this nonsense.
No way to reliably claim the reward currently even if you did crack it unfortunately  I suppose the vulnerability you're talking about is related to some range pattern you think you discovered, but you're probably wrong. Wait for 71 to be really solved and observe the key being in a completely different range than the one you are currently confident is the correct one. My investigations say that I am on the right track, and this means that what you said is wrong, but what I found is not something weak, and it is dangerous and inevitable, and it is not vague or random, and the margin of error is very small, and the problem lies in the resources, and solving puzzle 71 will only be a matter of time.
|
|
|
|
|
vneos
Jr. Member

Activity: 42
Merit: 12
|
 |
April 27, 2026, 06:48:09 AM |
|
No way to reliably claim the reward currently even if you did crack it unfortunately  I suppose the vulnerability you're talking about is related to some range pattern you think you discovered, but you're probably wrong. Wait for 71 to be really solved and observe the key being in a completely different range than the one you are currently confident is the correct one. My investigations say that I am on the right track, and this means that what you said is wrong, but what I found is not something weak, and it is dangerous and inevitable, and it is not vague or random, and the margin of error is very small, and the problem lies in the resources, and solving puzzle 71 will only be a matter of time. Resources are easy to obtain. You can easily rent 30×5090s on clore.ai or vast.ai and use them for 120 days. Assuming you are certain you can obtain 7.1 BTC, you could absolutely take out a loan to secure the startup capital; this would be a profitable trade. After you find it, use sha256(pubkey) to shut us up and prove that you were the one who found the key. Go do it. Stop talking nonsense here; actions speak louder than words.
|
|
|
|
|
|
|
|
nomachine
|
 |
April 27, 2026, 07:49:42 AM |
|
Look, this is exactly where the whole thing falls apart. Bitcoin ain’t just about math and fancy cryptography....it’s about credible neutrality. That’s the whole point. “If you got the keys, nobody can touch your coins.” Simple. Clean. No debates. The second you start talking about freezing dormant coins, even with some “good intentions” you already broke the rule. And once that line gets crossed? Yeah… good luck putting that genie back in the bottle. First it’s dormant coins. Then it’s “probably lost” coins. Then it’s “questionable origin” coins. Then suddenly it’s sanctioned wallets, flagged UTXOs, compliance layers… Next thing you know, you basically rebuilt the same system Bitcoin was supposed to replace, just with extra steps and better branding. Could it happen? Extremely unlikely. So yeah… don’t lose sleep over it. 
|
BTC: bc1qdwnxr7s08xwelpjy3cc52rrxg63xsmagv50fa8
|
|
|
Wanderingaran
Newbie

Activity: 45
Merit: 0
|
 |
April 27, 2026, 08:04:24 AM |
|
Look, this is exactly where the whole thing falls apart. Bitcoin ain’t just about math and fancy cryptography....it’s about credible neutrality. That’s the whole point. “If you got the keys, nobody can touch your coins.” Simple. Clean. No debates. The second you start talking about freezing dormant coins, even with some “good intentions” you already broke the rule. And once that line gets crossed? Yeah… good luck putting that genie back in the bottle. First it’s dormant coins. Then it’s “probably lost” coins. Then it’s “questionable origin” coins. Then suddenly it’s sanctioned wallets, flagged UTXOs, compliance layers… Next thing you know, you basically rebuilt the same system Bitcoin was supposed to replace, just with extra steps and better branding. Could it happen? Extremely unlikely. So yeah… don’t lose sleep over it.  Next thing you know Bitcoin will have customer service, a help desk, and a DEI officer like me..... Or… we could just let quantum computers vacuum up 5-6 million BTC in one weekend and call that sound money. Either way, at least we’ll still have the memes and the orange coin Twitter warriors screaming ‘NOTHING CHANGES’ while the network burns. Stay based, king. The slippery slope only goes one way in your head. Almost lost a brain cell reading this dormant coins Fed 2.0 nonsense. 
|
|
|
|
|
Akito S. M. Hosana
Jr. Member

Activity: 448
Merit: 8
|
 |
April 27, 2026, 08:19:11 AM |
|
All BTC dormand will freeze soon.
No, it's not going to happen. Not in any realistic sense. Bitcoin's governance makes this almost impossible. 
|
|
|
|
|
blankx4729
Newbie

Activity: 7
Merit: 0
|
 |
April 27, 2026, 09:42:25 AM Last edit: April 27, 2026, 11:14:04 AM by blankx4729 |
|
Hi Is it interesting I don't know but I found smthng more and it stop me.... I think I'm silly ))))
2^9=512 2*256=512 256=100 2*100=200 200=512
OC=270 O=70 C=200 C=12 12=2x10=20 2+10=2A or 210 21=210 546=222 500+12=512 256+256=512 546/5=109.2x10=1092 1/5=0.2x10=20 20=14 20=32
1=71.12=28=1/3=16 1=1/3=0.3(3) 71.12/16=4.445 28/16=1.75 16=si 546-512=34 34=22 34=52 34=4 33=12? 3/4=BE 3/4=0,75 0,75=0,C 1/4=0,25 0,25=0,4 0,75+0,25=1 0,C+0,4=0,4C? 4C=A7 (167) 256+14=270 90*3=270 90=1000?? 90=X-1? and can we say that 4C=SS=infinity?
Ok)) This puzzles brake my had)))
And what stop me)) The point 135 145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16 I think this point have missed something and I think is added above
but may be it's ok ) 145d2611c823a396ef6712ce0f712f09b9b4f3135e3e a3230fb9b6d08d1e16
and sorry, I know it today that D it's not something like D)
something missed - something add But it's ok - I'm just silly))
I will continue to find more but always don't have time. Always hurry up and hurry up watching on time but sometimes I think that the clock is broken that it always set on the one time.
Oh, no, I know that I don't find solution for this like flight from Earth Venus and Mars.
And I think maybe in one day somebody find that kiy in big sphere and get that gateau.
Thank you to read and sorry for English it's not good!
Testnet batch transaction exists | ✅ TRUE | | Testnet outputs map to mainnet puzzles | ✅ TRUE (by NUMBER) | | The mapping is deterministic | ✅ TRUE | | Testnet addresses were spent | ✅ TRUE | | Public keys were revealed | ✅ TRUE | | We can solve testnet private keys | ✅ TRUE (2 solved) | | The pattern can be found | ⏳ PENDING | | Testnet keys = mainnet keys | ❌ FALSE (for #70 at least) |
|
|
|
|
|
|
dex1
|
 |
April 27, 2026, 10:15:27 AM |
|
As I said before, I found a security vulnerability , and to solve puzzle 71, I'll only need 30x5090, and It will take 120 days the reward is 7 Bitcoins. It's profitable. The problem now is where to get these resources.
The only vulnerability (intended by creator) in puzzle 71 is that in 256 bit bitcoin private key 186 bits are known to be all 0s. You have to guess/brute force the other 70. There is no other vulnerability.
|
|
|
|
|
0xastraeus
Newbie

Activity: 39
Merit: 0
|
 |
April 27, 2026, 12:01:26 PM |
|
I love seeing people claim they've found some BS vulnerability. It makes me realize how many certifiable people are out there. There is NO such vulnerability, there is NO correlation between prefixes, there is NO other snake oil BS things that yall come up with. If there was, these wallets would've been solved MANY MANY moons ago. Those claiming these wallets will get blacklisted is comical, I'm sure these wallets that show ZERO indication of fraudulent activity will get blacklisted... Some of yall belong in psych wards. No way to reliably claim the reward currently even if you did crack it unfortunately  I suppose the vulnerability you're talking about is related to some range pattern you think you discovered, but you're probably wrong. Wait for 71 to be really solved and observe the key being in a completely different range than the one you are currently confident is the correct one. My investigations say that I am on the right track, and this means that what you said is wrong, but what I found is not something weak, and it is dangerous and inevitable, and it is not vague or random, and the margin of error is very small, and the problem lies in the resources, and solving puzzle 71 will only be a matter of time.
|
|
|
|
|
|
kTimesG
|
 |
April 27, 2026, 01:25:50 PM |
|
There is NO such vulnerability, there is NO correlation between prefixes, there is NO other snake oil BS things that yall come up with. If there was, these wallets would've been solved MANY MANY moons ago.
Some of yall belong in psych wards.
This thread itself is the psych ward for the last 500 pages or so. Once BTC goes back to bull trend we can expect another fresh generation of prefix hunters around here, calling themselves crypto experts who broke everything at once: the curve, the hashes, even the basic arithmetic itself. Meanwhile we're still waiting for bibiligin's hash-breaking discoveries ever since 67 was solved, as he promised to do, so...
|
Off the grid, training pigeons to broadcast signed messages.
|
|
|
akabaru48
Newbie

Activity: 2
Merit: 0
|
 |
April 27, 2026, 01:51:41 PM |
|
Testnet batch transaction exists | ✅ TRUE | | Testnet outputs map to mainnet puzzles | ✅ TRUE (by NUMBER) | | The mapping is deterministic | ✅ TRUE | | Testnet addresses were spent | ✅ TRUE | | Public keys were revealed | ✅ TRUE | | We can solve testnet private keys | ✅ TRUE (2 solved) | | The pattern can be found | ⏳ PENDING | | Testnet keys = mainnet keys | ❌ FALSE (for #70 at least) |
I only found outgoing transactions from private keys 1 to 900+
|
|
|
|
|
Realman121
Newbie

Activity: 6
Merit: 0
|
 |
April 27, 2026, 02:30:24 PM Last edit: April 27, 2026, 04:48:23 PM by Realman121 |
|
Sorry, that interrupt you)
And thank you "blankx4729" for your big counting!
Yes, I think about it, but you confirm this) And I think we can do some moving forward! I'm going to do some calculations I don't what this will give but WE are on that way)
I can't do as you did, only I can do it imagine and draw the way.... as I like say after rained always rise sun! And as I said I don't need that money - only what I want that this story end in my head)
And thank you again to read me and inviting to big story!
P.S. while you argue WE never catch the mices)
|
|
|
|
|
NUCLEAR7.1
Jr. Member

Activity: 42
Merit: 1
|
 |
April 27, 2026, 04:39:48 PM Last edit: April 27, 2026, 09:41:22 PM by Mr. Big |
|
No way to reliably claim the reward currently even if you did crack it unfortunately  I suppose the vulnerability you're talking about is related to some range pattern you think you discovered, but you're probably wrong. Wait for 71 to be really solved and observe the key being in a completely different range than the one you are currently confident is the correct one. My investigations say that I am on the right track, and this means that what you said is wrong, but what I found is not something weak, and it is dangerous and inevitable, and it is not vague or random, and the margin of error is very small, and the problem lies in the resources, and solving puzzle 71 will only be a matter of time. Resources are easy to obtain. You can easily rent 30×5090s on clore.ai or vast.ai and use them for 120 days. Assuming you are certain you can obtain 7.1 BTC, you could absolutely take out a loan to secure the startup capital; this would be a profitable trade. After you find it, use sha256(pubkey) to shut us up and prove that you were the one who found the key. Go do it. Stop talking nonsense here; actions speak louder than words. Do you think they would agree to lend you money without knowing your motives? Would you tell them you wanted to hack into a Bitcoin wallet? Can you guarantee they would agree? Of course not. Therefore, the option of borrowing money from the bank is non-existent here, even though I am 19 years old, and this in itself is a reason for a loan application to be rejected.
The one who finds the "vulnerability" or the private key itself will silently take bitcoins without making a fuss, and we won't even know who did it. "The fisherman will not tell where the fish are found"
Finding the vulnerability is not enough to find the key because the unavoidable issue is cost and resources, and that in itself is a challenge. As for the person who finds the key, they are legally obligated to prove publicly that they found it. If they are concealing their identity digitally, they are legally considered a thief.
I love seeing people claim they've found some BS vulnerability. It makes me realize how many certifiable people are out there. There is NO such vulnerability, there is NO correlation between prefixes, there is NO other snake oil BS things that yall come up with. If there was, these wallets would've been solved MANY MANY moons ago. Those claiming these wallets will get blacklisted is comical, I'm sure these wallets that show ZERO indication of fraudulent activity will get blacklisted... Some of yall belong in psych wards. No way to reliably claim the reward currently even if you did crack it unfortunately  I suppose the vulnerability you're talking about is related to some range pattern you think you discovered, but you're probably wrong. Wait for 71 to be really solved and observe the key being in a completely different range than the one you are currently confident is the correct one. My investigations say that I am on the right track, and this means that what you said is wrong, but what I found is not something weak, and it is dangerous and inevitable, and it is not vague or random, and the margin of error is very small, and the problem lies in the resources, and solving puzzle 71 will only be a matter of time. Using the word "illusion" in this context is itself scandalous. If you went back 20 years to before Bitcoin was invented and someone told you about the idea of Bitcoin, there's a 99.99% chance you'd call them an illusion.
|
|
|
|
|
Grzegorz2022
Newbie

Activity: 11
Merit: 0
|
 |
April 27, 2026, 05:12:11 PM |
|
Hello everyone, I wanted to ask you what speeds do you get in EC, and what search speeds do you have? In sequential BSGS, if anyone still does it that way.
Also, do you think anyone here will be able to answer my question? Thanks!
|
|
|
|
|
ik316m
Newbie

Activity: 11
Merit: 0
|
 |
April 27, 2026, 07:12:42 PM |
|
It is been 6+months running keyhunt bsgs searching for 135 in random mode on 4 pc's but no luck, I wish if some one like RC or anyone searching 135 in sequential mode share his status so that we can reduce some keys.
|
|
|
|
|
|
kTimesG
|
 |
April 27, 2026, 07:13:37 PM |
|
Hello everyone, I wanted to ask you what speeds do you get in EC, and what search speeds do you have? In sequential BSGS, if anyone still does it that way.
Around 1 X per addition. Not sure what "sequential BSGS" means though.
|
Off the grid, training pigeons to broadcast signed messages.
|
|
|
SecretAdmirere
Newbie

Activity: 14
Merit: 1
|
 |
April 27, 2026, 07:28:13 PM |
|
Hello everyone, I wanted to ask you what speeds do you get in EC, and what search speeds do you have? In sequential BSGS, if anyone still does it that way.
Also, do you think anyone here will be able to answer my question? Thanks!
I'm getting around 7.9b/s pubkey checks on 3070 Ti (no overclock, stock 300w), but that is just - generate coordinate and compare against a single target pubkey. It could be more but i never bothered "optimising" that pubkey kernel since it's just a old copy of my hashing kernel, just without hashing the pubkey. RCKangaroo runs at about 2.7b/s as is on github, with a little bit of changing the EC functions, it would be over 3.5b/s. Idk if that helps you with anything, it's also an old gpu and not that powerfull..
|
|
|
|
|
|