Handling of Transactions After Network Partition
From what I understand, during a network partition, such as an island 🏝️ temporarily becoming ❌ isolated from the rest of the network, local miners continue producing blocks that reference only the blocks they can see.
When connectivity is restored, the global DAG merges both views, and the GhostDAG protocol recalculates the blue 🟦 and red 🟥 sets — with the globally heavier side dominating. The “island” blocks then become red because they were created in isolation.
-
What happens to the transactions in those red blocks? If we ignore double spending for a moment, these transactions are at least unconfirmed, right?
-
What would a typical merchant wallet do in such a case - does it automatically rebroadcast transactions that ended up in red blocks?
-
Is there any time limit on how long a partition can last before rebroadcasting is no longer possible (again, assuming no double-spend conflict)?
1 answer
If the partition lasts less than a finality period (12 hours currently IIRC) then when remerged, then the effect is simply that one branch will become mostly red. Since red block's transactions are included in the sequencing, the effect is non grave and non conflicting txs will be confirmed.
If a finality period has surpassed then at least one of the parties should reject that of the other and not be able to naturally remerge. Resolving of the partition would require manual intervention and one of the sides accepting the other's as "the truth".
Once resolved, merchants should rebroadcast transactions. Default transactions are not time dependent and can be rebroadcast as they are. I don't think time expiration is a thing in txs at all, though I guess it could have been.
0 comment threads
0 comment threads