Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 191. (Read 229859 times)

Thank you very much for this code.
i will study the code further to understand how it works as I'm still a newbie in this but learning is my thing. thanks a lot.

You can understand how it works by looking at the code.

https://github.com/albertobsd/ecctools

I keep asking myself how that works but  always get very confused too. If there were an alleged calculator you could prescribe and a little bit of some explanation as to how the addition and subtraction works it'd be very understandable. I even tried to write a code to add and multiply below is the code. still all I got was an awkward result.

"import argparse
import ecdsa
from ecdsa.ellipticcurve import Point

# Function ato perform point addition
def point_addition(point1, point2):
    return point1 + point2

# Function to perform point subtraction
def point_subtraction(point1, point2):
    return point1 - point2

# Function to perform point multiplication
def point_multiplication(point, scalar):
    return scalar * point

# Function to perform point division (using scalar multiplication by the inverse)
def point_division(point, scalar):
    return point_multiplication(point, ecdsa.numbertheory.inverse_mod(scalar, curve.order()))

# Parse command-line arguments
parser = argparse.ArgumentParser(description="Elliptic Curve Point Operations")
parser.add_argument("-p1", dest="public_key1", type=str, help="Public key 1 (in hexadecimal)")
parser.add_argument("-p2", dest="public_key2", type=str, help="Public key 2 (in hexadecimal)")
parser.add_argument("operation", choices=["+", "-", "*", "/"], help="Operation to perform (+ for add, - for subtract, * for multiply, / for divide)")

args = parser.parse_args()

# Define the elliptic curve parameters (SECP256k1 in Bitcoin)
curve = ecdsa.SECP256k1

# Parse the public keys from the command-line arguments
public_key1 = ecdsa.VerifyingKey.from_string(bytes.fromhex(args.public_key1), curve=curve).pubkey.point
public_key2 = ecdsa.VerifyingKey.from_string(bytes.fromhex(args.public_key2), curve=curve).pubkey.point

# Perform the specified operation on the public keys
if args.operation == "+":
    result_point = point_addition(public_key1, public_key2)
elif args.operation == "-":
    result_point = point_subtraction(public_key1, public_key2)
elif args.operation == "*":
    scalar = int(input("Enter the scalar value (private key): "), 16)
    result_point = point_multiplication(public_key1, scalar)
elif args.operation == "/":
    scalar = int(input("Enter the scalar value (private key): "), 16)
    result_point = point_division(public_key1, scalar)

# Print the coordinates of the result point
result_x, result_y = ecdsa.util.number_to_string(result_point.x(), curve.order), ecdsa.util.number_to_string(result_point.y(), curve.order)
print("Result Point (x, y):", result_x.hex(), ",", result_y.hex())" result was awkward but anyway,

how do we go about the addition and subtraction, division and multiplication and how do we make sense off of the result from this process??
what tools are required?
Calculators and procedures involved. I'm down to learn too

Nvidia GPU, also not open source, modified version of 2 different tools.
https://bitcointalksearch.org/topic/m.56699222

Bitcrack :
https://bitcointalksearch.org/topic/bitcrack-a-tool-for-brute-forcing-private-keys-4453897

I'd suggest to dive into the ocean of public keys, learn how to add/subtract/divide, your chance of success is better than brute forcing for keys.

Hello, all.
Hope you are doing well.
I am new to here, and would like to attend this puzzle.
What tool can I use in my pc(Windows10)?

Thanks

Did you just use good cop, bad cop method on him? Lol.
If he wanted to share the code, he'd have done it at the first place and nobody would have attacked him.

In case some of you haven't noticed, around these woods we paint toads and sell them as porsche!

Personally I have nothing against him, I know enough not to run the tool, even if I do I have nothing of value on my system.
Besides, his tool, your tool, my tool, none of them really help unless you have 100+ GPUs, then having that many GPUs, you wouldn't go for #66, you'd use them to search for #130. So if we are talking about "luck" searching a site like keys.lol should do the trick, if it's up to your "luck" clicking on page numbers is enough or buying a lottery ticket could also give a better result. Being "lucky" is not exclusive to finding a puzzle key, So your and his argument is not reasonable.

Guys, stop the hate and the harassment of him!

Yes there's a doubt; The "Developer" could be suspected; Yes it could be a scam; Yes it could have a trojan; But it could be also real!

It's just a doubt, you are guys acting like he's 100% fake and scammer which is of course not the case! Nobody knows if he's real or not, but at least you could've friendly just asked him to upload his source code to GitHub instead of attacking him like this! What if he's real? You can't imagine how bad he will feel. You guys are hurting him so stop it please! We don't know if he's real or not, so we can't judge him that early!!

Maybe he's real and really developed a tool for CPU users for help. Who knows? And yes, it's his right for him to ask for 50% since he is the developer of it.

@puzzle-dev We apologize for that, but we are a sensitive community, so please we respectfully ask you to upload its source code just incase for us to be in the safe side.

Thanks,

Why don't you share this different approach in details with the rest of us? If it was working, you wouldn't be here talking, instead you'd have rented hundreds of CPUs to find #66.

Thanks for your trust and reply!

I don't know if it helps to gain more trust, but i updated the tool, removed the executeable permissions and included a warning about running binaries from unknown sources in the README.txt and added some hints how to run binaries if you do not trust the developer. Actually there are serveral tools on github where binaries are included (like iceland and the pool) and there are no sources available for these tools available, so i don't see a big difference if i would use github. I do not exspect anybody to trust me, but at least to be fair. i just offer a different approach an my tool is quite fast on CPUs and it would be very interesting to see the keyrates on modern CPUs.

I downloaded them this morning and ran them through the online scanner and they were all clean. Ran the generic on wsl and it worked 1 thread as about 2 mil/second older Xeon it seems to make a file that is either a checkpoint or remembers the addresses tried or both. works well but since I paid for a rtx GPU and made a control program so it runs unattended I am going to use that, but for CPU users it should be ok. Suggestion: put them on github and maybe others will be more comfortable then being on a file share website which makes others a little suspicious. you can open a free account there.

online scanner Lol, to bypass all antivirus you only need tools like pyarmor and other techniques that I will not mention for the sake of honest people.

very strange argument.
Next time, tell me about new mathematics right away.

This is my last reply regarding useless speed comparisions:


you simply have to compare the speed of my tool with your prefered tool on your own!!!
MY TOOL IS FOR CPU *NOT* FOR GPU - GPUs ARE FASTER - I KNOW IT - EVERYBODY KNOWS IT!


i just gave you a number for my very slow CPU and only on one core and this is a mobile CPU! This does not say anything about keyrates on your CPU!
if your prefered tool is faster, then use it and be happy with it! On my CPU my tool is faster - is this so hard to understand?

only through tests...
i run competiton tests between my tool and other CPU tools and my tool always found the key faster, so i guess my search logic works somehow better than a simple random search, but you cannot exspect miracles like a 10x speed improvement.

what cave did you come out of?
KEYHUNT by alberto 4 million keys per stream.
bitcrack 3 million keys per stream.
I personally have GPU generation - 4 billion keys per second.
And this is in open source - which the developers provided for free.

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.

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.

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.

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.

I'm making a 50$ contest