Bitcoin puzzle transaction ~32 BTC prize to who solves it

[ripemdhash]

here algo for finding in base58 how much difference is  beetween two bitcoin address

Code:

def base58_decode(s):
    base58_alphabet = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
    base58_dict = {c: i for i, c in enumerate(base58_alphabet)}

    num = 0
    for char in s:
        num = num * 58 + base58_dict[char]
    return num

def base58_encode(num):
    base58_alphabet = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
    if num == 0:
        return '1'
    result = ''
    while num > 0:
        num, idx = divmod(num, 58)
        result = base58_alphabet[idx] + result
    return result

def base58_diff(a, b):
    num_a = base58_decode(a)
    num_b = base58_decode(b)
    diff = num_b - num_a
    #print(diff)
    return base58_encode(diff)

def base58_sum(a, b):
    num_a = base58_decode(a)
    num_b = base58_decode(b)
    total = num_a + num_b
    return base58_encode(total)

# 
string1 = "13zb1hQxk5UHQDGTNScqWQj1Za9yDshWgH"
string2 = "13zb1hQzzSib25bt5DbkBFjHmbrHLRR9F2"

diff_result = base58_diff(string1, string2)
sum_result = base58_sum(string1, string2)

print("Difference:")
print(diff_result)

example as result above:

Code:

Difference: 3FNFJcsLRhmyufr1HD2hK7YidZk

[1714261402]

1714261402

[abdenn0ur]

=================================================================================
#66 PUZZLE RANGE 
based off my own personal work I believe #66 has high probability to be in one of these ranges:
me BTC: 1Dqsy2uo24Mq9Awg1gU4R7tjs3XYRrHyTZ 
Remember I can help you with #67 and rest of puzzles, all the data I collect myself with my own resources and electricity!

example: I find similar addresses like this one (within range) and analyze the wif, I understand there is no relation between address and private key, this is just based on large dataset comparison and probability, not guaranteed:
13Zb1hQBwVSzcX7L3KsxLMykonkpXui5r7    KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1txcTqpmeSt3KytEyM    37AFE498AC3D7A127
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so    KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1_________________    20000000000000000:3ffffffffffffffff
 
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa111111111111111111
80000000000000000000000000000000000000000000000003703ce60364eed80ffa9b640000
000000000000000000000000000000000000000000000003703ce60364eed80f
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1zzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000037c3e6b8c27a5a456c9a41dffff
0000000000000000000000000000000000000000000000037c3e6b8c27a5a456
3703ce60364eed80f:37c3e6b8c27a5a456

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa211111111111111111
800000000000000000000000000000000000000000000000037c3e6b8c27a5a456c9a41e0000
0000000000000000000000000000000000000000000000037c3e6b8c27a5a456
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa2zzzzzzzzzzzzzzzzz
80000000000000000000000000000000000000000000000003883ff114ea5c709d98acd7ffff
000000000000000000000000000000000000000000000003883ff114ea5c709d
37c3e6b8c27a5a456:3883ff114ea5c709d

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa311111111111111111
80000000000000000000000000000000000000000000000003883ff114ea5c709d98acd80000
000000000000000000000000000000000000000000000003883ff114ea5c709d
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa3zzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000039441769dad133ce467b591ffff
0000000000000000000000000000000000000000000000039441769dad133ce4
3883ff114ea5c709d:39441769dad133ce4

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa611111111111111111
80000000000000000000000000000000000000000000000003ac4481af3280d57205c7060000
000000000000000000000000000000000000000000000003ac4481af3280d572
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa6zzzzzzzzzzzzzzzzz
80000000000000000000000000000000000000000000000003b8460737f537a1b8d4cfbfffff
000000000000000000000000000000000000000000000003b8460737f537a1b8
3ac4481af3280d572:3b8460737f537a1b8

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZu11111111111111111
800000000000000000000000000000000000000000000000032833c4ced4a60e672067080000
0000000000000000000000000000000000000000000000032833c4ced4a60e67
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZuzzzzzzzzzzzzzzzzz
8000000000000000000000000000000000000000000000000334354a57975cdaadef6fc1ffff
00000000000000000000000000000000000000000000000334354a57975cdaad
32833c4ced4a60e67:334354a57975cdaad

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZv11111111111111111
8000000000000000000000000000000000000000000000000334354a57975cdaadef6fc20000
00000000000000000000000000000000000000000000000334354a57975cdaad
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZvzzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000034036cfe05a13a6f4be787bffff
0000000000000000000000000000000000000000000000034036cfe05a13a6f4
334354a57975cdaad:34036cfe05a13a6f4

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZw11111111111111111
800000000000000000000000000000000000000000000000034036cfe05a13a6f4be787c0000
0000000000000000000000000000000000000000000000034036cfe05a13a6f4
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZwzzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000034c3855691cca733b8d8135ffff
0000000000000000000000000000000000000000000000034c3855691cca733b
34036cfe05a13a6f4:34c3855691cca733b

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZx11111111111111111
800000000000000000000000000000000000000000000000034c3855691cca733b8d81360000
0000000000000000000000000000000000000000000000034c3855691cca733b
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZxzzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000035839daf1df813f825c89efffff
0000000000000000000000000000000000000000000000035839daf1df813f82
34c3855691cca733b:35839daf1df813f82

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZz11111111111111111
80000000000000000000000000000000000000000000000003643b607aa2380bc92b92aa0000
000000000000000000000000000000000000000000000003643b607aa2380bc9
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZzzzzzzzzzzzzzzzzzz
80000000000000000000000000000000000000000000000003703ce60364eed80ffa9b63ffff
000000000000000000000000000000000000000000000003703ce60364eed80f
3643b607aa2380bc9:3703ce60364eed80f
=================================================================================

