[bisq-network/bisq] Utilizing taproot to mask Bisq on-chain transactions (#5468)

[Max Hillebrand]

Yes, I think this is a priority requirement as soon as taproot is activated, the fee savings and privacy improvements are too numerous to ignore.

Just to get the conversation going, here a two basic ways taproot can be used to improve things:

- MuSig, replace script-based multisignatures with Schnorr public key and signature aggregation.
- Taptree, replace "single-line script" with a tree structure of spending condition, in the cooperative case use keyspend, in the uncooperative case reveal only one out of X spending conditions.

There are numerous more fundamental improvements to the whole Bisq trade architecture that are possible now [consider Lightning and DLC oracles too].

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/discussions/5468#discussioncomment-697623
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210505/e2f80099/attachment.htm>