mirror of
https://github.com/comit-network/xmr-btc-swap.git
synced 2025-04-27 11:19:18 -04:00

Our libp2p version is out of date, and we need to tackle the upgrade even though it's a significant undertaking. This'll also fix some other [issues](https://github.com/UnstoppableSwap/core/issues/95). ## This PR includes the following changes: - Breaking network protocol change: The libp2p version has been upgraded to 0.53 which includes breaking network protocol changes. ASBs and CLIs will not be able to swap if one of them is on the old version. - ASB: Transfer proofs will be repeatedly sent until they are acknowledged by the other party. This fixes a bug where it'd seem to Bob as if the Alice never locked the Monero. Forcing the swap to be refunded. - CLI: Encrypted signatures will be repeatedly sent until they are acknowledged by the other party - CLI+ASB: Libp2p network errors in request-response protocols are now propagated throught the event loop channels. This allows the caller to retry if an error occurs (e.g timeout) Closes https://github.com/UnstoppableSwap/core/issues/101, https://github.com/UnstoppableSwap/core/issues/95
Recommended IDE Setup
Requirements
- For compiling the Rust code:
cargo
andcargo tauri
(installation) - For running the Typescript code:
node
andyarn
- For formatting and bindings:
dprint
(cargo install dprint@0.39.1
) andtypeshare
(cargo install typeshare-cli
) - If you are on Windows and you want to use the
check-bindings
command you'll need to manually install the GNU DiffUtils (installation) and GNU CoreUtils (installtion). Remember to add the installation path (probablyC:\Program Files (x86)\GnuWin32\bin
) to thePATH
in your enviroment variables.
Start development servers
For development, we need to run both vite
and tauri
servers:
cd src-gui
yarn install && yarn run dev
# let this run
cd src-tauri
cargo tauri dev --no-watch -- -- --testnet
# let this run as well
Generate bindings for Tauri API
Running yarn run dev
or yarn build
should automatically re-build the Typescript bindings whenever something changes. You can also manually trigger this using the gen-bindings
command:
yarn run gen-bindings
You can also check whether the current bindings are up to date:
yarn run check-bindings