6 Commits (acdba8474bf52787ef4bfd02e6fd7017ba4ca0e4)

Author	SHA1	Message	Date
Daniel Karzel	c0070f8fa7	Move files from `protocol` to appropriate module ... Some network and application specific code does not belong in the protocol module and was moved. Eventloop, recovery and the outside behaviour were moved to the respective application module because they are application specific. The `swap_setup` was moved into the network module because upon change both sides will have to be changed and should thus stay close together.	3 years ago
Daniel Karzel	08fecb8fe3	Peer check for incoming transfer proofs ... Bob validates that incoming transfer proof messages are coming from the peer-id of Alice. Currently Bob will ignore any transfer proof message that is not coming from the counterparty peer-id associated to the current swap in execution. Once we add support for trying to save received transfer proofs for swaps that are currently not in execution we can also adapy allowing this for different counterparty peer-ids. This requires access to the database in Bob's event loop.	3 years ago
Thomas Eizinger	b417950f99	Improve error reporting of failed protocols ... Instead of forwarding every error, we deliberately ignore certain variants that are not worth being printed to the log. In particular, this concerns "UnsupportedProtocols" and "ResponseOmission". To make this less verbose we introduce a macro for mapping a `RequestResponseEvent` to `{alice,bob}::OutEvent`. We use a macro because those `OutEvent`s are different types and the only other way of abstracting over them would be to introduce traits that we implement on both of them. To make the macro easier to use, we move all the `From` implementations that convert between the protocol and the more high-level behaviour into the actual protocol module.	4 years ago
Daniel Karzel	c976358c37	Multiple swaps with the same peer ... - Swap-id is exchanged during execution setup. CLI (Bob) sends the swap-id to be used in his first message. - Transfer poof and encryption signature messages include the swap-id so it can be properly associated with the correct swap. - ASB: Encryption signatures are associated with swaps by swap-id, not peer-id. - ASB: Transfer proofs are still associated to peer-ids (because they have to be sent to the respective peer), but the ASB can buffer multiple - CLI: Incoming transfer proofs are checked for matching swap-id. If a transfer proof with a different swap-id than the current executing swap is received it will be ignored. We can change this to saving into the database. Includes concurrent swap tests with the same Bob. - One test that pauses and starts an additional swap after the transfer proof was received. Results in both swaps being redeemed after resuming the first swap. - One test that pauses and starts an additional swap before the transfer proof is sent (just after BTC locked). Results in the second swap redeeming and the first swap being refunded (because the transfer proof on Bob's side is lost). Once we store transfer proofs that we receive during executing a different swap into the database both swaps should redeem. Note that the monero harness was adapted to allow creating wallets with multiple outputs, which is needed for Alice.	4 years ago
Thomas Eizinger	0c0a322a8f	Rename module to better represent what it contains ... This module provides an implementation of the RequestResponseCodec using a cbor serialization.	4 years ago
Thomas Eizinger	9979cc9f1f	Unify transfer-proof protocol to a single one ... Previously, we had two implementations of this protocol. To reduce code size, we make Alice and Bob use the same implementation.	4 years ago