Author

Topic: Transaction stuck on testnet for a while. Any other reason apart from fee? (Read 668 times)

legendary
Activity: 1001
Merit: 1003
Why are you trying to save the tx fee when testnet coin is worthless?
If you are really short of testnet coin, you can obtain 0.001 tbtc from http://faucet.haskoin.com/.

It was just a test. So I can find out all the issues with sending transactions etc before using it on live. Not really short of testnet coins.
legendary
Activity: 910
Merit: 1000
Why are you trying to save the tx fee when testnet coin is worthless?
If you are really short of testnet coin, you can obtain 0.001 tbtc from http://faucet.haskoin.com/.
hero member
Activity: 686
Merit: 500
fb.com/Bitky.shop | Bitcoin Merch!Premium Quality!
Transactions without fee, you just need to wait for confirmation and it's depends on transaction volume.
Never got any trouble yet about transaction(with fee) since the blockchain split issue has been solved.
member
Activity: 70
Merit: 10
★YoBit.Net★ 200+ Coins Exchange & Dice
0 fee!?
the only thing you can do is 'wait'
it will be confirmed one day...
sr. member
Activity: 369
Merit: 250
Give it some time and if you still have a problem let me know via PM.
I'm sure there is nothing to worry about... Be patient and hit me up if you cant resolve this.
hero member
Activity: 517
Merit: 501
I guess that your transaction isn't relayed because there are too many free tx already on testnet. Try including a fee.

I doubt that many people adjusted minrelaytxfee or limitfreerelay as proposed in the 0.10.2 and 0.11 release notes. But it's testnet after all, so mining itself is rather inconsistent.
legendary
Activity: 1001
Merit: 1003
I have sent several transactions in the past on testnet with no fee and dust outputs. Until about a couple of weeks ago, they seemed to be going fine. Here is the one stuck:

https://www.blocktrail.com/tBTC/tx/9eaef2cb7725903535424028777fc75b758233281d52c0f445596db6f1f54998

What could be the reason? I guess its the fee but is it because everyone on testnet seems to have suddenly updated their client or setup new broadcasting rules after the stress test on mainnet.

How do I ensure that it is broadcast to a lot more nodes? (It seems to be not getting propagated enough despite me transmitting it to about 100 peers every 10 mins).
Jump to: