When my service detects a
conflicted transaction (either
received) it rollbacks everything that was logically built upon this transaction. The "problem" is that transactions can go from category
sent/received if a blockchain reorganization happens, so my question is how long (how many blocks) should my service wait in order to be positive that a
conflicted transaction will never get included into a block?
I have found this question to be helpful: What is the longest blockchain fork that has been orphaned to date?