wait reorgs happening every hour?! somehow i assumed it as a rare events, bc some production pipelines i reviewed are just watching for event logs to increase balance in database and totally ignoring possible reverts, are those pipelines doomed or im missing something??
Yes, especially for blockchains with high-speed block production rates, short one or two block reorgs are very common due to network latency. Reorgs that last for many blocks are rare and can become a problem for the network. The kind of pipelines you're referring to would need to handle those reorgs on the client side, whereas, with QuickNode Streams, you can create more robust and error-proof pipelines. You can set the Stream with reorg configuration either to delay the latest block streaming (you can set the block delay for a number of blocks) or you can even restream on reorg where Stream will automatically restream the updated parts in real-time💪. Learn more here www.quicknode.com/docs/streams/reorg-handling
wait reorgs happening every hour?! somehow i assumed it as a rare events, bc some production pipelines i reviewed are just watching for event logs to increase balance in database and totally ignoring possible reverts, are those pipelines doomed or im missing something??
Yes, especially for blockchains with high-speed block production rates, short one or two block reorgs are very common due to network latency. Reorgs that last for many blocks are rare and can become a problem for the network. The kind of pipelines you're referring to would need to handle those reorgs on the client side, whereas, with QuickNode Streams, you can create more robust and error-proof pipelines. You can set the Stream with reorg configuration either to delay the latest block streaming (you can set the block delay for a number of blocks) or you can even restream on reorg where Stream will automatically restream the updated parts in real-time💪. Learn more here www.quicknode.com/docs/streams/reorg-handling