TBTC sending issue (timed out transactions are sent later)
viilveer opened this issue · 5 comments
I have produced following scenario:
- Made new account
- Sent some TBTC from https://testnet.manu.backend.hamburg/faucet
- While having unconfirmed balance I started to send some funds to my own account
- Sending timed out, i tried it few times.
- After some time later, sending started to work (and balance was confirmed) but..
All my timed out transactions were also made... Check the timestamp of transactions.
@viilveer Were all these transactions confirmed in the same block?
When a transaction is pending, the time is set to the time the transation was first seen on the network, but once it's confirmed, we change this time to be the one the block in which it's included.
So here, if all these transactions were included in the same block, the times should be the same.
For the time out, it's strange, maybe you weren't connected to enough nodes at the time?
node.txt
Here are the logs aswell.
Thats true that they were confirmed in the same block.
https://live.blockcypher.com/btc-testnet/tx/cd7aea3d6ca4893f93e166cf707188ae6bb569bd8eb12cadd4192777173d0153/
https://live.blockcypher.com/btc-testnet/tx/9b6e6c88049f9a0fdb1efacf0e2f413e470a08db6fef8a6c9edc2045c09ac47c/
https://live.blockcypher.com/btc-testnet/tx/15a12994cde6a8f8a767dde727bdc33401dfe1c660a396cdc2f5f21170c9fa41/
I think that is also correct that I was not connected to enough nodes. But is it okay to make the transactions if connection is good at some point?
I can see from the logs that you were connected to a few nodes, none of which was up to date with their blockchain. So effectively it behaved as if you were connected to none.
I think this is behaving as expected.
If you ask me I would be surprised if it first says that it timed out and then later it completes the transaction. I might send the transaction again. I think that if this feature is supported (that timed out transactions are completed later on), those should be listed somewhere. my 2 cents only. :)
Fixed in a newer version of the Full Node