This is a multi-step multi-chain operation and critical to security, and probably needs a big Barrier that stops processing new outbound txs and wait for broadcasted txs to be mined and confirmed.
The barrier will wait for all signed & broadcasted txs to confirm (if not, they need to be cancelled).
Question: how does zetacore distinguish between pending txs and broadcasted txs?
Depends on the admin stopping functionality. You need to be able to do certain things during migrations.
This is a multi-step multi-chain operation and critical to security, and probably needs a big Barrier that stops processing new outbound txs and wait for broadcasted txs to be mined and confirmed.
The barrier will wait for all signed & broadcasted txs to confirm (if not, they need to be cancelled).
Question: how does zetacore distinguish between pending txs and broadcasted txs?
Depends on the admin stopping functionality. You need to be able to do certain things during migrations.
Proposed solution