[bisq-network/proposals] Using PoW for the P2P network messages as dos protection (#268)

Manuel notifications at github.com
Mon Nov 30 22:08:35 CET 2020


> If the bond would be part of the multisig we could not use 1 bond for multiple trades

If you look at the bond set up as mining new coins (following the Monero analogy), a 5000 BSQ Bond could generate for example 10 "bond-coins" or "bond-tokens" ("worth" 500 BSQ each), so you could use the bond for 10 concurrent trades worth 500 BSQ each.  If this is not possible, you would need to set up several smaller bonds (one "bond-coin" per each bond) to support several concurrent trades.  This is more expensive (mining fees) but in turn improves a bit on the anonimity set.

> BSQ does not support MultiSig and a bond need to be sitting on 1 utxo with a timelock to give the option for confiscation

The BSQ Bond would still be the same than now.  Imagine for one second that you have an additional sidechain, which is a Monero fork managed by trusted nodes (no PoW).  You would create "bond-coins" in that sidechain by setting up a bond, you would destroy them when recovering the BSQ Bond in the BSQ chain.  You would use the coins to back each offer taking advantage of the built-in untreacebility of Monero.

Of course, I know my suggestion is crazy, but I write it just in case it sparks some ideas that could be applied to the off-chain protocol.  What I think is not that crazy is that the problem we are facing with the traceability of trades is the same, if not identical, to what privacy coins have apparently solved.  So maybe it could be possible or reasonable to copycat their privacy techniques into the new trade protocol?

-- 
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/268#issuecomment-736057116
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201130/ca158361/attachment.htm>


More information about the bisq-github mailing list