I have a hunch that puzzle #66 starts with 594 in decimal, because it was the bitcoin amount funded (I assume by the creator), probably as part of a clue.

That was when the creator multiplied the prize by x10 so that the prize BTC amount matches the puzzle number (6.6BTC).
That's true for all other unsolved puzzles.
Plus, creator stated that the puzzles aren't really puzzles, so you won't find any pattern or an equation, your only chance to get the prize is by brute forcing the key. 

[mcdouglasx]

=================================================================================
#66 PUZZLE RANGE 
based off my own personal work I believe #66 has high probability to be in one of these ranges:
me BTC: 1Dqsy2uo24Mq9Awg1gU4R7tjs3XYRrHyTZ 
Remember I can help you with #67 and rest of puzzles, all the data I collect myself with my own resources and electricity!

example: I find similar addresses like this one (within range) and analyze the wif, I understand there is no relation between address and private key, this is just based on large dataset comparison and probability, not guaranteed:
13Zb1hQBwVSzcX7L3KsxLMykonkpXui5r7    KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1txcTqpmeSt3KytEyM    37AFE498AC3D7A127
13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so    KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1_________________    20000000000000000:3ffffffffffffffff
 
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa111111111111111111
80000000000000000000000000000000000000000000000003703ce60364eed80ffa9b640000
000000000000000000000000000000000000000000000003703ce60364eed80f
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa1zzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000037c3e6b8c27a5a456c9a41dffff
0000000000000000000000000000000000000000000000037c3e6b8c27a5a456
3703ce60364eed80f:37c3e6b8c27a5a456

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa211111111111111111
800000000000000000000000000000000000000000000000037c3e6b8c27a5a456c9a41e0000
0000000000000000000000000000000000000000000000037c3e6b8c27a5a456
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa2zzzzzzzzzzzzzzzzz
80000000000000000000000000000000000000000000000003883ff114ea5c709d98acd7ffff
000000000000000000000000000000000000000000000003883ff114ea5c709d
37c3e6b8c27a5a456:3883ff114ea5c709d

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa311111111111111111
80000000000000000000000000000000000000000000000003883ff114ea5c709d98acd80000
000000000000000000000000000000000000000000000003883ff114ea5c709d
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa3zzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000039441769dad133ce467b591ffff
0000000000000000000000000000000000000000000000039441769dad133ce4
3883ff114ea5c709d:39441769dad133ce4

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa611111111111111111
80000000000000000000000000000000000000000000000003ac4481af3280d57205c7060000
000000000000000000000000000000000000000000000003ac4481af3280d572
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qa6zzzzzzzzzzzzzzzzz
80000000000000000000000000000000000000000000000003b8460737f537a1b8d4cfbfffff
000000000000000000000000000000000000000000000003b8460737f537a1b8
3ac4481af3280d572:3b8460737f537a1b8

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZu11111111111111111
800000000000000000000000000000000000000000000000032833c4ced4a60e672067080000
0000000000000000000000000000000000000000000000032833c4ced4a60e67
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZuzzzzzzzzzzzzzzzzz
8000000000000000000000000000000000000000000000000334354a57975cdaadef6fc1ffff
00000000000000000000000000000000000000000000000334354a57975cdaad
32833c4ced4a60e67:334354a57975cdaad

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZv11111111111111111
8000000000000000000000000000000000000000000000000334354a57975cdaadef6fc20000
00000000000000000000000000000000000000000000000334354a57975cdaad
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZvzzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000034036cfe05a13a6f4be787bffff
0000000000000000000000000000000000000000000000034036cfe05a13a6f4
334354a57975cdaad:34036cfe05a13a6f4

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZw11111111111111111
800000000000000000000000000000000000000000000000034036cfe05a13a6f4be787c0000
0000000000000000000000000000000000000000000000034036cfe05a13a6f4
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZwzzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000034c3855691cca733b8d8135ffff
0000000000000000000000000000000000000000000000034c3855691cca733b
34036cfe05a13a6f4:34c3855691cca733b

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZx11111111111111111
800000000000000000000000000000000000000000000000034c3855691cca733b8d81360000
0000000000000000000000000000000000000000000000034c3855691cca733b
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZxzzzzzzzzzzzzzzzzz
800000000000000000000000000000000000000000000000035839daf1df813f825c89efffff
0000000000000000000000000000000000000000000000035839daf1df813f82
34c3855691cca733b:35839daf1df813f82

KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZz11111111111111111
80000000000000000000000000000000000000000000000003643b607aa2380bc92b92aa0000
000000000000000000000000000000000000000000000003643b607aa2380bc9
KwDiBf89QgGbjEhKnhXJuH7LrciVrZi3qZzzzzzzzzzzzzzzzzzz
80000000000000000000000000000000000000000000000003703ce60364eed80ffa9b63ffff
000000000000000000000000000000000000000000000003703ce60364eed80f
3643b607aa2380bc9:3703ce60364eed80f
=================================================================================

I have a hunch that puzzle #66 starts with 594 in decimal, because it was the bitcoin amount funded (I assume by the creator), probably as part of a clue.

That was when the creator multiplied the prize by x10 so that the prize BTC amount matches the puzzle number (6.6BTC).
That's true for all other unsolved puzzles.
Plus, creator stated that the puzzles aren't really puzzles, so you won't find any pattern or an equation, your only chance to get the prize is by brute forcing the key. 

regarding puzzle #66 you may be right, we are not in the mind of the creator to know,
I have analyzed the way the curve behaves and I think there are patterns everywhere... brute force is just "brute force" but there are mathematical methods to take load off numbers, everyone who knows this has advantages over others even if others have 100 times more computing power. It is a puzzle because it is based on finding the way to find the keys faster, if the creator only cared about brute force, the public keys would not be revealed.

[brainless]

who can solve
p = 115792089237316195423570985008687907852837564279074904382605163141518161494335
a = 1099511627776
b = 115792089237316195423570985008687907852837564279074904382605163141005436653346
c = (a-b) %p
result = 1612236468765

in pubkey

p =115792089237316195423570985008687907852837564279074904382605163141518161494335
a = 02feea6cae46d55b530ac2839f143bd7ec5cf8b266a41d6af52d5e688d9094696d
b = 02746bd76e07a0dbbcc610245439ee1db94f73b70df43bc543d4046ebe119ad6b3
c = (a-b) %p
result = 02b21dd66bfde832c2dae35688c0e15b91b274ec018e2c14e23f1ca7cb32fcca73

substract formula
p = int(2**256 - 2**32 - 977)
x1 =  # fill pubkey1-x
y1=  # fill pubkey1-y
x2=  # fill pubkey2-x
y2=  # fill pubkey2-y



