[bisq-network/bisq] Add option to make trade 'reason' less obvious (#2869)

[Conza]

Yes to all. In terms of maker or taker, I'd be asking what do we want to incentivise?

Maker, yeah? They get ability to control narrative a bit more? 🤔

E.g. If they're a seller of BTC (maker) and want a particular description in bank that associates with a cover story. Don't want to risk their selling operation?

E.g. If they're a buyer of BTC (maker), I generally want to accommodate seller of BTC. So would probably engage with them and ask if they wanted a particular cover used?

I probably wouldn't specify one from the get go.. but then there's no way to amend and save during trade?

Hmm
________________________________
From: pazza <notifications at github.com>
Sent: Tuesday, December 15, 2020 12:49:15 PM
To: bisq-network/bisq <bisq at noreply.github.com>
Cc: Conza <conza_ at hotmail.com>; Mention <mention at noreply.github.com>
Subject: Re: [bisq-network/bisq] Add option to make trade 'reason' less obvious (#2869)


Sure. And same with vice versa (seller)?

Hi @Conza88<https://github.com/Conza88> thanks for the feedback.

Yes, it would be the same. Think it should be maker/taker only. If it was maker and taker you would get 2 alterative options and it would get confusing.

I'd like an "(i)" that when hovered over indicates why, it's purpose.

Yes, I think it would be important to offer some more info to the reason.

I guess if maker of BTC sale put in e.g. "gun sale" and in my country that's illegal to own, that could cause issues - in which case, you'd just not do it...

Yes, counterparty could always ignore their peer's suggestion, this would always be acceptable.

Do you think it should be maker or taker that sets the alternative Trade ID? I am leaning towards taker as they can then learn which traders will include their suggestion and use this knowledge when taking future offers.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/bisq-network/bisq/issues/2869#issuecomment-745016910>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMMLWYQAYZP2EYXLTUYM6QDSU3FCXANCNFSM4HS7RAMQ>.


-- 
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/bisq/issues/2869#issuecomment-745179427
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201215/b3888067/attachment-0001.htm>