3 ms·
IIRC vbuterin formerly published code to brute force the nakamoto accounts specifically. It looks like the Python code to attempt such in Canada is no longer ea
by onlythehallpass 2y ago
IIRC vbuterin formerly published code to brute force the nakamoto accounts specifically. It looks like the Python code to attempt such in Canada is no longer easy to find on github and things CSVW did, like Calibri and OpenOffice.
TIL about keys.lol:
> Every Bitcoin and Ethereum private key is on this website
The Large Bitcoin Collider: https://lbc.cryptoguru.org/about https://lbc.cryptoguru.org/about
> The "Large Bitcoin Collider" (LBC - a homage to LHC) is a distributed effort to find at least one collision of private Bitcoin keys by creating addresses to private keys in a continuous 2160 range. These are checked against the list of known BTC addresses with funds on them. In the rare event of a collision, the funds on the address in question would become accessible to the collision finder.
Unfortunately it's not possible to prevent sanctioned states from stealing assets by guessing crypto keys either.
When one sends a transaction from a Bitcoin address, the public key of the source account is then disclosed.
Is it or isn't it a vulnerability to share public keys; or, how long would it take to guess one or all key pairs with n coherent qubits in what year?
- andirk 2y agoI've heard it explained as "It is like finding one specific grain of sand on an earth where all grains of sand on earth are earths with sand." Even shuffling a deck of cards has more arrangements than stars in the universe. If technology advances enough to brute force that many keys in a reasonable amount of time, then every other password and security technology that uses cryptography will also be compromised. It's just a 2x sha256 right?