mirror of
https://github.com/comit-network/xmr-btc-swap.git
synced 2024-10-01 01:45:40 -04:00
Work in review comments
This commit is contained in:
parent
83b6b78d17
commit
406ddc6b15
@ -36,12 +36,15 @@ The questions are split between `M`aker (liquidity provider) and `T`aker (normal
|
|||||||
| | | | configure Tor for trading | TM |
|
| | | | configure Tor for trading | TM |
|
||||||
| | | Do users care about P2P? | use a centralized service to find makers | TM |
|
| | | Do users care about P2P? | use a centralized service to find makers | TM |
|
||||||
| | | | user a decentralized service to find makers | TM |
|
| | | | user a decentralized service to find makers | TM |
|
||||||
|
| | | | discover peers automatically | TM |
|
||||||
| | | | add peers manually | TM |
|
| | | | add peers manually | TM |
|
||||||
| Software Setup | How does the user want to manage the swap software setup? | Is the user willing to download software? | download software (swap execution daemon) before being able to do a swap | T |
|
| Software Setup | How does the user want to manage the swap software setup? | Is the user willing to download software? | download software (swap execution daemon) before being able to do a swap | T |
|
||||||
| | | How does the user want to manage long-running tasks? | keep a GUI/CLI open for the whole length of the swap execution | T |
|
| | | How does the user want to manage long-running tasks? | keep a GUI/CLI open for the whole length of the swap execution | T |
|
||||||
| | | | keep a computer running (that hosts the daemon) for the whole length of the swap execution | T |
|
| | | | keep a computer running (that hosts the daemon) for the whole length of the swap execution | T |
|
||||||
| | | | keep the browser open for the whole length of a swap | T |
|
| | | | keep the browser open for the whole length of a swap | T |
|
||||||
| Protocol | How important are protocol details to the user? | Does the user care about the incentives of each role? | have different steps (locking first vs second) depending on the direction of the swap | TM |
|
| Protocol | How important are protocol details to the user? | Does the user care about the incentives of each role? | have different steps (locking first vs second) depending on the direction of the swap | TM |
|
||||||
|
|
||||||
|
|
||||||
## Prototypes
|
## Prototypes
|
||||||
|
|
||||||
In the initial project description we distinguished product `A` a single market-maker product and product `B` a product including peer-to-peer discovery and multiple makers.
|
In the initial project description we distinguished product `A` a single market-maker product and product `B` a product including peer-to-peer discovery and multiple makers.
|
||||||
@ -75,7 +78,7 @@ Example:
|
|||||||
| run both his own Bitcoin and Monero node | TM | T | T | | |
|
| run both his own Bitcoin and Monero node | TM | T | T | | |
|
||||||
| use a wallet that connects to third party nodes | TM | | | | |
|
| use a wallet that connects to third party nodes | TM | | | | |
|
||||||
| send signed transactions through third part nodes | TM | | | | |
|
| send signed transactions through third part nodes | TM | | | | |
|
||||||
| run his own blockchain full node | TM | | | | |
|
| run his own blockchain full node | TM | T | T | | |
|
||||||
| run an SPV node (Bitcoin) | TM | | | | |
|
| run an SPV node (Bitcoin) | TM | | | | |
|
||||||
| fund and redeem from existing wallets | TM | T | T | | |
|
| fund and redeem from existing wallets | TM | T | T | | |
|
||||||
| fund from existing Monero wallet, redeem to new Bitcoin wallet | TM | | | | |
|
| fund from existing Monero wallet, redeem to new Bitcoin wallet | TM | | | | |
|
||||||
@ -91,12 +94,15 @@ Example:
|
|||||||
| configure Tor for trading | TM | | | | |
|
| configure Tor for trading | TM | | | | |
|
||||||
| use a centralized service to find makers | TM | T | T | | |
|
| use a centralized service to find makers | TM | T | T | | |
|
||||||
| user a decentralized service to find makers | TM | | | | |
|
| user a decentralized service to find makers | TM | | | | |
|
||||||
|
| discover peers automatically | TM | | | | |
|
||||||
| add peers manually | TM | | | | |
|
| add peers manually | TM | | | | |
|
||||||
| download software (swap execution daemon) before being able to do a swap | T | | | | |
|
| download software (swap execution daemon) before being able to do a swap | T | | | | |
|
||||||
| keep a GUI/CLI open for the whole length of the swap execution | T | | | T | T |
|
| keep a GUI/CLI open for the whole length of the swap execution | T | | | T | T |
|
||||||
| keep a computer running (that hosts the daemon) for the whole length of the swap execution | T | T | T | T | T |
|
| keep a computer running (that hosts the daemon) for the whole length of the swap execution | T | T | T | T | T |
|
||||||
| keep the browser open for the whole length of a swap | T | | | | |
|
| keep the browser open for the whole length of a swap | T | | | | |
|
||||||
| have different steps (locking first vs second) depending on the direction of the swap | TM | | | T (M) | T (M) |
|
| have different steps (locking first vs second) depending on the direction of the swap | TM | | | T (M) | T (M) |
|
||||||
|
|
||||||
|
|
||||||
Legend:
|
Legend:
|
||||||
|
|
||||||
```
|
```
|
||||||
|
Loading…
Reference in New Issue
Block a user