Quote
char b1[] = "0";
Did you try starting with one? 0 * G is a special case for the scalar multiply over the point group so try starting with one instead.
Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 251. (Read 190789 times)
0 * G is a special case for the scalar multiply over the point group so try starting with one instead.
hey....you guys, the world of btc that unfolds before me everyday is still quite baffling, at least on the mining and coding side of it.
i've read most of this thread and am absolutely mesmerized by everyone's knowledge of the inner workings of things
i would love to be up to par with everyone on this. so who wants to tutor me and/or provide a link to something that explains
more in-depth?
i've read most of this thread and am absolutely mesmerized by everyone's knowledge of the inner workings of things
i would love to be up to par with everyone on this. so who wants to tutor me and/or provide a link to something that explains
more in-depth?
So I am trying to get the initial private key set to = 0; so I can do the search in sequential form, however its very difficult in oclvanitygen.
Basically I replaced
EC_KEY_generate_key(pkey);
with
char b1[] = "0";
BN_dec2bn(&res,b1);
EC_KEY_set_private_key(pkey, res)
However I keep getting the core segmentation fault error, probably something to do with the pointers.
Another issue is setting the rekey interval higher
const BN_ULONG rekey_max = 10000000;
BN_ULONG npoints, rekey_at, nbatch;
Setting rekey_max to like 999999999999999 doesnt seem to work because every private key generated doesn't look sequential with the previous.
Basically I replaced
EC_KEY_generate_key(pkey);
with
char b1[] = "0";
BN_dec2bn(&res,b1);
EC_KEY_set_private_key(pkey, res)
However I keep getting the core segmentation fault error, probably something to do with the pointers.
Another issue is setting the rekey interval higher
const BN_ULONG rekey_max = 10000000;
BN_ULONG npoints, rekey_at, nbatch;
Setting rekey_max to like 999999999999999 doesnt seem to work because every private key generated doesn't look sequential with the previous.
I got a bunch of old GPUs that can't mine ETH or ZEC and for fun I am thinking of trying to solve the 50th bit with brute force.
However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
You should read this thread and consider participating in the pooled search effort:However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
https://bitcointalksearch.org/topic/large-bitcoin-collider-collision-finders-pool-1573035
It looks like you can configure your system to search just the 251 - 252 private key address space (where then next payout will be):
https://bitcointalksearch.org/topic/m.16338052
This pooled effort is sequentially searching the key space. They have already re-found almost all the puzzle transactions, see this page:
https://lbc.cryptoguru.org/trophies
I got a bunch of old GPUs that can't mine ETH or ZEC and for fun I am thinking of trying to solve the 50th bit with brute force.
However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
If you have a hard time mining Ethereum using GPU then the best way and the most easy way is to register and download minergate. I am not advertising minergate but since it is the easiest way to mine ethereum I am sharing this to you. BUt with regards to ZEC I have no site to recommend to you. You can try my recommendation to find out if its a good option or not.
You should learn to read before you post.
I got a bunch of old GPUs that can't mine ETH or ZEC and for fun I am thinking of trying to solve the 50th bit with brute force.
However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
If you have a hard time mining Ethereum using GPU then the best way and the most easy way is to register and download minergate. I am not advertising minergate but since it is the easiest way to mine ethereum I am sharing this to you. BUt with regards to ZEC I have no site to recommend to you. You can try my recommendation to find out if its a good option or not.
I got a bunch of old GPUs that can't mine ETH or ZEC and for fun I am thinking of trying to solve the 50th bit with brute force.
However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
However how can I get the oclvangen program to start at 1,125,899,906,842,620 instead of using random numbers and go in order.
With the GPUs I got it should take about 15 days or so...
https://blockchain.info/tx/39553513f731ae20f98f3307e863f0aecee9842f22273bb2ddfc0fb6ba481c5e
Why 47~50 transactions happen together?
Is someone know all private key?
Read the thread before you post. Why 47~50 transactions happen together?
Is someone know all private key?
https://blockchain.info/tx/39553513f731ae20f98f3307e863f0aecee9842f22273bb2ddfc0fb6ba481c5e
Why 47~50 transactions happen together?
Is someone know all private key?
Why 47~50 transactions happen together?
Is someone know all private key?
https://lbc.cryptoguru.org/trophies
The pool found a private key to 8661cb56d9df0a61f01328b55af7e56a3fe7a2b2 (1DFYhaB2J9q1LLZJWKTnscPWos9VBqDHzv) as 0xade6d7ce3b9b. At the time of the find, there were 0 BTC on that address. This is #48 of the puzzle transaction.
Rico
LBC found 38-467 so far.
Let's be precise here.
Rico
PokerFace3 @ Have you reached your daily spam quota yet?
Oh nice. I didn't know there was a thread about this.
If I understand his posting correctly Ryan has the keys for 1-37, LBC found 38-46 so far. (and some guys up to 50, although they evidently didn't search the whole search space as LBC does)
I also think there is no pattern, it's just random keys of given length. Some early warning system or security demonstration as you say.
Rico
This is seroius, lets see who can win this huge amount of bitcoin. I wish I could win this huge amount so I can be the richest bitcoin millionaire or so. Lets see who could solve this puzzle and then we could call the person a genius. But, instead of struggling with it and ending up in disappointment, I will just focus on my regular job to have some peace of mind at least. LBC just found 38-42 of the puzzle transaction: http://lbc.cryptoguru.org:5000/trophies
I am keeping record of all of them in hopes to find a pattern.
I don't think there is a pattern or that this is even a puzzle. I think it's just a demonstration of security based on bit length of the PK.
I am keeping record of all of them in hopes to find a pattern.
I don't think there is a pattern or that this is even a puzzle. I think it's just a demonstration of security based on bit length of the PK.
If I understand his posting correctly Ryan has the keys for 1-37, LBC found 38-46 so far. (and some guys up to 50, although they evidently didn't search the whole search space as LBC does)
I also think there is no pattern, it's just random keys of given length. Some early warning system or security demonstration as you say.
Rico
Oh nice. I didn't know there was a thread about this.
If I understand his posting correctly Ryan has the keys for 1-37, LBC found 38-46 so far. (and some guys up to 50, although they evidently didn't search the whole search space as LBC does)
I also think there is no pattern, it's just random keys of given length. Some early warning system or security demonstration as you say.
Rico
LBC just found 38-42 of the puzzle transaction: http://lbc.cryptoguru.org:5000/trophies
I am keeping record of all of them in hopes to find a pattern.
I don't think there is a pattern or that this is even a puzzle. I think it's just a demonstration of security based on bit length of the PK.
I am keeping record of all of them in hopes to find a pattern.
I don't think there is a pattern or that this is even a puzzle. I think it's just a demonstration of security based on bit length of the PK.
If I understand his posting correctly Ryan has the keys for 1-37, LBC found 38-46 so far. (and some guys up to 50, although they evidently didn't search the whole search space as LBC does)
I also think there is no pattern, it's just random keys of given length. Some early warning system or security demonstration as you say.
Rico
Looks like all the transactions through 50 bits have been claimed and the 51 bit key has still not been claimed:
https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15
It is impossible to get all the rewards.
It is possible to get the next reward (0.051 BTC) in the sequence.
There are only 1,125,899,906,842,620 possible keys for the next unclaimed reward of 0.051 BTC.
At your rate of 5,000,000,000,000 trial per second it would only take a bit over 225 seconds to try all of them.
There is no hope of getting all the remaining rewards but it should be totally possible to get a few more small rewards from the sequence.
https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15
It is impossible to get all the rewards.
It is possible to get the next reward (0.051 BTC) in the sequence.
There are only 1,125,899,906,842,620 possible keys for the next unclaimed reward of 0.051 BTC.
At your rate of 5,000,000,000,000 trial per second it would only take a bit over 225 seconds to try all of them.
There is no hope of getting all the remaining rewards but it should be totally possible to get a few more small rewards from the sequence.
LBC just found 38-42 of the puzzle transaction: http://lbc.cryptoguru.org:5000/trophies
I am keeping record of all of them in hopes to find a pattern.
I don't think there is a pattern or that this is even a puzzle. I think it's just a demonstration of security based on bit length of the PK.
Thanks,
Jude
Looks like all the transactions through 50 bits have been claimed and the 51 bit key has still not been claimed:
https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15
It is impossible to get all the rewards.
It is possible to get the next reward (0.051 BTC) in the sequence.
There are only 1,125,899,906,842,620 possible keys for the next unclaimed reward of 0.051 BTC.
At your rate of 5,000,000,000,000 trial per second it would only take a bit over 225 seconds to try all of them.
There is no hope of getting all the remaining rewards but it should be totally possible to get a few more small rewards from the sequence.
https://blockchain.info/tx/08389f34c98c606322740c0be6a7125d9860bb8d5cb182c02f98461e5fa6cd15
It is impossible to get all the rewards.
It is possible to get the next reward (0.051 BTC) in the sequence.
There are only 1,125,899,906,842,620 possible keys for the next unclaimed reward of 0.051 BTC.
At your rate of 5,000,000,000,000 trial per second it would only take a bit over 225 seconds to try all of them.
There is no hope of getting all the remaining rewards but it should be totally possible to get a few more small rewards from the sequence.
Does anyone have the PK for number 41 and 42?
Thanks,
Jude
Thanks,
Jude
I have the formula:
y = 2n-1 + [rand() MOD (2n-1)]
[edit] or rather:
y = 2n-1 + [rand() MOD 2n-1]
[edit] or rather:
y = 2n-1 + [rand() MOD 2n-1]
Trolling ftw.
I have the formula:
y = 2n-1 + [rand() MOD (2n-1)]
[edit] or rather:
y = 2n-1 + [rand() MOD 2n-1]
[edit] or rather:
y = 2n-1 + [rand() MOD 2n-1]
Quote
This tx is weekly faucet payment to poor captcha solvers. Nothing interesting.lol.
Great, thanks, to whoever was generous enough to give me some faucet returns.
Nothing to see here then I believe.
Back to the formula... no one found anything useful yet?
Jump to: