So, LBC is going through first 160 bits of 256? But Rico says it is not.
https://lbc.cryptoguru.org/stats
actually 134.58 bits
Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 282. (Read 207440 times)
https://lbc.cryptoguru.org/stats
actually 134.58 bits
So, LBC is going through first 160 bits of 256? But Rico says it is not.
It exhausts each sequential search space, its not brute forcing the whole range
Thanks for the answer! And what's the magic of extracting 2^160 from 2^256? That's totally unclear
adr1 = ripemd160(sha256(pubkey(rand(2^256-2^160)+2^160)))
this line makes no sense to me
2^256 is from 1 to 115792089237316195423570985008687907853269984665640564039457584007913129639936.
2^160 is from 1 to 1461501637330902918203684832716283019655932542976
But the sha256-hash of LONG==1 is almost in the end of 2^256
48635463943209834798109814161294753926839975257569795305637098542720658922315
LONG==1461501637330902918203684832716283019659932542976 (around 2^161 ) is also near hash of 1.
So, if LBC is not going sequentally from PK == 1 to 2^256, does it really solve this puzzle?!
Example it cracks keys like this:
00001
000011
0000111
00001000
000010101
0000110001
00001001100
000011100000
0000111010011
00001000000010
000010010000011
0000101001111011
00001010001100000
000010100100110000
0000110100011110011
00001100100100110110
000010111011001001111
0000110000100000001101
00001010111010010011111
000011010010110001010101
0000110111010010100110100
00001011011110010000001111
000010101010110111001010010
0000110111000010101000000100
and so on
It exhausts each sequential search space, its not brute forcing the whole range
Thanks for the answer! And what's the magic of extracting 2^160 from 2^256? That's totally unclear
adr1 = ripemd160(sha256(pubkey(rand(2^256-2^160)+2^160)))
this line makes no sense to me
2^256 is from 1 to 115792089237316195423570985008687907853269984665640564039457584007913129639936.
2^160 is from 1 to 1461501637330902918203684832716283019655932542976
But the sha256-hash of LONG==1 is almost in the end of 2^256
48635463943209834798109814161294753926839975257569795305637098542720658922315
LONG==1461501637330902918203684832716283019659932542976 (around 2^161 ) is also near hash of 1.
So, if LBC is not going sequentally from PK == 1 to 2^256, does it really solve this puzzle?!
Hey, guys!
Please, anyone can explain how do you predict when LBC will find the key?
I've read (lbc.cryptoguru.org/man/theory) several times, but do not understand that pseudo code (I'm programmer, but noob in crypto)
The point I do not get completely: rico claims that they do not brute 2^256 range, because it is too large and do some hack to make range 2^159.
I of course understand that after sha256 we get a compression of range. But shouldn't sets 2^256 and 2^159 overlap chaotically? So how LBC chooses the right keys from 2^256 that map to unique addresses in 2^159 ?
For solving this puzzle shouldn't LBC brute 2^256 range ?!
Please, anyone can explain how do you predict when LBC will find the key?
I've read (lbc.cryptoguru.org/man/theory) several times, but do not understand that pseudo code (I'm programmer, but noob in crypto)
The point I do not get completely: rico claims that they do not brute 2^256 range, because it is too large and do some hack to make range 2^159.
I of course understand that after sha256 we get a compression of range. But shouldn't sets 2^256 and 2^159 overlap chaotically? So how LBC chooses the right keys from 2^256 that map to unique addresses in 2^159 ?
For solving this puzzle shouldn't LBC brute 2^256 range ?!
It exhausts each sequential search space, its not brute forcing the whole range
This is still going on.
GL
GL
Hey, guys!
Please, anyone can explain how do you predict when LBC will find the key?
I've read (lbc.cryptoguru.org/man/theory) several times, but do not understand that pseudo code (I'm programmer, but noob in crypto)
The point I do not get completely: rico claims that they do not brute 2^256 range, because it is too large and do some hack to make range 2^159.
I of course understand that after sha256 we get a compression of range. But shouldn't sets 2^256 and 2^159 overlap chaotically? So how LBC chooses the right keys from 2^256 that map to unique addresses in 2^159 ?
For solving this puzzle shouldn't LBC brute 2^256 range ?!
Please, anyone can explain how do you predict when LBC will find the key?
I've read (lbc.cryptoguru.org/man/theory) several times, but do not understand that pseudo code (I'm programmer, but noob in crypto)
The point I do not get completely: rico claims that they do not brute 2^256 range, because it is too large and do some hack to make range 2^159.
I of course understand that after sha256 we get a compression of range. But shouldn't sets 2^256 and 2^159 overlap chaotically? So how LBC chooses the right keys from 2^256 that map to unique addresses in 2^159 ?
For solving this puzzle shouldn't LBC brute 2^256 range ?!
Don't fully understand but ok.
LBC is going to start finding the 55th key in a few hours.
With 3GH/s should take around ~37 days
0.55 BTC plus BCH plus BTG yields around
~0.66 BTC = $8,500
Basically about 2x as profitable as regular ETH mining with a RX470/570 if you can find it in 37 days and not closer to the end around 74 days.
With 3GH/s should take around ~37 days
0.55 BTC plus BCH plus BTG yields around
~0.66 BTC = $8,500
Basically about 2x as profitable as regular ETH mining with a RX470/570 if you can find it in 37 days and not closer to the end around 74 days.
is it going to find the 55th key or start finding it in a few hours?
LBC is going to start finding the 55th key in a few hours.
With 3GH/s should take around ~37 days
0.55 BTC plus BCH plus BTG yields around
~0.66 BTC = $8,500
Basically about 2x as profitable as regular ETH mining with a RX470/570 if you can find it in 37 days and not closer to the end around 74 days.
With 3GH/s should take around ~37 days
0.55 BTC plus BCH plus BTG yields around
~0.66 BTC = $8,500
Basically about 2x as profitable as regular ETH mining with a RX470/570 if you can find it in 37 days and not closer to the end around 74 days.
Y'all gave up yet.....
Haha, this reminds me of https://www.funnyvideosapp.com/watch/
You are wasting your time. The person who created the puzzle has already posted exactly how he did it. It is random. You will not find a pattern to predict the private keys.
We should find a solution instead of brute forcing. What do you think?
The newest approach is very promising. As a basis we use the binaries of the private keys in a descending order and a special cellular automaton:
██░░█░░█░░██░██░
██░█░░░████░░██
█░█░░█░░██░░░░
█░█░░░██░░░░░
█░█░░████░██
█░░█░░░░░██
█░░░░░░░█░
███░█░░██
███░░░░░
█░░██░░
██░░░█
█░█░█
█░░░
███
██
█
Cellular Automaton:
Input: ██░ █░█ ░█░ █░░ ░░░ ░░█ ░██ ███ ░░█ ░██
Output: ██░ █░█ ░█░ █░░ ░░░ ░░█ ░██ ███ ░░█ ░██
The automaton speciality is that there isn't one static rule for the output, but the output depends on how often the rule has been executed before (same column). One big hint that someone has come up with this is: All the rules in- and outputs are the same!!
Example (See beginning of first row -> second row):
██░
█
██░ => █ because the function is executed the (3 % x = 1) th time
then second -> third:
██░ => ░ because the function is executed the (3 % x = 2) th time
██░
░
When you double check the results with 6 digit US patents ( US137821, US497622 !!! ) you see where this leads to ...
Keep up the good work!
...
https://1trash.github.io/
The newest approach is very promising. As a basis we use the binaries of the private keys in a descending order and a special cellular automaton:
██░░█░░█░░██░██░
██░█░░░████░░██
█░█░░█░░██░░░░
█░█░░░██░░░░░
█░█░░████░██
█░░█░░░░░██
█░░░░░░░█░
███░█░░██
███░░░░░
█░░██░░
██░░░█
█░█░█
█░░░
███
██
█
Cellular Automaton:
Input: ██░ █░█ ░█░ █░░ ░░░ ░░█ ░██ ███ ░░█ ░██
Output: ██░ █░█ ░█░ █░░ ░░░ ░░█ ░██ ███ ░░█ ░██
The automaton speciality is that there isn't one static rule for the output, but the output depends on how often the rule has been executed before (same column). One big hint that someone has come up with this is: All the rules in- and outputs are the same!!
Example (See beginning of first row -> second row):
██░
█
██░ => █ because the function is executed the (3 % x = 1) th time
then second -> third:
██░ => ░ because the function is executed the (3 % x = 2) th time
██░
░
When you double check the results with 6 digit US patents ( US137821, US497622 !!! ) you see where this leads to ...
Keep up the good work!
...
https://1trash.github.io/
I can sweep for you keys in the future only from the 32btc contest. So for the 55bit key and so forth. I can't sweep any other address due to the fact that it might belong to someone.
Its really not that difficult. For Bitcore you just download their wallet with the included blockchain (300mb) and it syncs quick since their blockchain is mostly empty and just go to Debug and put in "importprivkey XXXXX" and you are all set. You can sell on Crytopia.
For BitcoinGold I just used the Coinomi app from the Android app store. Just build a new wallet and there is an option there to sweep a BitcoinGold address.
Thanks for letting me keep the funds, I will keep half and donate the other half to your LBC Pot. As soon as either Poloniex or Bitfinex allows BitcoinGold deposits.
Its really not that difficult. For Bitcore you just download their wallet with the included blockchain (300mb) and it syncs quick since their blockchain is mostly empty and just go to Debug and put in "importprivkey XXXXX" and you are all set. You can sell on Crytopia.
For BitcoinGold I just used the Coinomi app from the Android app store. Just build a new wallet and there is an option there to sweep a BitcoinGold address.
Thanks for letting me keep the funds, I will keep half and donate the other half to your LBC Pot. As soon as either Poloniex or Bitfinex allows BitcoinGold deposits.
Sure - all of what you said goes d'accord with our stab at it - limited to the puzzle transactions it shall be.
It's just that we do only care about the BTC as that is where the project started off. So transferring the funds to a custodial address then publishing the privkey refers to BTC only and means the forks become at the time of publishing the privkey accessible to everybody else.
NOT OUR PROBLEM. I might add.
So by transferring these also to custodial addresses, you would actually save them for their rightful owners, because we do not care.
Also we certainly know technically how to sweep the funds, but the hassle of another blockchain and another exchange-account seems not worth it.
I sweeped both your BitCore and BitcoinGold funds before somebody else got to it. Post a BitCore and BitcoinGold address in this thread and I will send them back to you.
Here are those transaction ids
https://chainz.cryptoid.info/btx/tx.dws?172551.htm
http://btgexp.com/tx/f78617a5e6bf438c7a310639f6d8fe10c194a74be6ac98b2c329024a4d1df745
EDIT: Please post your addresses where you want the coins sent in the 32btc contest thread since its unmoderated.
Here are those transaction ids
https://chainz.cryptoid.info/btx/tx.dws?172551.htm
http://btgexp.com/tx/f78617a5e6bf438c7a310639f6d8fe10c194a74be6ac98b2c329024a4d1df745
EDIT: Please post your addresses where you want the coins sent in the 32btc contest thread since its unmoderated.
Thank you for the noble offer, but it seems not worth the hassle to go for every BTC fork. (We didn't even claim Bitcoin Cash).
If you want to support the project - which would be greatly appreciated - you can keep both BitCore and BitcoinGold funds you sweeped and transfer whatever you deem appropriate to the LBC Pot (https://blockchain.info/address/1LBCPotwPzBvBcTtd7ADGzCWPXXsZE19j6).
Thank you.
If this "mode of operation" is ok for you, feel free to send me an email address via PM, we could inform you in advance of private keys found, so you could see if you can process the BitCore and BitcoinGold attached to them.
I can sweep for you keys in the future only from the 32btc contest. So for the 55bit key and so forth. I can't sweep any other address due to the fact that it might belong to someone.
Its really not that difficult. For Bitcore you just download their wallet with the included blockchain (300mb) and it syncs quick since their blockchain is mostly empty and just go to Debug and put in "importprivkey XXXXX" and you are all set. You can sell on Crytopia.
For BitcoinGold I just used the Coinomi app from the Android app store. Just build a new wallet and there is an option there to sweep a BitcoinGold address.
Thanks for letting me keep the funds, I will keep half and donate the other half to your LBC Pot. As soon as either Poloniex or Bitfinex allows BitcoinGold deposits.
I sweeped both your BitCore and BitcoinGold funds before somebody else got to it. Post a BitCore and BitcoinGold address in this thread and I will send them back to you.
Here are those transaction ids
https://chainz.cryptoid.info/btx/tx.dws?172551.htm
http://btgexp.com/tx/f78617a5e6bf438c7a310639f6d8fe10c194a74be6ac98b2c329024a4d1df745
EDIT: Please post your addresses where you want the coins sent in the 32btc contest thread since its unmoderated.
Here are those transaction ids
https://chainz.cryptoid.info/btx/tx.dws?172551.htm
http://btgexp.com/tx/f78617a5e6bf438c7a310639f6d8fe10c194a74be6ac98b2c329024a4d1df745
EDIT: Please post your addresses where you want the coins sent in the 32btc contest thread since its unmoderated.
Thank you for the noble offer, but it seems not worth the hassle to go for every BTC fork. (We didn't even claim Bitcoin Cash).
If you want to support the project - which would be greatly appreciated - you can keep both BitCore and BitcoinGold funds you sweeped and transfer whatever you deem appropriate to the LBC Pot (https://blockchain.info/address/1LBCPotwPzBvBcTtd7ADGzCWPXXsZE19j6).
Thank you.
If this "mode of operation" is ok for you, feel free to send me an email address via PM, we could inform you in advance of private keys found, so you could see if you can process the BitCore and BitcoinGold attached to them.
Cross posting this
Congrats on finding the private key. I don't think you know but you can also claim BitCore and Bitcoin GOLD with that private key. I see you or somebody already claimed Bitcoin Cash.
I sweeped both your BitCore and BitcoinGold funds before somebody else got to it. Post a BitCore and BitcoinGold address in this thread and I will send them back to you.
Here are those transaction ids
https://chainz.cryptoid.info/btx/tx.dws?172551.htm
http://btgexp.com/tx/f78617a5e6bf438c7a310639f6d8fe10c194a74be6ac98b2c329024a4d1df745
EDIT: Please post your addresses where you want the coins sent in the 32btc contest thread since its unmoderated.
Congrats on finding the private key. I don't think you know but you can also claim BitCore and Bitcoin GOLD with that private key. I see you or somebody already claimed Bitcoin Cash.
I sweeped both your BitCore and BitcoinGold funds before somebody else got to it. Post a BitCore and BitcoinGold address in this thread and I will send them back to you.
Here are those transaction ids
https://chainz.cryptoid.info/btx/tx.dws?172551.htm
http://btgexp.com/tx/f78617a5e6bf438c7a310639f6d8fe10c194a74be6ac98b2c329024a4d1df745
EDIT: Please post your addresses where you want the coins sent in the 32btc contest thread since its unmoderated.
#54 has been found by LBC. They are now searching for #55. See:
https://bitcointalksearch.org/topic/m.24681091
https://bitcointalksearch.org/topic/m.24681091
Hi everyone
I saw your topic yesterday and from yesterday I tried to find the key for account number 54 with my own program. For now, I have already tested more than 16,777,216 keys to find the key for that account, which has been not answered so far.
I know this as a benchmark for my own calculations. we'll see soon Who will succeed. I'm not likely.
You are trying about 17,000,000 per day.I saw your topic yesterday and from yesterday I tried to find the key for account number 54 with my own program. For now, I have already tested more than 16,777,216 keys to find the key for that account, which has been not answered so far.
I know this as a benchmark for my own calculations. we'll see soon Who will succeed. I'm not likely.
LBC is trying about 190,000,000,000,000 per day.
Also, if you are sequentially searching the space for the number 54 then you are just searching addresses that LBC has already searched.
Wouldn't it make more sense to just join LBC?
I asked in his thread about what speeds my GPUs would get and my post was deleted.
Jump to: