Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
@nomachine
Can you tell me parameters inside your code for puzzle 135?
I understand that:
puzzle = 135
compressed_public_key = "02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16"
But what about kangaroo_power = 6? Can I rise it? Should I?
I am not asking about chances here which can be far below puzzle 50 or 71.
The cloud computer is 512 threads (2 times 128 cores/256 threads CPUs).
Can you tell me parameters inside your code for puzzle 135?
I understand that:
puzzle = 135
compressed_public_key = "02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16"
But what about kangaroo_power = 6? Can I rise it? Should I?
I am not asking about chances here which can be far below puzzle 50 or 71.
The cloud computer is 512 threads (2 times 128 cores/256 threads CPUs).
First change:
#Random seed Config
constant_prefix = b'' #back to no constant - need to be b''
prefix_length = len(constant_prefix)
length = 20
rest of code....
# Configuration for the puzzle
puzzle = 135
compressed_public_key = "02145d2611c823a396ef6712ce0f712f09b9b4f3135e3e0aa3230fb9b6d08d1e16"
lower_range_limit = 2 ** (puzzle - 1)
upper_range_limit = (2**puzzle) - 1
kangaroo_power = 8
Initially, try with kangaroo_power = 8. Ideally, it should be around puzzle / 10 (approximately 13), but computing the point table takes 15–20 minutes. Cross your fingers that one of the 256 cores randomly lands close to the X and Y coordinates.
