this is the issue... the mempool was flooded. we are engine…
this is the issue... the mempool was flooded. we are engineering to deal with these spikes
Replies
@metamitya are you trying to publish transactions via WhatsOnChain (TAAL), GorillaPool or by your own mining server?
atm whatsonchain but we were doing it naively which worked until these spikes... working on re broadcast and fee algos now and smarter utxo selection
going to diversify to gorilla also
Maybe the easiest solution is to have in your own database a new column for posts, something like "txid" and by default it's value is null. That way you know if transaction identifier is missing, then that post should be broadcast to the chain, and keep occasionally trying to broadcast it until txid is received. 🤗