15 Commits (e66e84085b0211bd2c5e43056c93913aedee7fa0)

Author	SHA1	Message	Date
Daniel Karzel	e66e84085b	Rename Bob's Behavior Failure to CommunicationError ... Failure does not express what the error represents. It is only used for communication errors for quote requests, receiving the XMR transfer proof and sending the encryption signature.	4 years ago
Franck Royer	9ded728879	The first message is actually a quote or rate request	4 years ago
Franck Royer	bfc19d5628	Remove acknowledgements processing ... We are aware of issues of timeouts when waiting for acknowledgements. Also, to properly supports acks in a multiple swap context, we need to revert to doing event processing on the behaviour so that we can link leverage the `RequestResponse` libp2p behaviour and link the messages requests ids to swap ids when receiving an ack or response. Acks are usefully for specific scenarios where we queue a message on the behaviour to be sent, save as sent in the DB but crash before the message is actually sent. With acks we are able to resume the swap, without ack, the swap will abort (refund).	4 years ago
Franck Royer	eefb1b3b16	Use event_process = false for Bob ... As we do not process the event, we can just implement the needed `From` traits.	4 years ago
Franck Royer	081237bb6f	Remove unused behaviours	4 years ago
Franck Royer	3fa4ffa82c	Implement new behaviour for execution setup	4 years ago
Franck Royer	cc76b201b5	Do not consider encrypted signature sent until it's ack'd	4 years ago
rishflab	77fc5743a2	Upgrade tokio to 1.0 ... Upgrade bitcoin harness dependency to latest commit Upgrade backoff to fix failing tests. The previous version of backoff had a broken version of the retry function. Upgraded to a newer comit which fixes this problem. Upgrade hyper to 0.14 as the 0.13 was bringing in tokio 0.2.24 Upgraded bitcoin harness to version that uses tokio 1.0 and reqwest 0.11 Upgrade reqwest to 0.11. Reqwest 0.11 uses tokio 1.0 Upgrade libp2p to 0.34 in preparation for tokio 1.0 upgrade	4 years ago
Franck Royer	b62ef9c2d9	Harmonizing naming	4 years ago
Franck Royer	8fd2620b83	Improve names for messages 4 and 5	4 years ago
Franck Royer	d2a1937f51	Use `Message4`	4 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.	4 years ago
Franck Royer	ae8134f04e	Replace amounts messages with swap res/req	4 years ago
Daniel Karzel	67e925fe1f	Refactor Bob's peer-id and identity to be handled on the outside ... Doing this in the behaviour is a weird indirection that is not needed.	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