[bisq-network/proposals] Trust-Minimizing Solution for Onboarding New Bisq Users Without BTC Ownership (Nocoiners) (#214)

dav1dpgit notifications at github.com
Sun Apr 19 07:20:27 UTC 2020


Thanks for the comments.  

**Seller sends a payment invoice to buyer: That reveals account details of veteran Bisq users for free.**  First step in the process is the buyer revealing his/her account details to which the BTC seller sends an invoice.  Bisq could maintain a list of name-and-shame scammer accounts if this is an ongoing concern against which any subsequent trades could be checked by the seller.  Additionally, if a seller wishes for information to be protected some payment services allow for pseudonyms or pseudo-accounts to be used for invoicing counterparties.  I’ll check around for others but this kind of anonymity is available for certain payment options.

**Utilization of a BTC onboarding transaction by a buyer is a one-time opportunity.
Unless buyers create a new Tor address and new payment account.**
Yes, hence limiting the size of the transaction and putting the burden of payment of all fees onto the  buyer.  We could also increase the Bisq fees for this kind of transaction if there is concern they are not sufficient given the trading burden, but that would incur additional coding, I am sure.

**BTC buyer sends payment to seller within payment methodology, which the seller confirms within Bisq
f the fiat payment is already received, there's no need to use multisig or security deposit. Seller could just release the bitccoin to settle the trade.**
I am looking to minimize the change to the transaction flow of Bisq, merging this process into existing framework. 

**What if seller does not confirm? Seller is at risk of losing an old payment account, which could be sufficient to make them confirm the trade. But not for a 1% spot price. For small trades just mining fees can be over 1%.**
Agree on the 1%, so it could easily be set to something higher.  10%?

-- 
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/214#issuecomment-616064648
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200419/d80651ef/attachment.html>


More information about the bisq-github mailing list