11 Commits (9eae0db9ac090fd8c6f47eb2b03999ce21bdedad)

Author	SHA1	Message	Date
Franck Royer	8fd2620b83	Improve names for messages 4 and 5	3 years ago
Franck Royer	d2a1937f51	Use `Message4`	3 years ago
Franck Royer	9a5e35c1bd	Rename `bob::Message2` to `Message5` ... As per the proposed changed in the sequence diagram. The aim is to have a unique terminology per message instead of having the same name for 2 consequent messages that share the same behaviour. Note that the aim is to remove the shared `RequestResponse` behaviours.	3 years ago
Franck Royer	f2a25ee49b	Move definitions out of lib.rs	3 years ago
Daniel Karzel	3593f5323a	Bob saves lock proof after received so he can resume swap	3 years ago
bors[bot]	4e858197c9	Merge #149 ... 149: Fix Alice redeem scenario r=da-kami a=da-kami Follow up of #144, partial fix of https://github.com/comit-network/xmr-btc-swap/issues/137 Fix Alice redeem scenario - Properly check the timelocks before trying to redeem - Distinguish different failure scenarios and reactions to it. - if we fail to construct the redeem transaction: wait for cancel. - if we fail to publish the redeem transaction: wait for cancel but let the user know that restarting the application will result in retrying to publish the tx. - if we succeed to publish the tx but then fail when waiting for finality, print error to the user (secreat already leaked, the user has to check manually if the tx was included) Co-authored-by: Daniel Karzel <daniel@comit.network>	3 years ago
Franck Royer	ae8134f04e	Replace amounts messages with swap res/req	3 years ago
Daniel Karzel	6a75c840b5	Fix Alice redeem scenario ... - Properly check the timelocks before trying to redeem - Distinguish different failure scenarios and reactions to it. - if we fail to construct the redeem transaction: wait for cancel. - if we fail to publish the redeem transaction: wait for cancel but let the user know that restarting the application will result in retrying to publish the tx. - if we succeed to publish the tx but then fail when waiting for finality, print error to the user (secreat already leaked, the user has to check manually if the tx was included)	3 years ago
Daniel Karzel	f8848aca55	Describe additional state for ToDo that might cause trouble ... If we wait for lock transaction confirmations immediately after sending the transaction without saving this state to the DB this might cause locking the money twice. An additional state is needed for such a scenario.	4 years ago
Franck Royer	17356eaff9	Do not guard waiting for encrypted signature with arbitrary timeout ... We already select waiting for this message with the cancellation expiry, we do not need add another guard that tries to guess how long it would for the Monero transaction to be finalised.	4 years ago
rishflab	c900d12593	Merge xmr_btc crate ... Created network, storage and protocol modules. Organised files into the modules where the belong. xmr_btc crate moved into isolated modulein swap crate. Remove the xmr_btc module and integrate into swap crate. Consolidate message related code Reorganise imports Remove unused parent Message enum Remove unused parent State enum Remove unused dependencies from Cargo.toml	4 years ago