8 Commits (3e82211a8202023406e33a18926eda1de01cc16f)

Author	SHA1	Message	Date
Lucas Soriano del Pino	5395303a99	Test on-chain protocol happy path	4 years ago
Lucas Soriano del Pino	50ed74319f	Simplify xmr-btc/tests Monero wallet ... - Make it the same for Alice and Bob. - Make it contain a wallet client instead of the `Monero` struct. Also: Remove `Container` from inside `Monero` struct. The caller of `new` can simply ensure that `Container` is not dropped to keep the container alive. This makes the `Monero` struct easier to work with, as it just holds the data necessary to create the different clients created during `init`, and does not have any lifetime restrictions.	4 years ago
Lucas Soriano del Pino	55629838f4	Implement test function that calls action_generator_alice	4 years ago
Lucas Soriano del Pino	7c99415cff	Write action_generator_alice	4 years ago
Lucas Soriano del Pino	969ca63081	Split RefundBitcoin into CancelBitcoin and RefundBitcoin	4 years ago
Lucas Soriano del Pino	176b2195e3	Make ReceiveTransferProof async and take &mut self	4 years ago
Lucas Soriano del Pino	4723626fc0	Suppress compiler noise in tests folder ... By having two modules that declare and use the `harness` module we ran into a situation where not all parts of the `harness` module were being used by both of these other test modules. This was producing annoying warnings. For now this can be solved by marking the `harness` module declaration as public. This has no real effect since modules under `/tests` cannot be depended on elsewhere, but it satisfies the compiler. It does mean that we will not hear about unused functions, but this change should be temporary and it's a very minor problem given that it's just test code.	4 years ago
Lucas Soriano del Pino	5daa3ea9a8	[WIP] Generate actions for Bob's on-chain protocol ... Mimics what @thomaseizinger did here [1] and here [2]. This has the advantage that the consumer has more freedom to execute `Action`s without having to implement particular traits. The error handling required inside this protocol-executing function is also reduced. As discussed with Thomas, for this approach to work well, the trait functions such as `receive_transfer_proof` should be infallible, and the implementer should be forced to hide IO errors behind a retry mechanism. All of these asynchronous calls need to be "raced" against the abort condition (determined by the `refund_timelock`), which is missing in the current state of the implementation. The initial handshake of the protocol has not been included here, because it may not be easy to integrate this approach with libp2p, but a couple of messages still need to exchanged. I need @tcharding to tell me if it's feasible/good to do it like this. [1] https://github.com/comit-network/comit-rs/blob/move-nectar-swap-to-comit/nectar/src/swap/comit/herc20_hbit.rs#L57-L184. [2] e584d2b14f/nectar/src/swap.rs (L716-L751).	4 years ago