|
|
|
|
|
|
|
|
|
"Governments are good at cutting off the heads of a centrally
controlled
networks like Napster, but pure P2P networks like Gnutella and Tor seem
to be holding their own." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
itod
Legendary
 Offline
Activity: 1974
Merit: 1075
^ Will code for Bitcoins
|
 |
December 09, 2014, 12:03:46 AM |
|
I don't think that he is a good samaritan unless he eventually gives me the coins he stole back. I also sent an email to blockchain so hopefully I can get refunded or something...this is retarded.
Here's the explanation how to sign the message, it's for two wallets but the procedure is pretty much the same for all other wallets: http://support.bitcoin.cz/Knowledgebase/Article/View/36/0/how-to-sign-a-message-using-a-bitcoin-clientJust sign the message to prove you are not trying to steal somebody else's coins, and PM that signature to johoe, he promised to return the coins to their rightful owners. IMHO it is very honorable thing if he fulfills the promise, if he haven't collected the coins a real thief could have done it and you would never see your coins back. |
|
|
|
|
|
TheRealSteve
|
|
December 09, 2014, 12:06:37 AM |
|
Here's the explanation how to sign the message Just to note: If you can convince me that they belong to you (signing a message with the address is obviously not enough; the private key is already known), I will send the funds back. |
|
|
|
Remember remember the 5th of November
Legendary
Offline
Activity: 1862
Merit: 1007
Reverse engineer from time to time
|
|
December 09, 2014, 12:15:04 AM |
|
Here's the explanation how to sign the message Just to note: If you can convince me that they belong to you (signing a message with the address is obviously not enough; the private key is already known), I will send the funds back. Just sign the previous address from which the funds were transferred from(their outputs) |
BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
|
|
|
itod
Legendary
Offline
Activity: 1974
Merit: 1075
^ Will code for Bitcoins
|
|
December 09, 2014, 12:17:30 AM |
|
Here's the explanation how to sign the message Just to note: If you can convince me that they belong to you (signing a message with the address is obviously not enough; the private key is already known), I will send the funds back. Just sign the previous address from which the funds were transferred from(their outputs) Good idea. This is definitely proof the coins are yours, no question about it. |
|
|
|
|
|
TheRealSteve
|
|
December 09, 2014, 12:28:41 AM |
|
The only problem is people who might have sent the original owner these coins might attempt to scam by pretending to be him. Well, that's not the only problem. Signing a message with the key associated with the address the funds were sent from - and this would of course have to be an unaffected address as well - does work well... if you can do so. If you are not the owner of that address - e.g. you purchased Bitcoin from a service, you're mining at a pool, any case where the coins were sent to you by a third party - you would be SOL, at least as far as this approach goes. In the mean time, it looks like blockchain.info is intending to make affected people whole again. Perhaps some people will effectively double their returns as a result  |
|
|
|
migovision
Newbie
Offline
Activity: 1
Merit: 0
|
|
December 09, 2014, 02:16:06 AM |
|
I am the other user with the adress 1LDpUmrwVKSFyXy2czE423dH8yd4K9R9WW. If the user with the 99BTC will read this. pls write me a messeage. |
|
|
|
|
molecular
Donator
Legendary
Offline
Activity: 2772
Merit: 1018
|
|
December 09, 2014, 07:20:24 AM |
|
Can someone point me to the actual commit that introduced this bug?
|
PGP key molecular F9B70769 fingerprint 9CDD C0D3 20F8 279F 6BE0 3F39 FC49 2362 F9B7 0769
|
|
|
|
|
|
JorgeStolfi
|
|
December 09, 2014, 08:07:50 AM |
|
I suppose that they generated one number with the new code, and it looked random allright.  |
Academic interest in bitcoin only. Not owner, not trader, very skeptical of its longterm success.
|
|
|
|
johoe (OP)
|
|
December 09, 2014, 10:56:09 AM |
|
I just want to say that I contacted the blockchain.info support, but I haven't heard back from them, yet.
To avoid double reimbursement, I want coordinate this with the blockchain.info people. They should, hopefully, be able to check whether claims are valid or not. If you lost funds due to this bug, contact the blockchain support, not me. I cannot answer all PMs regarding this problem.
|
Donations to 1CF62UFWXiKqFUmgQMUby9DpEW5LXjypU3
|
|
|
cr1776
Legendary
Offline
Activity: 3640
Merit: 1276
|
|
December 09, 2014, 11:13:08 AM |
|
I just want to say that I contacted the blockchain.info support, but I haven't heard back from them, yet.
To avoid double reimbursement, I want coordinate this with the blockchain.info people. They should, hopefully, be able to check whether claims are valid or not. If you lost funds due to this bug, contact the blockchain support, not me. I cannot answer all PMs regarding this problem.
Just remember, no good deed goes unpunished. Perhaps this should be in a new thread too. |
|
|
|
|
|
|
|
JorgeStolfi
|
|
December 09, 2014, 01:41:07 PM |
|
|
Academic interest in bitcoin only. Not owner, not trader, very skeptical of its longterm success.
|
|
|
flipperfish
Sr. Member
Offline
Activity: 350
Merit: 251
Dolphie Selfie
|
|
December 09, 2014, 07:10:21 PM |
|
Is it the unconditional use of Math.random() after the use of the Crypto API (if available), that lead to the bug? Or is there some other problem, I don't see? Why isn't there a fixing commit, yet? |
|
|
|
|
|
Initscri
|
|
December 09, 2014, 08:59:07 PM |
|
I just want to say that I contacted the blockchain.info support, but I haven't heard back from them, yet.
To avoid double reimbursement, I want coordinate this with the blockchain.info people. They should, hopefully, be able to check whether claims are valid or not. If you lost funds due to this bug, contact the blockchain support, not me. I cannot answer all PMs regarding this problem.
In my support ticket with them, I mentioned you. Hopefully this may elevate /escalate the priority. |
----------------------------------
Web Developer. PM for details.
----------------------------------
|
|
|
itod
Legendary
Offline
Activity: 1974
Merit: 1075
^ Will code for Bitcoins
|
|
December 10, 2014, 12:46:33 AM |
|
Is it the unconditional use of Math.random() after the use of the Crypto API (if available), that lead to the bug? Or is there some other problem, I don't see? Why isn't there a fixing commit, yet? zootreeves added a note an hour ago: For those interested. The bug was caused by missing line 29 and not initialising rng_pptr to 0. This commit was force pushed over. |
|
|
|
|
|
johoe (OP)
|
The money has been returned to blockchain.info. Please write to blockchain support to claim refund. From: Ben Reeves < ...@blockchain.info> If you could return the funds to address 15tXHJCjehqCEL6zRCkGwvuDY6YzZV5sKP that would be fantastic. I should also add if that using our admin tools, if users supply us with the correct wallet information, we are able to accurately determine which refund claims are valid and which are not. So far we have processed over 30 refund requests and will be processing more over the rest of this week. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 15tXHJCjehqCEL6zRCkGwvuDY6YzZV5sKP -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.orgiQEcBAEBAgAGBQJUh5AdAAoJEP3NqDUC96SQqH0H/3pTTawCXZWfWAwIoVQPkSYa DgpioEvHLDHXegfAfXyo8X9vc50kEseQVeZ5FAvoeC3Hy76gNIgEDllP5o6FUXL2 HsEj7qcafY5AxlxMgRRG9p1OcbeJS6mlbZrjB78BD+zrtzZaLFoSAf4+lw3YZHg5 xvA0WyNoHE1Hzg8+pdPbg1PPN6dHT38+PCyqFgYIjkjq07UbxxtyyWs8KIQqSuTe 4XIh0gjd73Wqtxm4CAHtnwy0PA5Pi/lE7v0d6qqF2l86SlxDkT6067asMw9Te0JJ WgnFM8fePrM8HU980n0xvamae7J71zlFMN2/RYfj2t/pTIEWz25ZI2iVS0MGg14= =9MGK -----END PGP SIGNATURE—— PGP key is available from https://blockchain.info/security.txt https://blockchain.info/tx/ea8fa447d59000843910932a42bf7a28915772d97a006e97714d026b78885754 |
Donations to 1CF62UFWXiKqFUmgQMUby9DpEW5LXjypU3
|
|
|
theymos
Administrator
Legendary
Offline
Activity: 4788
Merit: 10900
|
|
December 10, 2014, 01:14:15 AM |
|
The money has been returned to blockchain.info. Please write to blockchain support to claim refund.
That's very ethical of you. I hope they gave you a substantial reward. |
1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
|
|
|
|
BruceFenton
|
|
December 10, 2014, 02:04:08 AM |
|
The money has been returned to blockchain.info. Please write to blockchain support to claim refund. From: Ben Reeves < ...@blockchain.info> If you could return the funds to address 15tXHJCjehqCEL6zRCkGwvuDY6YzZV5sKP that would be fantastic. The return address is SINGLE SIG??!? C'mon guys. I absolutely love Blockchain -- but there is not a great excuse to not use multi signin this of all transactions. |
|
|
|
|
|
