[bisq-network/proposals] Federated trade fee aggregators (#329)

sqrrm notifications at github.com
Sat May 8 17:40:44 CEST 2021


I think the contract OP_RETURN that's part of the deposit tx is not necessary. The same security could be had by both parties signing the contract with the pubkeys used in the deposit tx and have the parties save that copy locally.

As long as BSQ or payment to burning man/woman is part of the trade tx it would still be possible to profile Bisq trade txs so that's where the FA would help. The FA would be able to see how much fees a certain bond owner has paid, but not see which trades and not know anything more about that bond owner. It might be possible to associate likely candidate trades with certain fee payments, but it's not obvious. If we stopped publishing trade statistics it might not be possible at all since those Bisq trades would not have any specific signature on chain, especially if we can get the taproot single tx protocol running.

Burning woman still suffers the issue of many outputs, although they wouldn't have to be aggregated as a singular operation, but I think the on chain footprint is similarly large to the burning man. The extra output to the burning woman, the extra BSQ input from burning woman and BSQ change.

-- 
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/proposals/issues/329#issuecomment-835406145
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210508/b9bfcdae/attachment-0001.htm>


More information about the bisq-github mailing list