Replies: 2 comments 2 replies
-
Thanks for reaching out! I guess it shares some basic ideas. I just read quickly your readme, so apologize if I misunderstood anything but to me the central role of a coordinator seems problematic from both security, scalability and regulatory point of view. If for dispute resolution no other solution than a 3rd party can be found it might be acceptable but I would not extend its role more as absolutely needed. |
Beta Was this translation helpful? Give feedback.
-
Thanks for letting us know of your efforts! Actually there are quite a number of common idea, which we were thinking of. Also I like that you guys are using MuSig2 to add more privacy to the happy path of the protocol. |
Beta Was this translation helpful? Give feedback.
-
We've been working on a taproot p2p trading pipeline over at the RoboSats project which could possibly be used in Bisq too. It needs 2 onchain transactions to finish the trade. The current state is a working demonstrator in Rust but no production ready library/application yet. You can have a look at the pipeline in the README.md of the Repo https://github.com/RoboSats/taptrade-core. Would this fit in your architecture/be of interest to the Bisq project? If so we could consider design choices in further development to allow for simpler integration in Bisq too.
Beta Was this translation helpful? Give feedback.
All reactions