prove it
satoshi made a few transactions from the same key
https://www.blockchain.com/explorer/transactions/btc/f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16
https://www.blockchain.com/explorer/transactions/btc/a16f3ce4dd5deb92d98ef5cf8afeaf0775ebca408f708b2146c4fb42b41e14be
https://www.blockchain.com/explorer/transactions/btc/12b5633bad1f9c167d523ad1aa1947b2732a865bf5414eab2f9e5ae5d5c191ba
https://www.blockchain.com/explorer/transactions/btc/591e91f809d716912ca1d4a9295e70c3e78bab077683f79350f101da64588073
https://www.blockchain.com/explorer/transactions/btc/828ef3b079f9c23829c56fe86e85b4a69d9e06e5b54ea597eef5fb3ffef509fe
HAVE FUN (many have tried for 15 years and failed) im sure you will fail
you can get the sigs and try and break satoshis first stash
the address still holds 195btc. so a good win for you if you can prove it
the great thing about satoshi leaving funds alone and then disappearing is he left people to test bitcoin for vulnerabilities. so if you can break it, prove it
Topic: I found a method to reverse public keys to private keys - page 4. (Read 538 times)
Here you go:
Private key, and nonces (k1 and k2) are less than 200 bits. Break it.
Code:
Public Key (Hex): 031f7b4d773de256a16526c6d2226d617e141250272b9f4521acc6db97d0e95cce
Signature 1:
R1 = 0x3076de63523a586e3f0050c1d0960977f1eaf26803d5dfbd139eec1df30480f2
S1 = 0x99a06d579865d4e5f608945a668dad03aa64baf1520b21efc2f90971c207f383
Z1 = 0x8055c4701f995b0c59c86e5c8a93706a7ea424035feec9a8641e8e5a763e7a20
Signature 2:
R2 = 0x669809d5a8007d6f82b4b97188101a9b81f4b6d52b1816dcb508f1c1627cdbeb
S2 = 0x419138af2715f77c0566c491f17405507dd63e7fb6076f2d7d1d87092f3ef25
Z2 = 0xa19d1f3d31d8896ac2626b0f466d0e416ceea61f0f5d935517ab416e08fc9806
Private key, and nonces (k1 and k2) are less than 200 bits. Break it.
So (who would believe
it didn't work. can you please provide more signatures? like upto 10? I have a script to generate them if you want. 
Will not find, 100%
Hi, you can generate walid signatures for custom publick key ?
First of all, I'd like to say that I have a different account on the forum, and I'm creating this one just to stay anonymous.
I know how this sounds. but here me out.
All i need is one of you to generate a public key with a private key which is below 200 bits (just to note, I already done this method on 256 bit keys. I didn't touch any funds).
Sign at least two messages with that public key.
Include your bitcointalk username in one of them.
The more signatures you provide the faster it'll take my computer to compute it.
10 is well more than enough.
I also have a script to generate these, if you want to save time on that, but i recommend not trusting what i say and write your own script.
Edit: when you send the signatures, send them in this format:
R = 0xHexValue
S = 0xHexValue
Z = 0xHexValue
Note: both the nonce and the private key needs to be below 200 bits.
I know how this sounds. but here me out.
All i need is one of you to generate a public key with a private key which is below 200 bits (just to note, I already done this method on 256 bit keys. I didn't touch any funds).
Sign at least two messages with that public key.
Include your bitcointalk username in one of them.
The more signatures you provide the faster it'll take my computer to compute it.
10 is well more than enough.
I also have a script to generate these, if you want to save time on that, but i recommend not trusting what i say and write your own script.
Edit: when you send the signatures, send them in this format:
R = 0xHexValue
S = 0xHexValue
Z = 0xHexValue
Note: both the nonce and the private key needs to be below 200 bits.
Hi, you can generate walid signatures for custom publick key ?
Here you go:
Private key, and nonces (k1 and k2) are less than 200 bits. Break it.
Code:
Public Key (Hex): 031f7b4d773de256a16526c6d2226d617e141250272b9f4521acc6db97d0e95cce
Signature 1:
R1 = 0x3076de63523a586e3f0050c1d0960977f1eaf26803d5dfbd139eec1df30480f2
S1 = 0x99a06d579865d4e5f608945a668dad03aa64baf1520b21efc2f90971c207f383
Z1 = 0x8055c4701f995b0c59c86e5c8a93706a7ea424035feec9a8641e8e5a763e7a20
Signature 2:
R2 = 0x669809d5a8007d6f82b4b97188101a9b81f4b6d52b1816dcb508f1c1627cdbeb
S2 = 0x419138af2715f77c0566c491f17405507dd63e7fb6076f2d7d1d87092f3ef25
Z2 = 0xa19d1f3d31d8896ac2626b0f466d0e416ceea61f0f5d935517ab416e08fc9806
Private key, and nonces (k1 and k2) are less than 200 bits. Break it.
First of all, I'd like to say that I have a different account on the forum, and I'm creating this one just to stay anonymous.
I know how this sounds. but here me out.
All i need is one of you to generate a public key with a private key which is below 200 bits (just to note, I already done this method on 256 bit keys. I didn't touch any funds).
Sign at least two messages with that public key.
Include your bitcointalk username in one of them.
The more signatures you provide the faster it'll take my computer to compute it.
10 is well more than enough.
I also have a script to generate these, if you want to save time on that, but i recommend not trusting what i say and write your own script.
Edit: when you send the signatures, send them in this format:
R = 0xHexValue
S = 0xHexValue
Z = 0xHexValue
Note: both the nonce and the private key needs to be below 200 bits.
I know how this sounds. but here me out.
All i need is one of you to generate a public key with a private key which is below 200 bits (just to note, I already done this method on 256 bit keys. I didn't touch any funds).
Sign at least two messages with that public key.
Include your bitcointalk username in one of them.
The more signatures you provide the faster it'll take my computer to compute it.
10 is well more than enough.
I also have a script to generate these, if you want to save time on that, but i recommend not trusting what i say and write your own script.
Edit: when you send the signatures, send them in this format:
R = 0xHexValue
S = 0xHexValue
Z = 0xHexValue
Note: both the nonce and the private key needs to be below 200 bits.
Jump to: