maybe trying to spread some fud? to cause a price panic?
I wouldn't be that harsh. I think the worse news would be if someone found a collision, but was afraid to post it.
It seems what happened was this (from my messagebox):
Quote
Until today i knew that the maximum possible value a bitcoin key could have is 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141
But i learned something new. If a key with value over maximum number of n points is used, then the address generation resets from base point G. For example, by adding 4 to the key i pasted above we get the value 0xfffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364145 which produces the same public keys and addreses as 0x4
But i learned something new. If a key with value over maximum number of n points is used, then the address generation resets from base point G. For example, by adding 4 to the key i pasted above we get the value 0xfffffffffffffffffffffffffffffffebaaedce6af48a03bbfd25e8cd0364145 which produces the same public keys and addreses as 0x4
Quote from: shifty252
Quote from: rico666
That's not a collision, that's the simple modulo p arithmetics.
True, but https://rawgit.com/brainwallet/brainwallet.github.io/f7679dd03f39a04edced641960a7c3df1116fea9/#generator accepts it as a real key.
In theory, a broken bitcoin client could accept a key over the limit and generating a "collision" like this.
So short story:
with LBC, you can wiggle in extreme keyspace, but you really should focus on the 1st 2160 bits.
shifty252 found buggy software @ https://rawgit.com
end of story
Rico
