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

Max Hillebrand notifications at github.com
Thu May 6 10:05:17 CEST 2021


If fee savings are the priority, then yes, tweaking the current protocol to use Taproot will already bring in a decent fee savings. I forget the exact percentage of tx vbyte decrease of 2-out-of-2 multisig. Probably roughly 50% reduction in script and witness size, which might take total fee savings to roughly 10%. [again, numbers are my rough guesses]

I think much more substantial fee savings can be accomplished when re-architecting the trade protocol to have less on-chain transactions in general. Cut it from 4 to 2 transactions, and you have a 50% fee-savings on the whole trade.

Here one project worth noting: @RubenSomsen's [Succinct Atomic Swap](https://gist.github.com/RubenSomsen/8853a66a64825716f51b409be528355f) idea utilizes pre-signed transactions and private key sharing, to reduce cross-chain swaps from 4 to 2 transactions. This comes with an online requirement for a certain period of time after the trade for one party. Since Bisq is somewhat designed to be [almost] always online, this might be a reasonable trade-off.

I added a minor contribution with [**externally funded** SAS](https://github.com/MaxHillebrand/research/blob/master/ExternallyFundedSuccinctAtomicSwaps.md), where one further transaction can be saved by the actual swap participants.

-- 
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-702704
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210506/e96c2a5a/attachment.htm>


More information about the bisq-github mailing list