It would be nice if relative paths are used instead of using relative paths like here:

Add an option for testnet config:

./mwixnet --testnet init-config

#3 (comment)

To avoid blocking progress on milestone 1, we merged it as there were only a few minor remarks some of which need to be discussed further.

Leftovers from milestone 1

• duplicate inputs/outputs handling
• real example in README

I suggest these are addressed here and we get them resolved in milestone 2.

init-config should create directories ~/.grin/[chaintype] if they don't exist. The command currently fails without a useful error if these directories aren't already in place)

The derive_outputs and derive_kernels apis (https://github.com/mimblewimble/mwixnet/blob/main/src/rpc.rs#L31) will be implemented along with the changes to execute_round necessary to consume them.

The minimal space efficiency gains fail to justify the additional complexity of our current scheme.
#18 (comment)

Milestone 2 PR Discussion:

yeastplume: Comment should ideally be spat out in the config file, similar to grin and grin-wallet (can be done later)

#3 (comment)

#3 (comment)

Starting up server with node / wallet properly configured:

grin_test_mwixnet_container  | thread 'main' panicked at src/bin/mwixnet.rs:185:37:
grin_test_mwixnet_container  | called `Result::unwrap()` on an `Err` value: Custom { kind: Other, error: TryCurrentError { kind: NoContext } }
grin_test_mwixnet_container  | stack backtrace:
grin_test_mwixnet_container  |    0:     0x562bd5002785 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h1e1a1972118942ad
grin_test_mwixnet_container  |    1:     0x562bd502bb9b - core::fmt::write::hc090a2ffd6b28c4a
grin_test_mwixnet_container  |    2:     0x562bd4ffedff - std::io::Write::write_fmt::h8898bac6ff039a23
grin_test_mwixnet_container  |    3:     0x562bd500255e - std::sys_common::backtrace::print::ha96650907276675e
grin_test_mwixnet_container  |    4:     0x562bd5003819 - std::panicking::default_hook::{{closure}}::h215c2a0a8346e0e0
grin_test_mwixnet_container  |    5:     0x562bd500355d - std::panicking::default_hook::h207342be97478370
grin_test_mwixnet_container  |    6:     0x562bd5003cb3 - std::panicking::rust_panic_with_hook::hac8bdceee1e4fe2c
grin_test_mwixnet_container  |    7:     0x562bd5003b94 - std::panicking::begin_panic_handler::{{closure}}::h00d785e82757ce3c
grin_test_mwixnet_container  |    8:     0x562bd5002c49 - std::sys_common::backtrace::__rust_end_short_backtrace::h1628d957bcd06996
grin_test_mwixnet_container  |    9:     0x562bd50038c7 - rust_begin_unwind
grin_test_mwixnet_container  |   10:     0x562bd44a1333 - core::panicking::panic_fmt::hdc63834ffaaefae5
grin_test_mwixnet_container  |   11:     0x562bd44a17e6 - core::result::unwrap_failed::h82b551e0ff2b2176
grin_test_mwixnet_container  |   12:     0x562bd462c3d4 - mwixnet::real_main::h024136c341448eb1
grin_test_mwixnet_container  |   13:     0x562bd4629466 - mwixnet::main::h41236ebf12b3df4a
grin_test_mwixnet_container  |   14:     0x562bd4608593 - std::sys_common::backtrace::__rust_begin_short_backtrace::hffd5985076f02833
grin_test_mwixnet_container  |   15:     0x562bd4749f59 - std::rt::lang_start::{{closure}}::h9bcea5e838a663e3
grin_test_mwixnet_container  |   16:     0x562bd4ff8600 - std::rt::lang_start_internal::h3ed4fe7b2f419135
grin_test_mwixnet_container  |   17:     0x562bd462d3c5 - main
grin_test_mwixnet_container  |   18:     0x7f24a6e5a24a - <unknown>
grin_test_mwixnet_container  |   19:     0x7f24a6e5a305 - __libc_start_main
grin_test_mwixnet_container  |   20:     0x562bd44a1b61 - _start
grin_test_mwixnet_container  |   21:                0x0 - <unknown>
grin_test_mwixnet_container  | Server password: 

Automated tests are needed that will spin up multiple mwixnet nodes (1...N) and perform swaps that test the entire multi-server flow.

I wonder if probably the service should not run if the APIs are not available.

• #6
• #14
• #13
• #5
• #4
• #8
• #9
• #10
• #19

Debian 12
rustc 1.77.2 (25ef9e3d8 2024-04-09)
cargo 1.77.2 (e52e36006 2024-03-26)

Following the instructions and adding + 'serialize to line 1151 of serialize.rs works, but should be fixed. Also given this warning at the end:

When running 'cargo install --path ~/mwixnet'

Please advise on how to proceed from here, I have no problem understanding what to do once installed, but can't debug the install myself

The first mwixnet node keeps all unfinished swap requests in volatile memory. Since CoinSwaps will only occur a few times per day, a process interruption could result in lots of swap requests being lost. We should instead serialize all unfinished swaps to disk and automatically recover them when an interrupted process is restored.

#3 (comment)

As part of milestone 3, the following protections will be added to help ensure CoinSwap transactions cannot be easily lost due to short chain reorgs:

1. If a transaction is broadcast but not accepted by the network due to inputs being already spent, the mwixnet servers will try to rebuild the transaction, pruning any swaps for inputs already spent.
2. If a CoinSwap transaction is included in a block, but later removed by a reorg, the mwixnet server will try to rebroadcast the transaction. If the transaction is no longer valid, try to rebuild it, pruning any swaps for inputs already spent.

Reasonable limits will be set for the size of the swap cache and the number of attempts at rebuilding the CoinSwap transaction for a round.