dx = (x1 - x2) % p
dy = (y1 - (-y2)) % p
c = dy * gmpy2.invert(dx, p) % p
Rx = (c*c - x2 - x1) % p
Ry = (c*(x2 - Rx) - y2) % p
print (Rx , Ry)
print (hex(Rx) , hex(Ry))


if you have alternate formula for adjust with mod p, apply and check for get acurate result in pubkey

No one have experience to play ecc ?

[Kamoheapohea]

...
No one have experience to play ecc ?

No. It won't work. ECC is not linear so you can not use linear functions as a shortcut. Also it uses modular arithmetic which prevents other shortcuts you guys try over the last months.
Why don't you believe the smartest mathematicians (yes, much smarter and more educated than you and me) that there is nothing faster than BSGS and Pollard Rho/Lambda/Kangaroo?

[brainless]

...
No one have experience to play ecc ?

No. It won't work. ECC is not linear so you can not use linear functions as a shortcut. Also it uses modular arithmetic which prevents other shortcuts you guys try over the last months.
Why don't you believe the smartest mathematicians (yes, much smarter and more educated than you and me) that there is nothing faster than BSGS and Pollard Rho/Lambda/Kangaroo?

It's not simple math , add sub mul etc, it's use mod P, only here is mod P change, in above calc

[puzzle-dev]

I have developed a new tool to solve #66:

- ONLY CPU / highly optimized for speed and about 30% faster (on my CPU) than the fastest tool i know
- ONLY LINUX x86_64 / there is no and NEVER will be a WINDOWS/MAC version (DO NOT ASK!!!), but it may run on Windows Subsystem for Linux (WSL) / not tested
- SPECIAL SEARCH ALGORITHM/LOGIC that allows resuming search and has a higher chance to find the key (sucessfully tested on the solved puzzles!) / no stupid random or incremental search
- DUE TO LEGAL REASONS PRECOMPILED/PRECONFIGURED FOR #66 / i will release an update for #67 once #66 is solved

In short:
My tool is afaik the best option if you have access to one or more modern powerfull multicore CPUs and want to solve #66.
It still will not be easy to solve #66, but at least your chance to solve it will be higher!
All i ask you for is to split the reward (50:50) with me, if you use my tool.

If you are interested: the download link is in my profile.

NOTE: For anything regarding this tool leave me a private message! It may take some time, but i will try to answer all messages - thanks!

[citb0in]

I have developed a new tool to solve #66:

- ONLY CPU / highly optimized for speed and about 30% faster (on my CPU) than the fastest tool i know
- ONLY LINUX x86_64 / there is no and NEVER will be a WINDOWS/MAC version (DO NOT ASK!!!), but it may run on Windows Subsystem for Linux (WSL) / not tested
- SPECIAL SEARCH ALGORITHM/LOGIC that allows resuming search and has a higher chance to find the key (sucessfully tested on the solved puzzles!) / no stupid random or incremental search
- DUE TO LEGAL REASONS PRECOMPILED/PRECONFIGURED FOR #66 / i will release an update for #67 once #66 is solved

In short:
My tool is afaik the best option if you have access to one or more modern powerfull multicore CPUs and want to solve #66.
It still will not be easy to solve #66, but at least your chance to solve it will be higher!
All i ask you for is to split the reward (50:50) with me, if you use my tool.

If you are interested: the download link is in my profile.

NOTE: For anything regarding this tool leave me a private message! It may take some time, but i will try to answer all messages - thanks!

!!! WARNING !!! WARNING !!! WARNING !!!

i can only strongly and highly recommend everyone NOT to download and run this file. First turn on your mind, then think again This is a newbie user with his first entry here in the forum. He promises the panacea and the magic bullet, that is already ridiculous per se. The .RAR file contains binary executables, without insight into the source code. You do not know what these programs execute. It can be assumed that they are malicious programs that can destroy or infiltrate your entire system. For example, the program could scan your hard drive for wallets, install keyloggers or perform other undesirable RAT/Trojan functions without your knowledge.

Do not download and run this program under any circumstances !!!
This is to be considered as a warning, act with a conscious mind and at your own risk.

PS: I have reported the post to the moderator team so that no one is harmed by it.

[puzzle-dev]

@citb0in
I have also reported your post!

