Please note, your funds are never lost! Connext is always non-custodial and your funds are always retrievable. In the worst possible case, you can reclaim your funds on the original chain 72 hours from the time you sent them.
This document is also available in:
When debugging a stuck transfer, it is important to understand the lifecycle of a crosschain transaction.
The NXTP crosschain transaction lifecycle.
There are three phases:
Once prepared, the transfer may be cancelled once it expires by either party if it is not fulfilled. Alternatively, the person who is owed funds can cancel the transfer prior to expiry rather than fulfilling. This means as soon as the transaction has been prepared, the user can cancel the transfer on the receiving chain while the router can cancel the transfer on the sending chain.
The following will show pictures from xpollinate.io, but the steps are the same to debug any NXTP transaction even if it is initiated from a different website!
Make sure the funds have left your wallet, and the transaction you are concerned about is related to xpollinate. Our preferred explorer is tenderly, but you should be able to see the transaction calling
prepare on any explorer!
Transaction Id from the UI
The Transaction Id is the unique identifier for your crosschain transaction. It's the most helpful for finding out information about a given transfer using the explorer.
Look up the transaction using the ID on connextscan.io.
If you do not see the transaction on the explorer, check the subgraph sync status on xpollinate.io. If the status is
unsynced, you will have to wait a bit longer for your transaction to be picked up by the network.
Easily check the subgraph sync status from the xpollinate website. If the sending or receiving chain subgraph shows "unsynced", expect longer wait times for your transfer.