I think you mean: adr1 = ripemd160(sha256(pubkey(rand(2^256-2^160)+2^160)))
for (a = 0 to 2^160) {
adr2 = ripemd160(sha256(pubkey(a)))
if (adr1 == adr2) {
print "We got ourselves a collision!\n";
}
}
Yep. That's what I mean. Rico |
|
|
|
What I think is important to state: A collision is not the event when while(1) {
if (rand(2^256) == rand(2^256) {
print "We got ourselves a re-used private key!\n";
}
}
a collision is when while(1) {
for (a = 0 to 2^160) {
adr1 = ripemd160(sha256(pubkey(a)))
adr2 = ripemd160(sha256(pubkey(rand(2^256-2^160)+2^160)))
if (adr1 == adr2) {
print "We got ourselves a collision!\n";
}
}
}
both is pseudo-code of course, one should not make any conclusions about probabilities of events because "one (the second one) seems to take longer". Personally, I do not see how faith in bitcoin could be shattered if a collision is found, as - hopefully - everyone knows already that because of the 256->160 bit reduction in address generation there inherently are collisions, namely 2^96 private keys per address. Even if two private keys do map to one address, the public key will still be different and I do not believe that even if cryptographers should have several examples of collisions they would be able to form a reverse-map attack against bitcoin. Also the problem with "2 randomly generated private keys (using a working rndgen) ending up as one and the same" can never by proven to have happened, while the collision can. Rico |
|
|
|
Ah! So we aren't concerned about 2 people generating the same private key?
Ok then, I'll happily take that bet. How much do you want to put on it, and what timeframe? You'd have a better chance of winning if you bet that all human life on the earth will be destroyed by an asteroid in the next 25 years.
Well - I am not concerned about anything.  I thought about 25y timeframe, because compared with the "There will never be a collision." statement which provoked my reaction, this is very very soon. As for the sum to put on it, let me do some research 1st like what is usual in these "scientific" bets https://en.wikipedia.org/wiki/David_Levy_(chess_player)#Computer_chess_betor rewards for solutions to "problems" https://en.wikipedia.org/wiki/Paul_Erd%C5%91s#Erd.C5.91s.27_problemsso between $500 and $5000 of todays $? BTW: Betting on the destruction of mankind is quite pointless if even one of the betting parties is human. Rico |
|
|
|
Collisions will occur (and have occurred) when people use random number generators with poor entropy, brain-wallets, or when they use poorly created wallet software.
That's not the definition of a collision. The definition of a collision is: 2 different private keys will compute into one hash160. I'm not the youngest anymore, but I'm quite confident we will see such a collision within the next 25 years. Rico edit: Huh Danny? You teleported away? |
|
|
|
There will never be a collision.
How about a bet? Rico |
|
|
|
no, rico is trying to find a key from an address of the first tansaction so that he can claim to be satoshi when he sign with this key.
Nah - that's not the purpose of the LBC pool. That will be the purpose of the CWR pool I will set up after we have searched the whole PK space. While I do believe the pool will find a significant number of PKs, I also do believe this (and how we will handle it) will have no adverse effect on Bitcoin price. These two beliefs are not mutually exclusive - I believe. Rico . . . . . . CraigWrightReloaded - in case you had trouble figuring it out. |
|
|
|
|
The pool may experience spikes in speed (or variance in general), as I will be testing my GPU client in the next few days.
Currently I get on a Nvidia Quadro M2000M about 8 MKeys/s and a R9 280x gives around 14 MKeys/s
I will try also on the K80 GPUs @ AWS
The long term tendency for the speed of the pool can be described as steadily rising - without the GPUs it has currently about 38 MKeys/s. Unfortunately the top30 is populated with many dormant clients who already brought quite some GKeys to the table, so the entry barrier to top30 is quite high (almost 500 GKeys as of this writing).
If your client is new, don't forget to do a ./LBC -q from time to time to see where you are. (you can do so in another console while your LBC is running - no need to stop it for that)
Early Access to GPU clients in about a week will be preferably given to people with active clients in the top30.
Rico
edit:
As the question came up about various ids:
If you changed the hostname or the number of CPUs or the memory (which happens if you reconfigure a VM) your client-id has also changed so you may have several Ids in the LBC database. I will help you consolidate this for any Id that has 50+ GKeys on its "account".
The next LBC release will allow you to change your Id, so you may be able to perform consolidation yourself to some extent.
|
|
|
|
I don't understand...
It seems...
Please define your pool.
The sole purpose of the pool is to discriminate between intelligent and less intelligent people. Rico |
|
|
|
The 99% idiots revolving around bitcoin.
The ones who are using bitcoin cannot be considered idiots i guess. Depends on the definition/metrics one applies - I guess. For me everyone with a Bets/Gambling paid signature here falls into that 99% pot already. Rico |
|
|
|
|
The 99% idiots revolving around bitcoin.
Rico
|
|
|
|
How did I miss this gem?
I've got 4 AMD GPUs ready to go!
Much excite!
$ LBC -g -t 10
Best generator chosen: gen-pleiades-linux64
Ask for work... got blocks [80253865-80303017] (51540 Mkeys)
************************************************
Ask for work... got blocks [80317417-80366569] (51540 Mkeys)
************************************************
Each '.' of the now-deprecated go-generator was 2^20 keys. Each 'o' of HRD-core generator is 2^24 keys (= 16 x '.') Each '*' of Pleiades generator (GPU) is 2^30 keys ( = 64 x 'o') Right now the GPU speed is still miserable, it's even a little bit less than 50% of what oclvanitygen gives me. Quite frankly I'm fighting with motivation, because I'm royally pissed about two facts: a) me being so bad/inexperienced with GPU programming b) nevertheless it still being me who has to program this generator despite the 1+ BTC bounty because in this cesspool of highly qualified individuals with all their faucet business ideas and signature campaigns and ... opinions ... everything else seems way more interesting.  Rico |
|
|
|
Pleiades Prototype alpha
Is this the marking of the KNL or another form of "cluster"?
Hmmmm?
Maybe not so clandestine anymore then? Rico |
|
|
|
|
Well - it's not stealing in Germany and in Japan. That much I know now.
Rico
|
|
|
|
Now:
In 2014, Burton Wagner was arrested without any crime being committed. His house ransacked and family torn apart in fear while he was dragged off to jail while government militia members stole all his money. They refused to release him from prison without his agreement that they could keep a large block of his money. That sounds a hell of a lot like government taxation without representation to me.
That's why I brought up the communist CZ of the 70ies. I can remember my parents telling me about the life situation. The status of "property". Like they simply could not be sure, some official would show up the other day and confiscate the car or anything else. https://www.youtube.com/watch?v=3kEpZWGgJkssounds like 1:1 - and I mean that without any exaggeration. None needed. Rico |
|
|
|
Purely hypothetical scenario that would never happen to someone like you or me:
1 )
...
9 )
Sounds a little bit worse than communist Czech Republic of the 70ies, where my parents had the decency to flee from - together with their child. Of course the Czech Republic had also better medical care in the 70ies than Colorado has today, but that's just as an aside. Rico |
|
|
|
|
This thread is so full of shit, one can barely breathe.
Rico
|
|
|
|
Wenn ich nochmal um den Faktor 1000 besser werde ist's nicht mehr ganz so kläglich, aber immer noch
ungefährlich für Bitcoin.
Im Übrigen sind wir soweit. Der Pool ist die letzten 2 Tage ca. um den Faktor 1000 schneller als die Keygenerierung zu der Zeit o.g. Zitats. Einen Riesengrund zur Besorgnis gibt es natürlich noch nicht, allerdings spricht prinzipiell Nichts dagegen, dass der Pool in ca. 4 Monaten nochmal um den Faktor 1000 schneller wird, denn nachdem ja hier keiner zu Potte kommt, habe ich beschlossen einen GPU client zu schreiben. https://youtu.be/lbDoZTs3NoY?t=65Rico |
|
|
|
Hey! I also blocked !  Also PM. I need infos about client-Id Rico |
|
|
|
No problem. Der effektive Suchraum bis man statistisch irgendeine Adresse findet ist 136.75 bit, weil wir derzeit gegen ca. 11 mio Adressen prüfen lg(11863283) = 23.5 2^160 / 2^23.5 = 2^136.75 Dass wir bereits eine Adresse gefunden haben und vor dem abknuspern von 136 bit noch potentiell mindestens weitere 80 Adressen finden werden ändert am effektiven Suchraum praktisch Nichts, denn dann wäre es lg(11863203) = 23.49999024646846237705, also immer noch 23.5 Rico |
|
|
|
Oh nice. I didn't know there was a thread about this. LBC just found 38-42 of the puzzle transaction: http://lbc.cryptoguru.org:5000/trophiesI 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 |
|
|
|
|
Show Posts
