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

[chimp1984]

I would love to see some real data for the no-coiner onboarding problem. It is a problem which gets mentioned since ages but as far I am aware it is always brought up from Bitcoiners never from real "first timers" - which can be explained that they are not involved in Bisq yet. But I have also the suspicion that we interpret more of a problem into it as it is really and as there is no easy solution I think we should first find out how many users would be affected by that. Getting first BTC via friends, meetupds, ATM, vouchers should already cover 90% of those, and then for 5 users/year it will not be justified to invest a lot of work (and risk) to get a solution for those.

The reason I got more excited in the discussion is that those ideas might help us to get to a new trade protocol version (off chain would be still my favorite if we find a safe way how to do it).

Regarding fees:
One way to think about alternatives to direct trade fee payment could be to require BSQ purchase (BSQ bonds). This increase demand of BSQ and by that increase price which makes Bisq financially more sustainable (require less issuance if BSQ had higher value). So we could look for alternatives for fee payment for those who are willing to set up a BSQ bond and use that additionally as security tool. So it solves 4 problems at once:
- security tool
- no trade fee tx/input required -> can simplify trade protocol which leads to the following 2 benefits:
- lower miner fee
- better on-chain privacy

As BSQ bonds cannot be enforced (would cause too high burden to enter) there will be always the normal burned fee which helps to stabilize the issuance/burn rate.


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