eaurevoir on Nostr: I’m 1000+ hours into Bitcoin. There is one thing I don’t understand. A private ...
I’m 1000+ hours into Bitcoin. There is one thing I don’t understand.
A private key is a 256-bit string.
When using a private key to login to a software wallet, or reinstalling a hardware wallet with private key or seed phrase, the private key is instantly recognized. It’s not like you only know if a private key is valid when you sign a transaction.
My point is, why couldn’t you write a script that tries 1000 combinations a second? There doesn’t seem to be a time lapse per try.
I know entropy and that there are many many many combinations. But still. What am I missing here?
Published at
2024-08-15 06:33:35Event JSON
{
"id": "029bab5b8108104cd50dd450e6571a214eccfbec4a85afea7ce28a7ca43b471a",
"pubkey": "9b82771b64e989a53a19773a749a049c131efb12402cf455163b57d3e1de8c3f",
"created_at": 1723703615,
"kind": 1,
"tags": [],
"content": "I’m 1000+ hours into Bitcoin. There is one thing I don’t understand.\n\nA private key is a 256-bit string.\n\nWhen using a private key to login to a software wallet, or reinstalling a hardware wallet with private key or seed phrase, the private key is instantly recognized. It’s not like you only know if a private key is valid when you sign a transaction.\n\nMy point is, why couldn’t you write a script that tries 1000 combinations a second? There doesn’t seem to be a time lapse per try. \n\nI know entropy and that there are many many many combinations. But still. What am I missing here?",
"sig": "993d136258212055e4110c102f01fd004d268da8e00b2f3fe00d66901b13aa5c6dfe6549524f795c2170a8cd2c407f7f101a4c3d6eeb70681c7ceed1878ef791"
}