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

viperperidot notifications at github.com
Thu May 6 06:52:58 CEST 2021


Yes this is a great point that I overlooked, there will be fee savings through taproot as well! I know we are going through a big transition in development right now with starting to work on Bisq 2.0 (for fee improvements) and there are lot's of different ideas floating around on that. Some ideas more complicated than others, maybe the fee savings with taproot would be our most actionable approach right now until the work on rebuilding the base layer protocol starts (which is probably more complicated?). It sounds like taproot can be activated as early as November from my understanding, so if the prelim work for adding it to bisq could be started now then potentially we could have it ready for then? That would likely be sooner than the other major overhaul ideas so at least we could get some wins on fee savings sooner. Also from what I have seen for Bisq 2.0, using bitcoin as the base layer will still be an option so all the taproot work will still be applicable moving forward. As far as all of the other more complex features that taproot allows, those sound very exciting from what Max has pointed out here. Not sure if any thought or research has be given to if the new coding abilities provided by taproot.. those might be enough to solve the majority of our issues without moving off the base layer. It would be cool if bisq was one of the first projects to put the full capabilities of taproot to the test. Maybe you can get down to a 1 transaction protocol with taproot by leveraging some of the smart contract functionality? Anyway I have lots of questions myself just as a user but i'm looking forward to see what all can be done with this, very exciting. :)

-- 
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-702178
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210505/4094dfd0/attachment-0001.htm>


More information about the bisq-github mailing list