-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1 XMR] Allow for cooperative release of funds #693
Comments
I'd propose that we add a libp2p protocol over which Bob can connect to Alice after Bob has been punished to request Alice to reveal the Monero secret share. Bob can then use that secret to redeem the XMR. This behaviour would be invoked by a custom There should be no reason for Alice not to release it if we assume she's good-willed. This will essentially resolve the entire issue of users getting punished in practice (most sellers are not malicious. There's no incentive for them to be). |
Some more discussion can found here: #713 |
We use bounties to incentivize development and reward contributors. All issues available for a bounty have the To receive the bounty of this issue, you agree to these conditions:
|
Sounds good, I like it. Will try start on this next week. |
Awesome |
Any update? :( |
sorry! no progress yet. will let you know as soon as I have an update. |
I've begun work on https://github.com/comit-network/xmr-btc-swap/tree/cooperative-xmr-redeem Feel free to jump in |
TODO:
|
I made a working PoC, going to create a PR tomorrow after reviewing the code. But it will most likely introduce breaking database changes. |
The protocol allows for Alice to punish Bob by taking the BTC in case Bob never refunds. This can happen unintentionally as well. See #688 for example.
In that case, the two parties would have agreed to a cooperative release of funds. This should be possible to implement if we add:
asb
to print the Monero secret sharecli
to claim the Monero using the secret shareThe text was updated successfully, but these errors were encountered: