I just hope I didn't just lose 13btc because of random chance. Anyone have any consoling words for me?
um, don't send 13BTC worth of goods/services until your incoming 13BTC confirms
Topic: ... - page 2. (Read 4640 times)
I just hope I didn't just lose 13btc because of random chance. Anyone have any consoling words for me?
um, don't send 13BTC worth of goods/services until your incoming 13BTC confirms
This was a payment from coinbase to my wallet. I didn't do anything wrong (I don't think)
. . . I just hope I didn't just lose 13btc because of random chance. Anyone have any consoling words for me?
This is one of the risks you take when accepting transactions with 0 confirmations. I suppose you can try and find someone else to accept the 13 BTC from you with 0 confirmations as well. If the OP transaction ever confirms then all the other transactions confirm. If it gets reversed with a double-spend, then the whole chain collapses. 
I just hope I didn't just lose 13btc because of random chance. Anyone have any consoling words for me?
um, don't send 13BTC worth of goods/services until your incoming 13BTC confirms
I only looked at the first one but it is one giant "spammy" transaction (per low priority rules) which is 22KB and has a fee of 0.005 BTC. The min mandatory fee for low priority transactions is 0.0005 BTC per kb. For this tx that would require 0.011 BTC so the tx is non-compliant and many nodes will simply drop it.
Even with a 0.011 fee how long it takes to be confirmed depends on if a miner wants to include it in a block. Most miners are just going to pass on including junk like this. 22KB with 600? outputs is enough to increase the risk of getting an orphan. So say it increases propagation delay by 1%. So I can collect get 25 BTC or include your tx and get 25.01 BTC but 1% of the time I lose the entire block. In the long run I earn more by not including your tx. If I were running a pool I wouldn't include it ... ever.
Even with a 0.011 fee how long it takes to be confirmed depends on if a miner wants to include it in a block. Most miners are just going to pass on including junk like this. 22KB with 600? outputs is enough to increase the risk of getting an orphan. So say it increases propagation delay by 1%. So I can collect get 25 BTC or include your tx and get 25.01 BTC but 1% of the time I lose the entire block. In the long run I earn more by not including your tx. If I were running a pool I wouldn't include it ... ever.
Not really, since the propagation delay also increases the amount of time other miners work on an old block. I don't have a mathematical proof, but my gut feeling is that on average the size of the block simply does not matter.
So if I have a transaction that relies on a transaction that relies on a transaction that relies on this guy: http://blockchain.info/tx/88eb395b48a6d3875d8d55a6efd34afd2e1d4e397b43f9f790479914fba0c74b, does that mean that I won't get any confirmations until this goes through (if ever)?
My transaction (http://blockchain.info/tx-index/52509782/9eb202978e1653a0d3b1c936c2a07228055ce434c6c065c727336cfc0a74d115) has been unconfirmed for like 8 hours now and I think I traced the backup to the OPs transaction by using bitcoincharts (http://bitcoincharts.com/bitcoin/txlist/#9eb202978e1653a0d3b1c936c2a07228055ce434c6c065c727336cfc0a74d115). I guess there is no recourse right? I just hope I didn't just lose 13btc because of random chance. Anyone have any consoling words for me?
My transaction (http://blockchain.info/tx-index/52509782/9eb202978e1653a0d3b1c936c2a07228055ce434c6c065c727336cfc0a74d115) has been unconfirmed for like 8 hours now and I think I traced the backup to the OPs transaction by using bitcoincharts (http://bitcoincharts.com/bitcoin/txlist/#9eb202978e1653a0d3b1c936c2a07228055ce434c6c065c727336cfc0a74d115). I guess there is no recourse right? I just hope I didn't just lose 13btc because of random chance. Anyone have any consoling words for me?
Any chance they will ever confirm/return?
Do you control any of the outputs?
I think that if you initiate a transaction from any of the outputs, and put a juicy fee on it, miners will combine the two when analyzing its fee/priority ratio. That might speed things up.
as i recall, the relay fee is 0.001 vs the creation fee of 0.005. so it seems like your transaction would be relayed at least (if your node broadcasts it, some others should relay it). it would be pushed down to the bottom of the list as more transactions are added
0.0001 per kB (not KiB) to relay x 22.530kB in size = minimum 0.0023 fee to relay (vs 0.0005 paid). Bitcoin requires the minimum fee if any output is less than 0.01 BTC, which many many are. 
as i recall, the relay fee is 0.001 vs the creation fee of 0.005. so it seems like your transaction would be relayed at least (if your node broadcasts it, some others should relay it). it would be pushed down to the bottom of the list as more transactions are added
Good point forgot about the lower threshold for relay vs inclusion.
as i recall, the relay fee is 0.001 vs the creation fee of 0.005. so it seems like your transaction would be relayed at least (if your node broadcasts it, some others should relay it). it would be pushed down to the bottom of the list as more transactions are added
Even with a 0.011 fee how long it takes to be confirmed depends on if a miner wants to include it in a block. Most miners are just going to pass on including junk like this. 22KB with 600? outputs is enough to increase the risk of getting an orphan. So say it increases propagation delay by 1%. So I can collect get 25 BTC or include your tx and get 25.01 BTC but 1% of the time I lose the entire block. In the long run I earn more by not including your tx. If I were running a pool I wouldn't include it ... ever.
They only have 1 input though. I thought many inputs was the biggest problem in what concerns verification time.
Actually, if this transaction was paying 0,011 in fees, wouldn't it be better to include it instead of 22 tx of 1kb paying 0,0005 each, in what concerns propagation time? Since the latter would have at least 22 different inputs to be validated.
EDIT: Dumb me, outputs have to be inserted in the transaction index, and that's likely to take more time than validating inputs. Ignore what I said above.
I only looked at the first one but it is one giant "spammy" transaction (per low priority rules) which is 22KB and has a fee of 0.005 BTC. The min mandatory fee for low priority transactions is 0.0005 BTC per kb. For this tx that would require 0.011 BTC so the tx is non-compliant and many nodes will simply drop it.
Even with a 0.011 fee how long it takes to be confirmed depends on if a miner wants to include it in a block. Most miners are just going to pass on including junk like this. 22KB with 600? outputs is enough to increase the risk of getting an orphan. So say it increases propagation delay by 1%. So I can collect get 25 BTC or include your tx and get 25.01 BTC but 1% of the time I lose the entire block. In the long run I earn more by not including your tx. If I were running a pool I wouldn't include it ... ever.
Even with a 0.011 fee how long it takes to be confirmed depends on if a miner wants to include it in a block. Most miners are just going to pass on including junk like this. 22KB with 600? outputs is enough to increase the risk of getting an orphan. So say it increases propagation delay by 1%. So I can collect get 25 BTC or include your tx and get 25.01 BTC but 1% of the time I lose the entire block. In the long run I earn more by not including your tx. If I were running a pool I wouldn't include it ... ever.
Jump to: