wal said:



Under what circumstances is it possible for an IX transaction (one where instantlock=true) to fail ? I'm referring to a TX that is *received* by a full node from the network.



Or to rephrase, does a TX with instantlock=true mean the TX will definitely be mined even when it hasnt actually been mined yet (as confirmations=0) Thanks @UdjinM6 Under what circumstances is it possible for an IX transaction (one where instantlock=true) to fail ? I'm referring to a TX that is *received* by a full node from the network.Or to rephrase, does a TX with instantlock=true mean the TX will definitely be mined even when it hasnt actually been mined yet (as confirmations=0) Click to expand...

"Locked" tx means that:1. tx was broadcasted to at least some masternodes;2. masternodes who are required to vote for it received it, checked it and voted;3. votes were brodcasted by them and reached at least your node.Taking into account network topology (which is pretty complex, (master)nodes have multiple interconnections etc.), it's very unlikely that IS tx and IS votes were relayed only by masternodes that were required to vote for it and your node. It's most likely that the whole network (or at least the vast non-isolated majority of it) has both IS tx and all required IS votes to lock it. IS tx lock is going to be kept by every online node until it has at least 24 confirmations. This guarantees with very high probability that no other txes trying to double-spend the same inputs are going to be accepted by the network. This does NOT guarantee however that IS tx is going to be mined in the very next block but at the same time it's pretty likely because IS txes have higher fee comparing to most other txes (by default).