Comment on page
From the creation up to the completion step the swap lifecycle goes as follows:
Whenever the swap is created, either programmatically or from the Layerswap UI, the swap has
user_transfer_pendingstatus. At this stage, Layerswap is awaiting the incoming transaction to the deposit address in the source network to match it with the corresponding swap. Users have the option to cancel the swap.
If the user decides to cancel the swap, the swap status will be changed to cancelled. The swap can still be retrieved for historical purposes, however, no incoming transaction will be matched against the swap.
If the user does not cancel the swap and also does not initiate the transaction in the source network within
4 days, the Swap status will be changed to expired.
After the user has initiated the transfer to the deposit address in the source network, Layerswap will monitor the blockchain network to verify that a transaction has been received. After receiving the transaction and matching it with the corresponding swap, Layerswap will create an Input transaction object, which will describe the transaction sent by the user and connect it with the corresponding swap. The swap status will be changed to
After receiving the transaction and setting the swap status to
ls_transfer_pending, Layerswap will initiate the outgoing transaction to the user-specified destination address in the destination network and the swap status will be changed to
If there is an issue with Layerswap and the outgoing transaction to the user-specified destination address could not be initiated, the swap status will be changed to failed.
Last modified 30d ago