Yes i am new here, but my tool is absolutely safe to use!

It seems you are windows user and do not understand anything about linux and permissions.
Please try to understand this before posting false warnings and telling lies (i did not made false promises!):


- my tool does not require any dangerous permissions (like internet access or anything else)
- my tool requires only read and write permissions in the current folder (to save the current search position and the key, once it is found)

It's OK not to trust anybody, but in linux you can run tools in a sandboxed environment (and i recommend this) - this way it can not do any harm!


So, please think twice before you post such a warning and accuse people!
I worked hard to develop this tool and i want to share it with anybody who is interested to solve #66 - that's it!

I hope here are enough linux users who understand what i am talking about.

[citb0in]

It seems you are windows user and do not understand anything about linux and permissions.
Please try to understand this before posting false warnings and telling lies:


- my tool does not require any dangerous permissions (like internet access or anything else)
- my tool requires only read and write permissions in the current folder (to save the current position and the key, once it is found)

Nope, you're wrong. I'm a Linux geek. And the content of the file you're advertising is:

-rw-r--r--   1 citb0in citb0in 5,6K Jul 23 15:06 README.txt
-rwxr-xr-x   1 citb0in citb0in 1,3M Jul 23 15:06 solve66-amd-2017+*
-rwxr-xr-x   1 citb0in citb0in 1,3M Jul 23 15:06 solve66-amd-2022+*
-rwxr-xr-x   1 citb0in citb0in 1,3M Jul 23 15:06 solve66-generic*
-rwxr-xr-x   1 citb0in citb0in 1,3M Jul 23 15:06 solve66-intel-2019+*
-rwxr-xr-x   1 citb0in citb0in 1,3M Jul 23 15:06 solve66-intel-2022+*

All red marked files have been attributed by you as executable (!), PERIOD !

Code:

$ file solve66*

solve66-amd-2017+:   ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, not stripped
solve66-amd-2022+:   ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, not stripped
solve66-generic:     ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, not stripped
solve66-intel-2019+: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, not stripped
solve66-intel-2022+: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, for GNU/Linux 3.2.0, not stripped

As everyone clearly sees, those are binary executables (!).

I highly suggest to everyone NOT EXECUTE ANY OF THOSE FILE, unless you know what you're doing !

I worked hard to develop this tool and i want to share it with anybody who is interested to solve #66 - that's it!

Then publish the source code of your tool on github, gitlab, or bitbucket so anyone can see what your holy ADVERTISED tool is doing in detail. Remove the binary executables, write a readme on how to compile the program. You're on Linux, right ?

[puzzle-dev]

You can't even read...

YES, there are executables in the file, yes of course these are precompiled versions (README.txt) and if you would have read the REAME.txt you would understand why i cannot publish the sources,
but you simply don't want to understand... and there are also online virus-scanners where you could upload the executeables, but you just want to tell lies...

You are a linux geek and do not even understand what PRECOMPILED means or what a SANDBOXED environment is???

If you are a linux geek you could even boot a linux live-cd, unplug all your harddrives and network connections (if you are paranoid) and simply test my tool and you will see it does no harm at all, still all you can do is telling lies.

I just hope here are some people with a brain who like my work.

It seems i am wasting my time with you, unless some more intelligent people jump in.

You really made my day...  

[citb0in]

/IGNORE

I can highly recommend everyone to think and not to download and run executables from this user who freshly registers here on the forum and advertises the miracle cure. There is no plausible explanation why the program code should not be made public. If someone really wants to help and contribute to the community in a valuable way, he usually does so in the form of open source code. This is common practice and of course also here in the forum with all code snippets or programs in the sub-forums. So every developer can read through the code and make sure what the program does and also contribute to further develop and optimize the code. All in the interest of the community.

As far as no program code is published, it can be assumed that something is hidden and obfuscated and in the worst case even malicious functions are behind the program.

Therefore, I still insist on the warning to distance yourself from these programs and not to run them under any circumstances !

[puzzle-dev]

And again just lies... I never said i found the holy grail or promised that my tools solves #66 within a day

everything is explained in the README.txt, but he simply does not want to understand it.

For everybody else who wants to try my tool:

