You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I stumbled upon the following bug when using sendBitcoin() API call - sometimes, the call would return a txid (which my app treats as success) but this tx would never make it to the mempool. Why would that be? And how could developers accommodate to this behaviour?
The text was updated successfully, but these errors were encountered:
UPD from my observations - 1 of every 20-30 transactions would not make it to the mempool. I also noticed delayed propagation sometimes (don't have any metrics on this), like it could sometimes take more than a minute for the tx to reach my well-connected node as well as mempool.space. Looking to hear back on this 👀
I stumbled upon the following bug when using
sendBitcoin()
API call - sometimes, the call would return a txid (which my app treats as success) but this tx would never make it to the mempool. Why would that be? And how could developers accommodate to this behaviour?The text was updated successfully, but these errors were encountered: