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

Manuel notifications at github.com
Fri Nov 27 19:34:02 CET 2020


Then, if we want to use this kind of trades as a testbed for the off-chain protocol, probably requiring a BSQ bond would be the way to go.   An independent BSQ bond would be required for each different (hash) payment account, so if someone generates many payment accounts that are internally the same (i.e. same account number), we don't care because he will have to pledge a bond for each one of them.

To avoid too many paralell trades, maybe we could have an extended order book (visually hidden) where all the offers within the ongoing trades are still accesible with a hash of the payment account.  If for example we don't allow more than 1 concurrent offer with the same hash, a second offer would be rejected (or not shown) in the public order book, and would only be allowed (or shown) in the public order book once the previous offer is completed or canceled. 

This is the only "intelligent" thing (if intelligent at all or not discussed before) that I can contribute for the off chain protocol. Regarding the onboarding, it could be tried on a second stage.  I´ll write it on a separate comment. 

-- 
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-734947822
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201127/2c34ff60/attachment.htm>


More information about the bisq-github mailing list