- use an online virus scanner on the executeables
- use a sandboxed environment or a VM or a linux live-CD to test the executeables
- then you are free to judge me


I hope somebody with a good reputation can help me against these false accusations from this paranoid guy!?
It's ok to warn people, but just not with false accusations and lies...

Thanks!

[citb0in]

Everything is said. Let the user decide. Just a few words added, following parts is contained in those binary executables:

Congratulations, you found a key! Before i can send you your reward i have to verify that it is no false positive. Please send me a private message with this text: ...

if the tool has found a key, you will never see it yourself, you will have to ask the creator of the program for "approval/activation" to get your 50% share. Just imagine the case you would never receive a reply By the way, the program also contains functions that initialize and use the network stack (strange, huh?), i.e. it is quite possible that a found key is also immediately transmitted to this dubious user via an existing network connection through an initialized TLS stack. Those who are more familiar with this and want to deal with it, I encourage them to take a look at the binary executables themselves and get a picture of it. You certainly will get the idea.

Therefore, my warning still applies --> Hands off this closed-source tool!

I have developed a new tool to solve #66:

- ONLY CPU / highly optimized for speed and about 30% faster (on my CPU) than the fastest tool i know
- ONLY LINUX x86_64 / there is no and NEVER will be a WINDOWS/MAC version (DO NOT ASK!!!), but it may run on Windows Subsystem for Linux (WSL) / not tested
- SPECIAL SEARCH ALGORITHM/LOGIC that allows resuming search and has a higher chance to find the key (sucessfully tested on the solved puzzles!) / no stupid random or incremental search
- DUE TO LEGAL REASONS PRECOMPILED/PRECONFIGURED FOR #66 / i will release an update for #67 once #66 is solved

In short:
My tool is afaik the best option if you have access to one or more modern powerfull multicore CPUs and want to solve #66.
It still will not be easy to solve #66, but at least your chance to solve it will be higher!
All i ask you for is to split the reward (50:50) with me, if you use my tool.

If you are interested: the download link is in my profile.

NOTE: For anything regarding this tool leave me a private message! It may take some time, but i will try to answer all messages - thanks!

[puzzle-dev]

and here again you are posting false accusations

if you quote my README.txt you should also quote this:

BY USING THIS TOOL YOU AGREE TO SPLIT THE REWARD 50:50 WITH ME IF YOU FIND THE KEY. IF YOU DO NOT AGREE THEN USE OTHER TOOLS - THANKS!

and if a key is found:

Congratulations, you found a key!
Before i can send you your reward i have to verify that it is no false positive.
Please send me a private message with this text:
---
verify: _..._
wallet: YOUR WALLETADDRESS FOR THE REWARD
---

It was hard to develop this tool, so i have to make sure i get my share by verifying the key otherwise the user could just use the key and run - you see the problem?
Do you think #120 and #125 was solved with tools the guy/s have developed on their own? i don't think so! And how much did the developer of the tool they used get?

It's all about trust... you don't trust me, but i should  trust the users? we are talking about a big reward and months of work!

Of course the user has to trust me that i do not take the money and run - that's right, but think about this:
would this be wise from my point of view? NO, we have #67 and more to come, so i am very interested that whoever finds the key gets his share and uses my tool again to find the next key and i get again 50% of the reward.
If i would take the money and run i could do it only once... this would be very stupid.

I can only repeat:
my tool does not require internet permission - the key is just saved to a text file. why would i ask the user to send me message if i would send the found key over internet to me? and why would i ask for the users wallet, if my intention would be to take the money and run? so, most of your accusations are not very logical.
The TLS stuff comes from the linked libgmpxx.a which was build by compiling libgmp.a, so i linked it (i have to admit this is strange, but libgmpxx.a is not part of my code - i will have to check if libgmp.a really requires it, if not i will remove it)

As we are talking about trust and false warnings:
Why don't you warn people using the pool that is advertised here? It also includes precompiled executeables for windows and linux and unlike my tool the keys and ranges are send to a server... so to all you guys contributing to the pool: bad news - you have to trust the guy who runs the server (also a newbie), but i don't say that you cannot trust him an he will run once a key is found, but it's almost the same problem (even bigger, as internet permission is required), so it is quite strange that you talk only about my tool and not about the pool.

