|
jl2012
Legendary
Offline
Activity: 1792
Merit: 1097
|
|
February 11, 2014, 04:14:11 AM |
|
Quick answer: don't need to worry. You fund is perfectly safe
|
Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY) LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC) PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
|
|
|
jl2012
Legendary
Offline
Activity: 1792
Merit: 1097
|
|
February 11, 2014, 04:17:18 AM |
|
Someone is using the malleability to spread FUD. It looks bad but won't lead to any real harm.
|
Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY) LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC) PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
|
|
|
buffett (OP)
Newbie
Offline
Activity: 59
Merit: 0
|
|
February 11, 2014, 04:19:01 AM |
|
Quick answer: don't need to worry. You fund is perfectly safe
what's going on with blockchain? is the whole network effected by malleable attack?
|
|
|
|
jl2012
Legendary
Offline
Activity: 1792
Merit: 1097
|
|
February 11, 2014, 04:22:14 AM |
|
Quick answer: don't need to worry. You fund is perfectly safe
what's going on with blockchain? is the whole network effected by malleable attack? Blockchain.info mistakenly thinks those transactions are double-spending but actually they are not. However, these are all cosmetic issue and no real harm could be done. I have pm-ed piuk asking him to stop reporting double-spending on his service for now
|
Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY) LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC) PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
|
|
|
buffett (OP)
Newbie
Offline
Activity: 59
Merit: 0
|
|
February 11, 2014, 04:26:41 AM |
|
Quick answer: don't need to worry. You fund is perfectly safe
what's going on with blockchain? is the whole network effected by malleable attack? Blockchain.info mistakenly thinks those transactions are double-spending but actually they are not. However, these are all cosmetic issue and no real harm could be done. I have pm-ed piuk asking him to stop reporting double-spending on his service for now everytime i send btc to my customer, i also send email notification of the txid. so now this practice should be avoided because huge chance that txid can be altered? and should we store the txid into our database? if not, how we determine each transaction from our end? what should we do as merchant/developer to anticipate this malleability issue?
|
|
|
|
jl2012
Legendary
Offline
Activity: 1792
Merit: 1097
|
|
February 11, 2014, 04:30:10 AM |
|
everytime i send btc to my customer, i also send notification of the txid. so now this practice should be avoided because huge chance that txid can be altered? and we should not store the txid into our database?
what should we do as merchant/developer to anticipate this malleability issue?
You can still rely on txid, but ONLY AFTER SEVERAL CONFIRMATIONS Confirmation is the king: not just for the safety of the fund, but also for the reliability of txid
|
Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY) LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC) PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
|
|
|
jl2012
Legendary
Offline
Activity: 1792
Merit: 1097
|
|
February 11, 2014, 04:42:28 AM |
|
For merchants, if they want to record a transaction immediately without waiting for confirmation, what they could do now is to record the inputs (txid:index), outputs (address), and values. These information, altogether, is not malleable and could be an unique identifier for a transaction, even for zero confirmation
|
Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY) LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC) PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
|
|
|
renee25
Member
Offline
Activity: 79
Merit: 12
|
|
February 11, 2014, 07:08:11 PM |
|
so bitcoin 102 guy and gox maybe right after all
|
|
|
|
buffett (OP)
Newbie
Offline
Activity: 59
Merit: 0
|
|
February 11, 2014, 07:19:29 PM |
|
For merchants, if they want to record a transaction immediately without waiting for confirmation, what they could do now is to record the inputs (txid:index), outputs (address), and values. These information, altogether, is not malleable and could be an unique identifier for a transaction, even for zero confirmation
what is txid:index?
|
|
|
|
nmersulypnem
|
|
February 11, 2014, 07:40:25 PM |
|
everytime i send btc to my customer, i also send notification of the txid. so now this practice should be avoided because huge chance that txid can be altered? and we should not store the txid into our database?
what should we do as merchant/developer to anticipate this malleability issue?
You can still rely on txid, but ONLY AFTER SEVERAL CONFIRMATIONS Confirmation is the king: not just for the safety of the fund, but also for the reliability of txid Wait - I thought that this wasn't true. I thought that the altered transaction might be accepted to the block chain before the original one does, and so you can have a situation where the service thinks it didn't go through, but in fact the attacker DID get the BTC. If the attacker does that multiple times, they could withdraw an unbounded amount from the service.
|
|
|
|
dserrano5
Legendary
Offline
Activity: 1974
Merit: 1029
|
|
February 11, 2014, 07:59:13 PM |
|
what is txid:index?
Inputs to transactions refer to previously confirmed transactions and an index within, ie "The second output in transaction 01234567". This is what "txid:index" refers to.
|
|
|
|
buffett (OP)
Newbie
Offline
Activity: 59
Merit: 0
|
|
February 12, 2014, 12:59:33 AM |
|
what is txid:index?
Inputs to transactions refer to previously confirmed transactions and an index within, ie "The second output in transaction 01234567". This is what "txid:index" refers to. still don't get it. how to get txid:index from bitcoind?
|
|
|
|
dserrano5
Legendary
Offline
Activity: 1974
Merit: 1029
|
|
February 14, 2014, 08:32:23 AM |
|
what is txid:index?
Inputs to transactions refer to previously confirmed transactions and an index within, ie "The second output in transaction 01234567". This is what "txid:index" refers to. still don't get it. how to get txid:index from bitcoind? With 'bitcoind listunspent'. Example output: [ { "txid" : "3bec01c0bf0f52f79043abfbe3ba2c21ae417ffea74bf152368418df21a1d939" "vout" : 1, […] }, { "txid" : "9125d985a969a4c0a9cd7686a2d7e96cff886e55697ddc809639b3e690c558b8", "vout" : 0, […] }, […] ] The first entry refers to the second output in tx 3bec01c0bf0f52f79043abfbe3ba2c21ae417ffea74bf152368418df21a1d939 (59.3 BTC), the second entry refers to the first output in tx 9125d985a969a4c0a9cd7686a2d7e96cff886e55697ddc809639b3e690c558b8 (0.5 BTC) and so on. Try it with your wallet, you should be able to check in blockchain.info that all entries in your list appear as unspent, which they really are (unlike this example, where I just picked a couple of random txs). The sum of amounts in all your unspent outputs is your balance. That's how bitcoind figures it out.
|
|
|
|
|