[owl352]

Issue

At the moment, the zmq channel will not be deployed again in case of an unexpected closure, which will cause indexer to stop synchronizing transactions in real time, which is quite a big problem. Also, in case of problems with zmq, you need to add a backup source of pending transactions from rpc, which will allow you to insure yourself in case of problems with zmq.

Apart from this, there is also the problem that transactions that are already included in the block may still be displayed as pending, although this may not be the case.

Things done

• Added an attempt to reconnect to zmq in case we don't receive messages for 10+ minutes.
• In live-sync mode, we now also poll the rpc to receive mempool transactions every 10 seconds. In this communication channel, transactions will arrive later than in zmq, and due to internal checks, we will simply skip the data if it already exists.
• Fixed a bug where a transaction from a mempool receives confirmation, but is still pending.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
dashscan	Ready	Preview	Oct 19, 2026 8:43pm UTC