So i repeat:My tool works as advertised (the chance to find a key is afaik higher than with any other CPU tool i have tested) and i do not intend to run, if a key is found.
I really hope someone here here will use it and find the key - just to proof that it works and citb0in is wrong with his assumptions about me and my intentions.


I just want to get a share of the reward as a compensation for my hard work!
If you don't trust me or don't want to share the reward 50:50 then simply don't use my tool, but in this case you should also not use any pools and you should always use only open source tools you checked and compiled yourself! Or do you think precompiled executeables from github without sourcecode are more trustworthy than my tool? i guess not!

[FASTPROFITTRADER]

I'm making a 50$ contest

[digaran]

I have developed a new tool to solve #66:

- ONLY CPU / highly optimized for speed and about 30% faster (on my CPU) than the fastest tool i know
- ONLY LINUX x86_64 / there is no and NEVER will be a WINDOWS/MAC version (DO NOT ASK!!!), but it may run on Windows Subsystem for Linux (WSL) / not tested
- SPECIAL SEARCH ALGORITHM/LOGIC that allows resuming search and has a higher chance to find the key (sucessfully tested on the solved puzzles!) / no stupid random or incremental search
- DUE TO LEGAL REASONS PRECOMPILED/PRECONFIGURED FOR #66 / i will release an update for #67 once #66 is solved

In short:
My tool is afaik the best option if you have access to one or more modern powerfull multicore CPUs and want to solve #66.
It still will not be easy to solve #66, but at least your chance to solve it will be higher!
All i ask you for is to split the reward (50:50) with me, if you use my tool.

If you are interested: the download link is in my profile.

NOTE: For anything regarding this tool leave me a private message! It may take some time, but i will try to answer all messages - thanks!

Speed? No benchmark? We already have GPU enabled tools which are 20 to 30 times faster than CPU versions, I don't know what you are promising, but definitely your tool is not faster than others whatsoever, besides searching with CPU is useless.

[puzzle-dev]

Speed? No benchmark? We already have GPU enabled tools which are 20 to 30 times faster than CPU versions, I don't know what you are promising, but definitely your tool is not faster than others whatsoever, besides searching with CPU is useless.

You can benchmark it for yourself:
- run the fastest CPU tool you know and compare the keyrate with my tool!
On my slow CPU i get about 30% more speed (now i get about 2.6 million keys/s on one core), but the speedgain may be different on other CPUs - hard to say. I would be happy if some users would post keyrates of their CPUs.

I never talked about GPUs and said that my tool can compete with them - of course GPUs are faster, but not everybody (like me) has access to a fast GPU, but some people here may have access to fast multicore CPUs and using several cores of a modern CPU could give in total a quite good rate, even if a GPU may still be faster. All i say is that my approach/logic for searching is different and that i took a big effort in improving speed for CPUs - that's it.

Solving #66 requires not only speed, it also requires luck and with luck even a slow CPU could solve #66 - unlikely, but possible - in the end it's more lotto than a puzzle  

So, if you have a fast GPU then you should use it and in this case my tool is of course not helpfull for you at all.

[ripemdhash]

Never ever run anything compiled by unknown individuals without the possibility of inspecting the source code. Never trust individuals who include "forcing" the sending of a private key in file contents, no matter how it sounds. Never run it on an instance where you have your own wallet, preferably on a VM instance without internet access, and in general, compiled programs without source code should be automatically blocked.

[modma]

I have developed a new tool to solve #66:

- ONLY CPU / highly optimized for speed and about 30% faster (on my CPU) than the fastest tool i know
- ONLY LINUX x86_64 / there is no and NEVER will be a WINDOWS/MAC version (DO NOT ASK!!!), but it may run on Windows Subsystem for Linux (WSL) / not tested
- SPECIAL SEARCH ALGORITHM/LOGIC that allows resuming search and has a higher chance to find the key (sucessfully tested on the solved puzzles!) / no stupid random or incremental search
- DUE TO LEGAL REASONS PRECOMPILED/PRECONFIGURED FOR #66 / i will release an update for #67 once #66 is solved

30 percent faster than what? Can I have a specific example?
you are talking about an increased chance of searching - how is this statement justified?
PS do not install code from an unknown source.