Search content
Sort by
Showing 20 of 54 results by fantom06
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
the prefix method is always the better choice
You're right! I finally cracked the puzzle (of what's happening here and why this is my last post indeed).
- I know why McD is pushing fwd with the magic theory, even after being debated and refuted for 50 pages
- I know why nomachine publishes dozens of scripts from his code folder.
- I know why Akito is too bored and sees conspiracies everywhere (remember when you PM'ed me when 130 was snitched to tell me that RC is the creator dude? bad day indeed)
- I know why real facts are refuted so intensely in this thread.
It's dead simple: considering that what happens here would make zero sense in the real world, my best guess is that at least part of you are straight-up mass manipulators (not even trolls). And I know why you do it, it's not at all hard to guess. After all, what's the best way of increasing your own chances than to convince everyone else of using some better methods, that actually are the worst ones imaginable?
GG to the guy(s) pulling the strings. You won. Since this thread is the go-to destination of anyone new to the puzzle, your mission will continue successfully. Others, like me, gave up fighting the disinformation wave. It's simply not worth it.
I think you're reading too much into it. Reality is probably way more sad.
People are desperate and this puzzle pulls ambiant temperature IQ folks like a magnet. There's likely not much more to it.
To be honest, when I came, I had a good opinion of both of you Bram24732 and kTimesG. And now it has changed. SHAME ON YOU!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
We have here actual math fascists, drug heads, delusional "experts", AI-hallucinated breakthroughs, crooks, self-called hackers, and a lot more... as if that's what the puzzles are about.
Dude, which group do you classify yourself in here? A puzzle — a TED speaker on steroids, or what?
He's afraid of not being able to catch his luck by the tail, that's why he's furious.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I have a theory regarding the remaining puzzles. I hope that those who find the key to the next puzzle will be able to delight me with bitcoins. Would you like to hear it?
I will give away 13% of all future finds
My theory is called Three Numbers. They are 4, 7, and 9. It is applicable in this puzzle.
Those who don't believe can apply the two previous puzzles using these numbers, and everything will fall into place!
For the script creators, I would also ask you to send me the working script in a private message if you create it.
If you want, I can write examples for you and post them here.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I have a theory regarding the remaining puzzles. I hope that those who find the key to the next puzzle will be able to delight me with bitcoins. Would you like to hear it?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
whatever you all do, dont keep giving bram more of your code. he already has 3000 computers and the rest of us might only be using two. so giving away all of your code secrets to him will only make sure that the rest of us end up broke with no money when he uses that knowledge to solve every remaining puzzle. dont say i never warned you when it happens. lol i do believe in some knowledge sharing though. but he has too big of an advantage already over the rest of us. just my opinion or thoughts.
I think I already said I’m not working on any puzzle now that they are no longer profitable.
I sent you a scrypt, check your private messages
Please do not send me generic AI generated scripts which don’t even make sense.
I imagine you are aware that big data already uses AI for their code, as is the case with GitHub itself. Your reasoning is ridiculous. Whether it is code that comes out of AI or human, it is still code. It is the way it is worked that matters.
and you Bram24732 didn't even write that you don't need it! You asked for it - here you go! And don't show off like a little child!
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
whatever you all do, dont keep giving bram more of your code. he already has 3000 computers and the rest of us might only be using two. so giving away all of your code secrets to him will only make sure that the rest of us end up broke with no money when he uses that knowledge to solve every remaining puzzle. dont say i never warned you when it happens. lol i do believe in some knowledge sharing though. but he has too big of an advantage already over the rest of us. just my opinion or thoughts.
I think I already said I’m not working on any puzzle now that they are no longer profitable.
I sent you a scrypt, check your private messages
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
in file very well virus
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Hey guys, there is a new Cyclone on the block
Still working hard, hu?
Some new interesting features?
Now, I even have a faster version on GitHub, where I'm experimenting with compiler flags.
Quote
================= WORK IN PROGRESS =================
Puzzle/Bits : 71
Target Hash160: f6f5431d25bbf7b...5e3475c44a0a5b8
Prefix length : 8 bytes
Mode : Random
CPU Threads : 12
Mkeys/s : 42.91
Total Checked : 1661029376
Elapsed Time : 00:00:45
Start Range : 400000000000000000
End Range : 7fffffffffffffffff
Progress : N/A
Progress Save : 0
Stride : 1
Puzzle/Bits : 71
Target Hash160: f6f5431d25bbf7b...5e3475c44a0a5b8
Prefix length : 8 bytes
Mode : Random
CPU Threads : 12
Mkeys/s : 42.91
Total Checked : 1661029376
Elapsed Time : 00:00:45
Start Range : 400000000000000000
End Range : 7fffffffffffffffff
Progress : N/A
Progress Save : 0
Stride : 1
Previously, it was 34–35 Mkeys/s.
Dookoo2/Cyclone.exe DON'T WORK random!!!
Progress Save #14 at 4200.02 sec: TotalChecked=165648870912, ElapsedTime=01:09:56, Mkeys/s=39.47
Thread Key 0: 00000000000000000000000000000000000000000000004000000000ED06BF4C
Thread Key 1: 000000000000000000000000000000000000000000000041C71C71C84FB74D1D
Thread Key 2: 0000000000000000000000000000000000000000000000438E38E38F4C82E82C
Thread Key 3: 000000000000000000000000000000000000000000000045555555566746FCAB
Thread Key 4: 0000000000000000000000000000000000000000000000471C71C71D83FF9AAA
Thread Key 5: 000000000000000000000000000000000000000000000048E38E38E4A19A7F7F
Thread Key 6: 00000000000000000000000000000000000000000000004AAAAAAAABC571EB8A
Thread Key 7: 00000000000000000000000000000000000000000000004C71C71C72E1BEE19D
Thread Key 8: 00000000000000000000000000000000000000000000004E38E38E39FCD2CDF4
Thread Key 9: 00000000000000000000000000000000000000000000005000000001180AFBE5
Thread Key 10: 000000000000000000000000000000000000000000000051C71C71C831899D1E
Thread Key 11: 0000000000000000000000000000000000000000000000538E38E38F4C811407
Thread Key 12: 000000000000000000000000000000000000000000000055555555566AB7C870
Thread Key 13: 0000000000000000000000000000000000000000000000571C71C71D87F356FB
Thread Key 14: 000000000000000000000000000000000000000000000058E38E38E49C52A4AC
Thread Key 15: 00000000000000000000000000000000000000000000005AAAAAAAABB81BE4F9
Thread Key 16: 00000000000000000000000000000000000000000000005C71C71C72B2F23946
Thread Key 17: 00000000000000000000000000000000000000000000005E38E38E39D115A50A
Thread Key 18: 0000000000000000000000000000000000000000000000600000000134385842
Thread Key 19: 000000000000000000000000000000000000000000000061C71C71C84EE355F0
Thread Key 20: 0000000000000000000000000000000000000000000000638E38E38F4C38D490
Thread Key 21: 0000000000000000000000000000000000000000000000655555555667E224EC
Thread Key 22: 0000000000000000000000000000000000000000000000671C71C71D823EFD0E
Thread Key 23: 000000000000000000000000000000000000000000000068E38E38E4A1425FFA
Thread Key 24: 00000000000000000000000000000000000000000000006AAAAAAAABC5224582
Thread Key 25: 00000000000000000000000000000000000000000000006C71C71C72E20053EA
Thread Key 26: 00000000000000000000000000000000000000000000006E38E38E39FB295D10
Thread Key 27: 00000000000000000000000000000000000000000000007000000001197A72FC
Thread Key 28: 000000000000000000000000000000000000000000000071C71C71C8328DD3E0
Thread Key 29: 0000000000000000000000000000000000000000000000738E38E38F4E4C8CBE
Thread Key 30: 0000000000000000000000000000000000000000000000755555555669FBD51C
Thread Key 31: 0000000000000000000000000000000000000000000000771C71C71D886EF6DA
Thread Key 32: 000000000000000000000000000000000000000000000078E38E38E49B721E0E
Thread Key 33: 00000000000000000000000000000000000000000000007AAAAAAAABB6BD38FE
Thread Key 34: 00000000000000000000000000000000000000000000007C71C71C72B10BA1BE
Thread Key 35: 00000000000000000000000000000000000000000000007E38E38E39C9A0A182
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
the key was found after 0.7206% of the range.
So someone solved puzzle 69 using a modified Cyclone in 20 days?
Try your luck:)
With a small tweak 😉. I'm still a bit confused about how the jump function works, so I avoided using it. Interestingly, it seems to take the same amount of time with or without it.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
the key was found after 0.7206% of the range.
So someone solved puzzle 69 using a modified Cyclone in 20 days?
Try your luck:)
terminate called after throwing an instance of 'std::invalid_argument'
what(): ╨Э╨╡╨┤╨╛╨┐╤Г╤Б╤В╨╕╨╝╤Л╨╣ ╤Б╨╕╨╝╨▓╨╛╨╗ ╨▓ ╤Б╤В╤А╨╛╨║╨╡ Base58
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
We got robbed of Puzzle 69.
Hello, we are coming out to claim we are the group that solved puzzle 69.
We are a group consisting of 12 software developers in Asia with interest in cryptography. We have been scanning puzzle 66, 67, 68 and 69 since last year.
We have rented several GPUs online to use for the puzzles. Unfortunately, puzzle 66 was solved by
1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd (not us)
but got stolen using RBF. Puzzles 67 and 68 were solved by 1 person and then finally we were able to solve puzzle 69.
We are using our custom software written using CUDA C++. Each member has several GPUs which will be given a range to scan. It was really a eureka moment when we were notified that a match was found by one of our members.
We are aware of RBF attack so we used a wallet software (we prefer not to say which one) which does not enable RBF by default, to transfer the coins. But when we checked the transaction, before it was confirmed, another transaction was created.
This is really heartbreaking for me and my group because we spent months scanning the range only for it to be stolen by others. We are contributing part of our savings to pay our GPU bills monthly. We might resort to contacting the wallet software provider but we know that our 6.9 BTC is long gone forever.
Now, our problem is how to pay our remaining GPU bill which amounts to $158,954.07. This is so frustrating! Why can't people play fair and square???
We are accepting donations to help us pay our remaining GPU bill in these addresses:
1BMWUDeiq15EDZETNG49YfdQvLoEzGBjxm
bc1q2pqem06ad053rnt656dta4nej6uqe9p786kjls
Hello, we are coming out to claim we are the group that solved puzzle 69.
We are a group consisting of 12 software developers in Asia with interest in cryptography. We have been scanning puzzle 66, 67, 68 and 69 since last year.
We have rented several GPUs online to use for the puzzles. Unfortunately, puzzle 66 was solved by
1Jvv4yWkE9MhbuwGUoqFYzDjRVQHaLWuJd (not us)
but got stolen using RBF. Puzzles 67 and 68 were solved by 1 person and then finally we were able to solve puzzle 69.
Code:
0x101d83275fb2bc762d
0x101d83275fb2bc7ba7
0x101d83275fb2bc7f4e
0x101d83275fb2bc7604
0x101d83275fb2bc7e0c
Match found!
Private Key: 0x101d83275fb2bc7e0c
Compressed Public Key: 024babadccc6cfd5f0e5e7fd2a50aa7d677ce0aa16fdce26a0d0882eed03e7ba53
We are using our custom software written using CUDA C++. Each member has several GPUs which will be given a range to scan. It was really a eureka moment when we were notified that a match was found by one of our members.
We are aware of RBF attack so we used a wallet software (we prefer not to say which one) which does not enable RBF by default, to transfer the coins. But when we checked the transaction, before it was confirmed, another transaction was created.
This is really heartbreaking for me and my group because we spent months scanning the range only for it to be stolen by others. We are contributing part of our savings to pay our GPU bills monthly. We might resort to contacting the wallet software provider but we know that our 6.9 BTC is long gone forever.
Now, our problem is how to pay our remaining GPU bill which amounts to $158,954.07. This is so frustrating! Why can't people play fair and square???
We are accepting donations to help us pay our remaining GPU bill in these addresses:
1BMWUDeiq15EDZETNG49YfdQvLoEzGBjxm
bc1q2pqem06ad053rnt656dta4nej6uqe9p786kjls
I don't understand you, you say that you were able to find the key and at the same time you write that you were unable to use bitcoins. Where is the logic?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Are you brute-forcing using a paper? How many keys per... ehm... day?
I can brute the last 12 digit for 3 hours in 3080
I have 6x 3080. So every 3 hours i can verify 6 guesses that i wrote on papers😅
Puzzle 69 start with 1 so im guessing 6 hex after 1
Every day i verify 18 guesses , i change range manually 🙃😅
This doesn't make sense for me why you brute force the first 6 digits ?!!!
Huh its like lottery ticket
You guess 1+6 hex ( ticket)
Last 12 digit brute by my rig
I dont brute the first 6 digit , in that paper is my 6 hex guesses. Add 1 in front so 7 digit 😅.
For puzzle 71 this example guesess list ✌️
0x45219D3
0x45E3C04
0x466A1EF
0x46F83D1
0x474DC6A
0x4837E58
0x48AF92C
0x4910B6F
0x49F24C1
0x4A68EB3
0x4AD73C9
0x4B8C1F7
0x4C9E745
0x4D27AF2
0x4DF53B0
0x4E7C98A
0x4F6D21F
0x50E1394
0x515E48B
0x520C7E1
0x52A1D93
I figured out how you do it. The guess is clear
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I'm going to end up believing that you're just lucky
Your method only returns the number of operations from the thread which finds the key. It discards all the tries of the 3 other threads which do not find it.
ChatGPTor not, if you want that bounty you need to up your game
I'm also preparing a script, it will appear here soon.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Hello everyone. Guys, please help me with the script. I made a script in Python that calculates addresses in order, but it calculates on the CPU. The speed is 200 Kkey/s. I have already tried everything. Tell me a script that would calculate on the GPU. Please, someone.
a hundred for the script?
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Quote
When Prefix wins - it wins by a very small margin (by just a few ops ahead)
When Prefix loses - it loses by a very high margin (proportional to range size)
When Prefix loses - it loses by a very high margin (proportional to range size)
Well we are working with very tiny ranges lol...
Quote
Once you freely let go of this constraint - you will notice that both methods act identical, which is the expected thing to happen.
For grins and giggles I will use random starting points (since I am just using 1 block size)Who needs prefixes or straight line sequential order
(2^17 range size, 500 simulations, random checked 4096 consecutive keys then skipped 64, if range was exhausted, it went back to first key skipped and checked them sequentially until key was found)
Code:
=== FINAL RESULTS (Sequential, Full Range) ===
Wins:
ScoobyDoo : 0
Prefix : 9
RandomSkip : 482
Ties : 9
Total Checks:
ScoobyDoo : 31597542
Prefix : 31485133
RandomSkip : 31429414
Total Time:
ScoobyDoo : 43.892759 seconds
Prefix : 53.199185 seconds
RandomSkip : 46.203749 seconds
Averages (Total Time / Wins):
ScoobyDoo : inf seconds/victory
Prefix : 5.911021 seconds/victory
RandomSkip : 0.095858 seconds/victory
Checks per Win:
ScoobyDoo : inf checks/win
Prefix : 3,498,348.11 checks/win
RandomSkip : 65,206.25 checks/win
Average Checks per Simulation:
ScoobyDoo : 63,195.08 checks/simulation
Prefix : 62,970.27 checks/simulation
RandomSkip : 62,858.83 checks/simulation
Ok, 2^17 range size, 500 simulations, each method started from a random point inside the range, if key not found it went to whatever keys were not checked, and started checking those.
Code:
=== FINAL RESULTS (Sequential, Full Range with Random Starts) ===
Wins:
ScoobyDoo : 133
Prefix : 241
RandomSkip : 126
Ties : 0
Total Checks:
ScoobyDoo : 31775601
Prefix : 22520018
RandomSkip : 32676939
Total Time:
ScoobyDoo : 45.047694 seconds
Prefix : 42.106104 seconds
RandomSkip : 49.145924 seconds
Averages (Total Time / Wins):
ScoobyDoo : 0.338704 seconds/victory
Prefix : 0.174714 seconds/victory
RandomSkip : 0.390047 seconds/victory
Checks per Win:
ScoobyDoo : 238,914.29 checks/win
Prefix : 93,444.06 checks/win
RandomSkip : 259,340.79 checks/win
Average Checks per Simulation:
ScoobyDoo : 63,551.20 checks/simulation
Prefix : 45,040.04 checks/simulation
RandomSkip : 65,353.88 checks/simulation
Prefix whooped some azzzzz....
Simulation 5000: Scooby_Doo = 87634 checks in 0.406732s | Prefix = 70515 checks in 0.261866s
=== FINAL RESULTS ===
Wins:
Scooby_Doo: 2423
Prefix: 2379
Ties: 198
Total Checks:
Scooby_Doo: 248193832
Prefix: 251283717
Total Time:
Scooby_Doo: 1133.652252 seconds
Prefix: 949.231911 seconds
Averages (Total Time / Wins):
Scooby_Doo : 0.467871 seconds/victory
Prefix : 0.399005 seconds/victory
Checks per Win:
Scooby_Doo : 102432.45 checks/win
Prefix : 105625.77 checks/win
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Presenting the Scooby Doo method
... also called "Where are you? Whoo Whoo!" - because we all love animals inhere: from kangaroos to cats writing better code then most here, when walking over our keyboard.
Besides, we all have something in common: we don't know where Scooby is! I mean, the random key... uhm.
Prerequisites:
1. Clone any of the prefix theory magic scripts, in whatever language you wish.
2. Make sure the programming language is not rigged (what can we even trust these days, right? Even the AI became unreliable when writing high quality enterprise-level code).
3. Patch the bastard:
4. Run and watch the magic happen! Wins wins wins WINS !!!11
The Scooby Doo method relies on the following optimizations:
- replaces deprecated prefix search with a better heuristic method - efficiency, baby!
- removes reliance on any pre-existing useless information, such as "what are we even looking for anyway?"
- finds stuff faster! Why? Who are you, the police? It just works.
- leaves any sequential method far behind. Let's get rid of that sucker and switch to the Scooby Doo method TODAY!
Caveats and known issues
1. Please don't show this to your math teacher - they may lose their night's sleep trying to figure out if you broke reality.
2. It is forbidden to shuffle the block order when comparing the Scooby Doo method with other methods.
3. If you are comparing the Scooby Doo method with any other method - please make sure to use the same block order, so that we have a fair comparison of the same initial conditions.
4. Do not dare to ever disclose the Scooby Doo method to a statistician. They will terrorize you with all sorts of graphs showing cumulative probabilities, survival functions integration areas, and all sorts of voodoo that no one who cares about their mental sanity would ever understand.
Disclaimer
The Scooby Doo method might be dangerous and present a high risk factor of working slower than expected in some circumstances, but life is dangerous anyway.
Using the Scooby Doo method is not a cryptographical advice. Use at your own discretion.
... also called "Where are you? Whoo Whoo!" - because we all love animals inhere: from kangaroos to cats writing better code then most here, when walking over our keyboard.
Besides, we all have something in common: we don't know where Scooby is! I mean, the random key... uhm.
Prerequisites:
1. Clone any of the prefix theory magic scripts, in whatever language you wish.
2. Make sure the programming language is not rigged (what can we even trust these days, right? Even the AI became unreliable when writing high quality enterprise-level code).
3. Patch the bastard:
Code:
>>> Remove this!
if not found_prefix and h.startswith(prefix_hash):
>>> Replace with this:
if random.randint(0, 5000) == 0: // critical magic update
4. Run and watch the magic happen! Wins wins wins WINS !!!11
The Scooby Doo method relies on the following optimizations:
- replaces deprecated prefix search with a better heuristic method - efficiency, baby!
- removes reliance on any pre-existing useless information, such as "what are we even looking for anyway?"
- finds stuff faster! Why? Who are you, the police? It just works.
- leaves any sequential method far behind. Let's get rid of that sucker and switch to the Scooby Doo method TODAY!
Caveats and known issues
1. Please don't show this to your math teacher - they may lose their night's sleep trying to figure out if you broke reality.
2. It is forbidden to shuffle the block order when comparing the Scooby Doo method with other methods.
3. If you are comparing the Scooby Doo method with any other method - please make sure to use the same block order, so that we have a fair comparison of the same initial conditions.
4. Do not dare to ever disclose the Scooby Doo method to a statistician. They will terrorize you with all sorts of graphs showing cumulative probabilities, survival functions integration areas, and all sorts of voodoo that no one who cares about their mental sanity would ever understand.
Disclaimer
The Scooby Doo method might be dangerous and present a high risk factor of working slower than expected in some circumstances, but life is dangerous anyway.
Using the Scooby Doo method is not a cryptographical advice. Use at your own discretion.
I'm intrigued by this method and want to try it out.
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Why people keep sending sats to puzzle wallets?
Coздaтeль дocылaeт нa aдpecc биткoинa,этo пoдcкaзкa,гдe в диaпaзoнe нaxoдитcя ключThis is your theory, but I don't see any proof
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Hahaha, take it easy... It’s not that simple... But... Every member in this topic will get 0.2 BTC—if they have a BTC address in their signature. Satisfied?
Are you talking about that key?
Code:
KyDi5tDzUCEN5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tFNbmN45bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KyDi5tJzYm5M5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk1GeGqp5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk2nLZCk5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
KzDiBk377UHr5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L2Die4KeEMng5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
L3DiBgEqot9K5bCRZhiS5sEGMpmcRZdpAhmWLRfMmutGmPHtjVob
That’s probably a scam. I’ve bunch of WIFs with partial matches in sequence, be careful not to waste your time there.
For those who think searching for WIF has some magical twist—let me tell you, it's much slower compared to generating an address directly from a private key (hex, bytes or dec).
@nomachine, maybe let the curious minds DM you directly -: this thread’s starting to feel like a rerun marathon.
Let’s save the scrolls for fresh stuff!-- Sim results
If you sum the number of checks over 10k simulations you get this :
Code:
=== FINAL RESULTS ===
Sequential: 495816995
Prefix: 496059807
WHICH IS ALMOST 50-50!
And maybe I have conducted the most experiments on prefixes, whether it be in the form of base58 or hash160.
Through these experiments, I have consistently encountered a 50-50 probability of outcomes.
Through these experiments, I have consistently encountered a 50-50 probability of outcomes.
but the basic aspect has already been demonstrated, which was the probabilistic success rate.
Well done! But let’s be real—if we’re talking probabilities, I Still remember, how you got yourself stuck in this argument when you trying to defend someone. Your heroic moment, huh? Maybe now’s a good time to snap out of that mess and chase some actual probability breakthroughs.
=== Configuration ===
Total numbers: 2,097,152
Block size: 4,096
Prefix: 3 characters (16^3 combinations)
Simulations: 10000
=== FINAL RESULTS ===
Wins:
Sequential: 3736 (Average Win Margin: 42.57%)
Prefix: 6244 (Average Win Margin: 36.55%)
Ties: 20
Total Checks:
Sequential: 10,472,126,509
Prefix: 10,548,477,557
Total numbers: 2,097,152
Block size: 4,096
Prefix: 3 characters (16^3 combinations)
Simulations: 10000
=== FINAL RESULTS ===
Wins:
Sequential: 3736 (Average Win Margin: 42.57%)
Prefix: 6244 (Average Win Margin: 36.55%)
Ties: 20
Total Checks:
Sequential: 10,472,126,509
Prefix: 10,548,477,557
Bro demonstration is over now! lets reduce the talk in this forum that we can easily read important posts
And thanks for searching all 10 digit seeds for me 
I'm always happy to help! Contact me if you have any questions!