Topic: Bitcoin is not the answer for microtransactions; how to rebroadcast unconfirmed? (Read 3936 times)

If you send with less then the recommend TX fee then you are more or less sending without a fee at all. A smaller fee may speed up confirmation somewhat but it will still take a long time if it confirms at all.

Nice marketspeak (Still don't know how safecoin gets around the problem).

Neil

At the moment Micro-transactions are not that bad really

 Fee =  0.00005 BTC is ---- 3 cents

If you want to tip someone 5 Cents it means you need to send 8 Cents to include the fee, that really isnt that bad, I think you can manage even less fees.

And on top of this, when the fee things gets sorted , fees should change to depending how much or how little your sending. I was watching the last video of the core devs speaking . I think it was in Amsterdam, they brought the fee thing up and said it will be coming in the next version or seomthing.

+1  devs are working on this also . Its being talked about

LOL , It may be ok because its worth next to nothing. But mainstream are still struggling to adopt BTC and now we talking dogecoin, a coin with a picture of a dog on it? Man i never understood that stupid image, Dogs & Money is just ridiculous mix.

If micro-payments is what the market really REALLY wants and needs, the clients will be modified to make it plausible...  Gavin mentioned something about adjustable fees at the last meeting which will be coming out in one of the next versions, not sure exactly is this will sort it a little. But anyway at this point of time its not needed,  if even 25% of users and larger companies start opting for throwing money to invest into the startups And start creating applications around this tipping market.. THIS is when clients or core will be modified slightly to enable this type of thing

this problem is here only because bitcoin isn't at fully potential, i mean price of btc is still in his infancy, with a better price problem like this will not occur anymore

Yeah, i think 10k satoshi ($0.06) is too big for small payment
Last time i try to send some BTC with 0.00001 fee. take 4 hours just for 1 confirmation 

You can rebroadcast unconfirmed with higher fee
anyway, i think minimum fee for nom is 0.00005 BTC

if you very small fee payment, use dogecoin
the fee is about 1 - 2 dogecoin (35 - 70 satoshi) only 

safecoin does not use a blockchain and yes it is decentralized. Check out the systemDocs: http://maidsafe.net/SystemDocs/

FTFY.  "bits"?!

Really? What stops some malicious person filling up safecoins blockchain with terabytes of junk by transferring inputs around the place?

That is the main problem that fee's solve with bitcoin at the moment, it is not really about paying the miners yet.

Neil

idiotic statement... safecoin will have no transaction fees.

Well, not really, have you gone into a convenience store lately? Most of them say "5 dollar  minimum to use a credit card or debit card" because when they take credit cards they are charge a 30 cent or so fee just to do the transaction, then the 3-7 or so percent. then when the batch is uploaded for the day they are charged a batch fee, which is usually 20-50 cents for the entire day. so, 12 cents to take btc for a tiny amount still beats taking credit cards, though I would like it changed..

Most nodes usually will "forget" a TX after 24 hours if not confirmed. If your wallet is connected to a node that has "forgotten" a unconfirmed TX then you can rebroadcast the TX with a higher fee.

Ahhh… I see. Thanks so much for the clarification! Okay, so if this were to happen to me in the future, I would need to figure out those 3 commands and use the debug console.

I was using the ordinary Bitcoin-QT client (0.9.2.1). I used the debug console to create the transaction using the commands:

createrawtransaction ...
signrawtransaction ...
sendrawtransaction ...

I don't think Bitcoin-QT gives a way to choose which coins to spend using ordinary (GUI) methods.

Wow, this is a fantastic discovery with a surprise positive ending to your story! Congratulations on the terrific sleuthing here!!!

Which Bitcoin Wallet software did you use that enabled you to spend the unconfirmed output?? I ask because I know that some clients will not let people spend the unconfirmed output while the original transaction is still pending.

I'm glad your problem seems to be resolved. I've had a similar problem since April 23 -- i.e., over 3 months. I managed to resolve it. I'll share it in case it helps someone in the future.

On April 23 I sent a small transaction from myself to myself. I didn't include a fee. Maybe I was cheap or maybe I forgot. I don't remember. I know the confirmation wasn't urgent. Well, it had been sitting in my wallet "unconfirmed" since then -- for over 3 months. At some point I tried the things described in this thread: rebroadcast with a fee, but it wouldn't get pushed onto the network because it looked like it never would. I waited for the transaction to "fall off" the network so I could resend it, but when I checked every few weeks it was still on blockchain.info as "unconfirmed."

Yesterday I had an idea: Spend the output of the unconfirmed transaction to myself again, but this time with a fee. I thought maybe a miner would confirm the first transaction in the hopes of being able to confirm the next one (the one with the fee). It worked -- and in a way I didn't know possible. Both of the transactions were confirmed in the same block. I didn't know a block could include two transactions, one of which spends from the output of the other, but apparently it's possible.

Conclusion: If there is a transaction that won't confirm due to a low fee, and you are the intended recipient, then just spend the output to yourself with a fee.

Here's the original transaction that was sent in April and confirmed today:

https://blockchain.info/tx/17f723bc265ebbeef77b2b081e29985c30b737025ed6a6547842d3c24d023797

Here's the second transaction confirmed in the same block (314320) with a fee of 0.0004827:

https://blockchain.info/tx/730546e11c79a3399f1fe7f617a7d4ff28edae1c7732180307ca84c2f1e63af2

And that's the story of how I got back my two mbits from 3.5 months of limbo.

The transaction finally "fell off" of Blockchain.info, which was the node that was holding onto it and keeping it "stuck". It took 4 days, but I got my coins back! I then sent them again with the appropriate fee and everything is now good.

I checked whether the transaction is ok:


It appears to decode ok



When I do a sendrawtxransaction, I receive a code 18 bad-txns-inputs-spent message.

I thought it might be a formatting problem. I also assumed that this is the new, higher fees tx to try and override the old one.