Bisq Support Calls

[huey735]

Issue for summary of Bisq Support Calls

[huey735]

Support call 2021-04-21

Topics

1. Development:

   1. [SUGGESTION] Flagging users

      Give mediators option to flag users. Have field for out of the ordinary users

   2. [SUGGESTION] Store draft of messages between chat windows

2. Support agents:

   1. Do we need more members?

      Not right now

   2. Encourage and redirect members to contribute to the Wiki.

3. Code of conduct for mediators:

   1. Improve support and mediation

   2. Action Protocol for Mediators

4. Standardize messages for mediators (@huey735 is working on it)

5. Should compensation be increased with time spent on a role?

   After a certain period it may make sense add a compensation increase for consistent contributors.

   Suggestion for possible tiers:

   • intern - works one cycle as a test

   • level 1 - fixed amount of USD (200)

   • level 2 - get compensation increase after 3-6 cycles (500 USD)

   • consider more increases after

     This timeline is only a guide and more knowledgeable contributors can skip levels if the team leaders agree to it.

6. @huey735 is to share meeting notes on a single issue on the support repository

7. Mining Fees continues to be an issue

8. Low liquidity the BSQ market forces contributors to hold BSQ.

[huey735]

Bisq Support Call 2021-04-28

Topics

Trading

• Uphold payment method

  • Discrepancy in trade duration - 1 or 4 days?

    The make/take offer screen for Uphold screens is in discrepancy with the rest in terms of the duration of trades for this payment method.

  • Full name plus username/email/phone

    Bisq's account system requires, in the creation of an Uphold payment account for the trader to specify a username, email or phone number. However the the payment app displays only the trader's full name. So it's important for Bisq to also require it in order for traders to be able to confirm the identity of their payers.

Support

• Code of conduct should be about:

  • Expectations to have from traders, mediators and arbitrators

    Examples:

    • mediator should respond in x time
    • trader should respond in x time

• Penalties should be visible before to users start trading. Either in the Terms of Services screen or before each trade.

  • Add codes to penalties
  • Add link to Penalties table on the Dispute resolution page

• Common Questions - move FAQ to wiki

• Suggestion to add an About tab to the Support View

• Add link to Support Agents calendar links on the #support channel

Development

• 1.6.3 fixes the "Seller can't confirm" bug

Compensation

Should compensation be increased with time spent on a role?

After a certain period it may make sense add a compensation increase for consistent contributors.

Suggestion for possible tiers:

• intern - works one cycle as a test

• level 1 - fixed amount of USD (200) 10 hours per week - maybe too low

• level 2 - get compensation increase after 3-6 cycles (500 USD)

• consider more increases after - 800??

  This timeline is only a guide and more knowledgeable contributors can skip levels if the team leaders agree to it.

• Think about hours per tier. How to calculate compensation:

  • rate per hour
  • fixed rate per tier

[huey735]

Bisq Support Call 2021-05-05

Topics

Development

Request
Give mediators the ability to set payout amounts by percentage (respecting minimum amounts). Currently the software provides 5 options:

• BTC buyer gets trade amount
  BTC buyer gets the trade amount plus their security deposit back. The BTC seller gets their security deposit back.

• Max payment to BTC buyer
  BTC buyer gets the trade amount, their security back plus most of the security deposit of the BTC seller. The BTC seller gets to keep 0.0005 BTC.

• BTC seller gets trade amount
  BTC seller gets the trade amount plus their security deposit back. The buyer seller gets their security deposit back.

• Max payment to BTC seller
  BTC seller gets the trade amount, their security back plus most of the security deposit of the BTC buyer. The BTC buyer gets to keep 0.0005 BTC.

• Custom
  Used for applying penalties which require other divisions of amounts.

Suggestion put slide next to penalties options to select percentages of the trade amount and to whom it should go.

Trading

Arbitration

Should the DAO get part of the trader's funds in case of arbitration?

Cap max reimbursement from peers security deposit

How to improve?

• make it clear that there is a limit on the amount to be reimbursed in case of errors by the Software or the Arbitrator/Support team and that it's in BSQ
• make it clear how repayments should be calculated (btc or usd value of btc at the time )

DAO

How to reduce supply of BSQ
How BSQ is burned

• voting - you are required to burn 2 BSQ to cast a vote
• trading fees - traders burn BSQ when using it for paying trading fees
• Burning Man - this role buys BSQ from the market and burns it. It represents the trading fees paid in BTC.
• Altcoins listing

How to increase burning BSQ

More people using BSQ for trading fees

• create more incentives to use BSQ
• use different model (subscription)
• make BSQ usage compulsory

Lack of attention to financial side

Have a role for monitoring Bisq's finances. Accountant?
Is trading fees enough to compensate contributors?

[huey735]

Bisq Support Call 20210519

Topics

Development

Suggestions for the release of coins by the BTC seller

After mediation is opened and a payout suggestion is made by the Mediator the Confirm Payment Received should be locked.

Suggestion

What about a "payment not received" button which locks the "payment received" button, to avoid accidents. Pressing "payment not received" could be reversed. Seems easy to implement.

Call it a "lock payment received" button.

Scenarios:

• Mediation is opened. BTC seller still can release the coins

Can BTC seller release btc even after trade duration is over after mediation is opened?

I think it's locked when mediation is bad for seller only.

Get answer from devs

Reafirm the need update to Tor v2

[huey735]

Bisq Support Call 20210527

Topics

Support

We considered adding more mediators. And rethink how the handling of cases is done and how we other mediators/support agents could be assigned cases in case the first mediator isn't available or loses access to the trade data.

DAO

We also touched on the need to have a better grasp of Bisq finances. Currently there is no detailed accounting taking place and it would be great if we could improve on that.

[leo816]

Support call 2021-08-25

Topics

1. Development:

   1. [SUGGESTION] Give traders the ability to make mediator proposals themselves.

2. Support agents:

   1. Do we need more members?

      Not right now. Cases are lower or similar than last cycle

   2. Better communication and response to users through keybase and the rest of platforms

3. for mediators:

   1. For all support calls have an update of all cases that are still open. And what bugs need to be solved.

   2. Read conza's suggestions: Priorities (Bigger Picture Solutions) bisq#5271 (comment)

4. Recent discussions about compensation from a previous support agent.

5. Refund Agent mentioned the double payment issue he faced this cycle.

- Topics for next call:

1. Implementing Tether
2. Mobile app ( can we add on to the one we currently have so that you can move from step 1 to step 2?

[leo816]

Support call 2021-09-01

Topics

1. Development:

   1. [SUGGESTION] How can we improve the UI?

Reach out to pedro
what are the current suggestions for improvement?
what needs to be done for new coiners to use bisq?

2. Mobile App:

   -Devin, can we have an update on the already existing app?
   -Add buttons to go from step 1 to stage 2

3. Add more payment methods (Paxful has +400)

4. Add top 5 altcoins in volume (start with Tether)

5. for mediators:

   -Have XMR users give feedback. Through Keybase and mediation dispute.
   -For all support calls have an update of all cases that are still open. And what bugs need to be solved.
   -Read conza's suggestions: Priorities (Bigger Picture Solutions) bisq#5271 (comment)

6. Current 0.25 BTC limit for fiat trades, should we increase it?

7. Monero traders activate the auto-confirm on their settings.

8. Better marketing in Developing countries where CEX are banned? (Venezuela, Nigeria, China...)

9. Bugs:
   Biggest drivers for people to leave bisq:

• Locked funds (Bitcoinj problem)
• Chat messages not going through

- Topics for next call:

1. Monero Feedback on what can be better. (communicate the auto-confirm tool)
2. Mediator's comment on the weekly disputes.
3. Get back to using the standup channel on keybase

[leo816]

Support call 2021-11-17

Topics

1. Refund Agent's dispute issue:

• Tickets not closing

2. Comptroller role:
   -(https://bisq.network/dashboard/)
   -Do we still need the comptroller role? how much of this is automated?

3. Mediations, support cases

4. Review of the new dispute resolution window

- Topics for next call:

[leo816]

Support call 2021-12-08

Topics

1. Priorities/ Short term objectives

• Mediations
• Bugs
• tracking of newly implemented payment methods
• Grin payment verification pending

2. Discussed specific user cases and how to approach them.
   -(https://bisq.network/dashboard/)
   -Do we still need the comptroller role? how much of this is automated?

3. Proposal by @pazza83 to make it easier for users to share their bisq logs:
   Make it easier for users to provide logs to mediators and support agents bisq#5906

4. Proposal to analyze the blockchain data
   Proposal to analyze blockchain data of Bisq trades to report on failed trades, arbitration instances and long-term locked funds proposals#352

- Topics for next call:

[leo816]

Support call 2021-12-22

Topics

DAO files get corrupted
chimps looked into it, currently reviewing this case

Exception error pop up. From saving the account.

1. Priorities/ Short term objectives

• Mediations
• Bugs
• tracking of newly implemented payment methods
• Grin payment verification pending

-Previous proposal that have been discussed:

3. Proposal by @pazza83 to make it easier for users to share their bisq logs:
   Make it easier for users to provide logs to mediators and support agents bisq#5906

4. Proposal to analyze the blockchain data
   Proposal to analyze blockchain data of Bisq trades to report on failed trades, arbitration instances and long-term locked funds proposals#352

- Topics for next call:
Apply changes to the payment method window

[leo816]

Support call 2022-01-12

Topics

Improvement proposal of table of penalties
https://gist.github.com/w0000000t/6d9ba235578a4fbcbf01154f491f8119

We should have a weekly bullet point list to go over + goals:

1. Priorities/ Short term objectives

• Mediations
• Bugs
• tracking of newly implemented payment methods
• Grin payment verification pending

The idea for next week is for each support team member to have a task at hand that can improve the overall experience (improving table of penalties, add information to the bisq.wiki...)

- Topics for next call:

[leo816]

Support call 2022-01-26

Topics

Going over the penalties table:
https://gist.github.com/w0000000t/6d9ba235578a4fbcbf01154f491f8119

• Be able to sign a message (show the chat log to the mediator)
• if a user does have another bank account with the same name, that should not have a penalty.
• Transition from Keybase to matrix (now its starting to be more active)

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations
• Bugs
• tracking of newly implemented payment methods
• Grin payment verification pending
• Adding Matrix notifications instead of Keybase to redirect users.
  .
  .
  .
  This goal for every week:

The idea for next week is for each support team member to have a task at hand that can improve the overall experience (improving table of penalties, add information to the bisq.wiki...)

- Topics for next call:

[pazza83]

Support call 2022-02-09

Topics

General feelings were that things are going well with support. Quiet with no major issues.

Topics discussed included:

• Trade mpcfvoz resolved by @w0000000t and @jmacxx where a users trade payout address was reused from prior trade & no funds received. This is now the third documented case of it occuring. A fix is in progress to stop this from recurring: Trade payout address was reused from prior trade & no funds received bisq#5725 (comment)

• Discussed the case of a user that risked losing 500 BSQ by using their Bisq Bitcoin wallet in a wallet application than other than Bisq. Support team confirmed warning were clear on both Bisq app (Wallet Info) and on the Wiki that using another application was not recommended and that you should NEVER send BSQ from a non BSQ wallet. @sqrrm explained to the user how they could confirm if their BSQ were recoverable.

• @pazza83 said 50% of manual payouts were being done in cases where both users had already accepted mediation. Will make a proposal to outline issue and ask for input as to how it could be addressed.

• @jmacxx mentioned an issue were a BSQ swap was unable to be taken. This is documented here: An error occurred at task: ProcessBsqSwapTxInputsMessage bisq#6033

• @w0000000t will look at creating an issue / proposal around Traders being able to filter offers by signed status, and/or making offers that are only able to be taken by signed payment methods.

• @pazza83 to investigate why a user might have been able to take a SEPA offer of over 0.01 BTC without having a signed account.

Topics for next call:

Updates on the above

[leo816]

Support call 2022-02-16

Topics

1. BUGS:

   1. [LOW FEES] Users that have paid low fees in some trades seem to be due to the fact that the user is running Bisq with the DAO disabled.

2. [Mediation Cases] Going over the penalties table:
   https://bisq.wiki/Table_of_penalties

   1. "Completely different name in a buyer payment account, a case which is missing from penalties table"

• Be able to sign a message (show the chat log to the mediator)
• If a user does have another bank account with the same name, that should not have a penalty.
• Transition from Keybase to matrix (now its starting to be more active).

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations
• Bugs
• tracking of newly implemented payment methods
• Grin payment verification pending
• Adding Matrix notifications instead of Keybase to redirect users.
  .
  .
  .
  This goal for every week:

The idea for next week is for each support team member to have a task at hand that can improve the overall experience (improving table of penalties, add information to the bisq.wiki...)

- Topics for next call:

[leo816]

Support call 2022-02-23

Topics

1. [BUGS]:

   1. Glitch on the account signing, seller appeared not to be verified when he actually was.
   2. Some penalties can't be fulfilled because the deposit is set too low.
   3. low fees bug from last week, error due to user having the DAO disabled.
   4. BSQ swap offers not takeable where maker's DAO is out of sync (because of this DAO resync popup will be re-enabled) (1. explanation is that when bsq swaps were implemented there was a bug that caused bsq users have their account age signed status published, that was solved but caused this underlying out of sync issue.)

2. [Suggestions/Observations]:

• Clearer dispute resolution summary
• Have a clearer guide on how to join the How to buy your first BTC on matrix
• Be able to sign a message (show the chat log to the mediator)
• why do you need to restart Bisq every time DAO gets out of sync, couldn't you just adjust sync "online"? need to ask chimp. w000000t will open issue
• Seems like less mediations are related to bugs now (sometimes though users didn't see mediator's suggestion, so need to do manual payout)
• Burningman should be more transparent BTC donation address owner ("Burningman") roles#80 (comment)
  issue about them holding 4 BTC from arbitration and not buying BSQ with them, only with trade fees.
  It would be a good idea to decide a protocol by which BM buys/burns BSQ, sort of rules for them to follow (All support team strongly agrees)
• some users should be able to trade directly with BM depending on situation. (reimbursements)

2. [Mediation Cases] Going over the penalties table:
   https://bisq.wiki/Table_of_penalties
   1. "Completely different name in a buyer payment account, a case which is missing from penalties table"

• If a user does have another bank account with the same name, that should not have a penalty.
• Transition from Keybase to matrix (now its starting to be more active).

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations
• Bugs
• tracking of newly implemented payment methods
• Grin payment verification pending

.
.
.
Future updates:

- Topics for next call:

[leo816]

Support call 2022-03-02

Topics

1. [BUGS]:

   2. Some account age accounts are not accurate. this is not causing any issues but worth looking into.
      restore signing and aging status of payment methods correcting name: keep same iban and swift and restore the salt from previous account, then account will have same age (as long as client's "public key" is the same, which will be the case if it's the same Bisq instance, otherwise it's not 100% which "public key" needs to be restored)
      account aging acting weird when age > 1000days

   3. how to make users join getyourfirstBTC room on matrix more easily, make the room show by default on join? (MnM covered instructions for this at https://bisq.wiki/Matrix_bisq.chat#Joining_channels )

   4. bug that makes the DAO out of sync. James will continue to look into it.

2. [Suggestions/Observations]:

• Burning man doesn't have a clear guide on how to contact users. and improve communication.
• BTC donation address owner ("Burningman") roles#80 (comment)
  Pazza will make a proposal about having burningman follow an agreed protocol to burn BSQ? referring to the 64K BSQ refund
  should bisq "hold reserves" for contributors? medium-long term plan with monthly profit?

some users should be able to trade directly with BM depending on situation. (reimbursements)
ask refundagent to give special treatment for users who have been refunded so they can sell BSQ more easily
proposal by pazza to establish a BSQ/BTC rate (equal to the original refund rate?) to honour for user being refunded by burningman, probably for the time of a cycle's duration.

• Tool Account signing transfer to new payment accounts using Salt, only available for some payment methods (SEPA)

3. [Mediation Cases]
   1. Issue with DAO not in consensus needing a restart, status is "needs to be solved, will probably be solved, for now on hold"
      external case where exchange locking funds allegedly "stolen", user claiming to having got them on Bisq, exchange saying it's a lie, pazza offered to help, probably user was actually malicious

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations
• Bugs
• discussion about new proposals
  .
  .
  .
  Future updates:

- Topics for next call:

100$ pay increase to support agents after 6 months (added by pazza in private support room)

[leo816]

Support call 2022-03-09

Topics

1. [BUGS]:

   2. Stuck trades need to be pushed to the donation address (arbitration). None for pazza 1 for Leo this last cycle.
   3. taker fee issue with the DAO disabled. should be solved with 1.8.4 unless users do not update.
   4. Alva looking into why some messages aren't going through so that we don't have that issue being transferred over to Bisq 2.
   5. issue still ongoing with not being able to take swap offers when maker is not in consensus

2. [Suggestions/Observations]:

• First trade with rubles for mediation.
• Burning Man ongoing proposals, should buy at market price? above? below? put it for discussion among DAO?
  define a wiki page to describe RA/BM operativity regarding BSQ/BTC management:
  Have a clearly defined process for how Burning man trades BTC from donation and trade fee addresses for BSQ proposals#367 (comment) Have a clearly defined process for how users with accepted DAO reimbursement requests can trade with Burning Man proposals#366
• Increase support team pay: proposal to raise compensations for contributors after 6 months' stay,
• compensation for leo's team lead role
• asking RA to attend calls
• Users who needs to be reimbursed aren't aware they should be in contact with the burning man, the refund agent should always re-direct them.
• somewhat trending topic on telegram and matrix is about setting your own node
• review UXP's summary (Bisq 2 social trading concept bisq#6011 (comment))

3. [Bisq 2.0]

• On bisq2 there are no deposits, which makes support agents/Mediators very similar. Maybe a support agent should be a bonded role? (lower bond limit required that current) they should have some skin in the game.

On bisq2:
James: I wouldn't be really happy to burn that much BSQ to get a monthly subscription. Initially there is not going to be much volume, if you burn 100 BSQ then how much volume do you need to have to get that back?
locking up a bond? if forces you to behave as a seller.

Bisq2 fee model: burned BSQ from sellers to be able to sell, each month, or N amount BSQ as a bond that can be unlocked in the future.
No foreseeable volume in getyourfirstbtc room and so in future bisq2's version of the room; also way more risks than it makes sense.

4. [Mediation Cases]
   1. All similar from last call: DAO disabled, messages not going through, late payment, user not answering...

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations
• Bugs
• discussion about new proposals
  .
  .
  .
  Future updates:

- Topics for next call:

1. should bisq "hold reserves" for contributors? medium-long term plan with monthly profit?
2. ¿Why isn't BSQ in other exchanges?

Pros:

• Will increase price and contributors will be rewarded.
• Will increase exposure and more people will be aware of Bisq. (not enough people are aware about BSQ-BTC swaps, the first ones on Bitcoin.)
• People that use BSQ to trade on Bisq would always buy it on Bisq, the only reason they would buy it on a CEX is because they are a newbie and want some equity on the Bisq Project, I think we should encourage that.

Cons:

• Bisq will be in CEXs and shitcoins casinos, which would be against everything Bisq represents.

[pazza83]

Support call 2022-03-16

My computer crashed last week so writing these from memory.

Topics

Topics discussed included:

• Should BSQ be listed on other exchanges - Support team have left comments on GitHub issue

• BSQ price falling recently in BSQ/BTC terms - what affects it? and is anything that should be actioned? It was decided that no actions were needed

• User in Telegram was concerned that having trade info deleted after x days might mean they have less evidence to supply to their bank should they be accused of something nefarious. Decided they should look to use another bank if their bank was asking lots of questions regarding transfers.

• Locked fund issues - These are rare but occasionally due to both traders be unresponsive, or problems with on unresponsive users and another user losing access to data manual payouts / pushing funds to donation address is not possible. Both mediators have a small amount of cases (~ 4) with users that have funds locked in multi-sigs with no way to access them. Discussed how funds being sent to donation address automatically might solve this. @MwithM shared concerns this would be bad in scenarios where Burning Man had been compromised. @pazza83 said they would ask @jmacxx is there could be a solution that would be feasible.

• Discussion around the proposal have a clearly defined process for how Burning man trades BTC from donation and trade fee addresses for BSQ

Topics for next call:

Updates on the above

[w0000000t]

Support call 2022-03-23

Filling in from my own notes as I noticed the notes are missing for following calls

Topics

• no special issues for pazza, proposal for burningman spending is moving forward
• proposal to implement XMR/Fiat trading pair with BTC deposit
• advertisement for Bisq on Brave browser, they want to be contacted from a @bisq.network email address, need to hear from chris for that
• ...why not allow any trading pair at this point with BTC deposit?
• setup auto-delayed payout in case both traders cannot take action (still issue with possibility of compromised BM)
• automated backup, maybe encrypted in cloud, to secure the data directory for users suffering from crashes? need to trim down backup size to strictly necessary for this
• MnM reports about connectivy issues, how to solve for users
• Using proposal's new support compensation for current cycle CR

[w0000000t]

Support call 2022-03-30

See previous entry

Topics

• nothing particular last week happened last week, someone on TG talked about an IRC group on Bisq which is not an official venue, w000000t will try and find outr more (MnM had the chance to check themselves later, and actually no bisq chat was on that server... which is incredibly hard to reach via Tor so w000000t desisted)
• Miami conference with leo and m52go will give opportunities to reach out to people and increase volume on Bisq
• how to go about sharing twitter account with m52go
• recounting last meeting issues, about BSQ price going down, MwithM talks about possible strategies, comparison with other platforms and chains
• BSQ market is picking up though, maybe because of bots
• lots of mediation tickets for pazza, one CBM trade where cash might be lost, + minor issues
• bug where failed trades banking info is not removed after N days like with completed trades
• zelle showing problems with buyers not being able to send money, maybe related to protonmail zelle addresses

[leo816]

Support call 2022-03-30

Topics

Attendants: leo, pazza, mwithm, jmacxx and w000000t

1. [BUGS]:

   2. Stuck trades need to be pushed to the donation address (arbitration). None for pazza 1 for Leo this last cycle.
   3. lots of mediation tickets for pazza, one CBM trade where cash might be lost, + minor issues.
   4. bug where failed trades banking info is not removed after N days like with completed trades
   5. issue still ongoing with not being able to take swap offers when maker is not in consensus
   6. zelle showing problems with buyers not being able to send money, maybe related to protonmail zelle addresses

2. [Suggestions/Observations]:

• BSQ price keeps going down, different ideas as to why this is happening and how could this be solved. BSQ market is picking up though, maybe because of bots. A fully working API should improve this even more.
• nothing particular last week happened, someone on TG talked about an IRC group on Bisq which is not an official venue, w000000t willtry and find outr more.
• Twitter activity.
  (Miami conference with leo and m52go will give opportunities to reach out to people and increase volume on Bisq
  how to go about sharing twitter account with m52go)

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations
• Bugs
• discussion about new proposals
  .
  .
  .
  Future updates:

- Topics for next call:

[pazza83]

Support call 2022-04-13

Topics

Topics discussed included:

• Quick update from @leo816 on the Bitcoin 2022 conference. All went well. Bisq had some good discussions with some potential new contributors. Will update us more next call.

• Locked fund issues - This was discussed at length. @jmacxx, @w0000000t and @MwithM all felt adding another key holder to the deposit transaction, or doing an automatic payout to the donation address, from the mutli-sig would create potential security issues. @jmacxx was also against automatic delayed payout in principle, it would be like taking the funds of the users, and it is debatable as a policy. It was also agreed by all that locked funds are usually the result of both traders involved neglecting their Trade outcome for a long time. The recently accepted proposal of reimbursement requests to only be valid if submitted within 3 months now puts more importance on traders doing what they can to resolve issues within 3 months. There is now no longer the expectation of DAO assistance should a user approach the support team with a historic issue. @MwithM considered that it might be possible for users to upload delayed payout tx to the cloud as a safety backup, but it was also agreed this should be the responsibility of the users to action if appropriate for themselves rather than something Bisq should implement. After long discussing on the topic, we decided to keep the responsibility with the users themselves, if they lose credentials and access to bisq data directory, then so be it, this is what comes with self custody; all the alternatives will pose the risk of a single point of failure where a corrupted individual in a trusted role, receiving/controlling the delayed payout instead of the users, could exploit their position.

• @MwithM brought up the repeated requests received on Telegram for new coin listings. New coins listing are currently on hold and have been for some time. There is potential this will be included in Bisq 2. It would be good to know what the social trading model will enable users to trade. Will it be any asset to any asset?

• Following on from the discussion about trade pairs / new coins listings @MwithM mentioned the proposal to Add Monero to fiat trading pairs using BTC as the security deposit (multi-sig). This could be used for trading any asset on Bisq with BTC as collateral.

• @MwithM discussion a possible option of using a stable coin as collateral should something like the above be implemented. @pazza83 discussed how they would like to be able to use BSQ as collateral for trading. @jmacxx liked this idea and felt it would be good to further explore it as BSQ wallet is already built into Bisq and it would be good to give BSQ holders the possibility of using their BSQ as collateral. BSQ able to be used as collateral would also incentivize contributors to hold onto it.

• @w0000000t brought up the idea of a Bisq user that suggested implementing coinjoins directly into Bisq, as a means to also be additional income for the DAO, which would act as coordinator like in wasabi and samourai and earn fees; it would still be a very complex endeavor, development-wise.

• BSQ privacy issues - Team felt the privacy issues regarding BSQ should be discussed. By voting in the DAO you are disclosing your holdings, plus all your voting history. It is good practice to use two different instances for voting and trading. There was some discussion of how contributors might be less inclined to vote in DAO cycles for privacy reasons, this is an issue when quorum is low like last cycle. There was also discussion about possible privacy implications of linking BSQ compensation to contributors GitHub profiles. It was felt Bisq is stronger when users participate in the DAO and that it would be good to consider ways participation in the DAO can be more private.

• Team discussed recent CR by opticbit. Team was in favour of this getting accepted and receiving the required votes.

• Last month less than 20% of trading fees was paid via BSQ. It would be good for this to be higher. Team discussed if privacy might be a factor in keeping this low. Last month the percentage of trade fees paid in BSQ was at it's lowest levels. @pazza83 reported big volume trades (2 BTC) still almost all use BSQ, but small trades are the largest volume overall, and their fees are usually paid with BTC.

Topics for next call:

Updates on the above including events from the conference.

[leo816]

Support call 2022-04-20

Topics

Attendants: leo, pazza, w000000t, jmacxx and mwithm

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations: Pazza says its a fairly normal week last week, this week has been much busier. MwithM has taken face2face offers which have been spams basically. The remaining have gone offline
• to do: final report for bisq accounts, 31st March for the financial year.
• Bugs: Nothing out of the ordinary.
• UI complaints. A user says bisq is too complicated and there is too much info overall. Had to do with the buyer not being able to make the payment. ACH and wire transfers work better in terms of weekly limits so we recommend them.
• W00t: nothing out of the ordinary, less work than usual. The most common issue this week has been that the"payment made" button isn't working. Waiting for m52go for allowance on the twitter.
• MwithM: the info about the BSQ swaps on the wiki are not well explained. He might start to work on it.
• Jmacxx: Quiet week, besides an issue this morning which was a false alarm, nothing major.
  .
  .

2. Suggestions/Observations:

• Marketing people: Mycelia could be a good candidate.
• Questions for dev call: What will you be able to do on Bisq2.0?
• Add more of a social aspect on bisq. More open channels for monero/stablecoins chats. Not just "get your first btc" kind of channel.
• BSQ privacy issues. Barrier of entry for people to ask for reimbursement.

Future updates:

- Topics for next call:

[leo816]

Support call 2022-04-20

Topics

Attendants: leo, pazza, w000000t, jmacxx and mwithm

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations: Issue with seller releasing btc even after buyer opened mediation (because of txid in interac acceptance); possibly happened because of block delay between mediation opening and btc release, jmacxx doesn't agree and thinks it's been a race condition between p2p network packets with mediation opening and trade being closed; leo will send an email to seller. Pazza: reporting about user publishing offers with bot-like replies in mediation, and reopening tickets; asking for them to be banned
• Pazza: mediation with a F2F seller who was placing telegram handle for direct contacts in offer details; mediation ensues, trade was for a large amount, discussing possible reduction in penalty amount.
• to do: final report for bisq accounts, 31st March for the financial year.
• Bugs: Nothing out of the ordinary.
• MwithM: the info about the BSQ swaps on the wiki are not well explained. He might start to work on it.
• Jmacxx: Quiet week.
  .

2. Suggestions/Observations:

• w000000t added section on wiki for payment started stuck button

• Debate about users taking offers with the purpose of inflitcting penalty on peer.
  discussing probable good will of above seller... they asked to meet far away from the city as well
  general agreement about 1-200USD penalty as a one time thing because of new rule.

• one-time popup to remind users to follow rules or they risk losing money, discussing contents
  brief discussion about chimp's GH comment regarding the math behind the reputation score for satoshi square; will it be a success? going from keybase/matrix experience, that might need to be seen, but it's still a first base for Bisq2
  Commenting on CD podcast Fee reimbursement for trade 1316406 #62 (from 1h49m), DAO's importance should have been stressed more
  Pazza is bullish about BSQ but defdending the rights of contributors to sell it all if they so wish.

Future updates:

- Topics for next call:

[leo816]

Support call 2022-04-20

Topics

Attendants: leo816, pazza, w000000t, jmacxx, mwithm and Refund Agent

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations:
• Pazza: issue with faster payments combined with revolut in mediation, bank blocked account, will make a proposal to address issue
• Pazza: dispute with late XMR payment vs BTC, penalized buyer for 25% as they also waited 3days to reply in mediation
  possibility to change payout in mediation when traders reach an agreement on their end; RA only sees first proposal if two are made
• Calm week for MnM and w000000t, some more social activity than usual on TG group
• Bugs: Nothing out of the ordinary.

.

2. Suggestions/Observations:

• bonding btc as well instead of bsq? how would it be technically possible?
• higher trade volume which will imply the need to check for red flags
• unbonded roles in DAO to be addressed; some bonds are still very high, amounts should be reduced across the board.
• RA: minimum dispute payout currently at 0.0005btc will be too low for losing peer trading large amounts; increasing it will allow for reduced amount of arbitrations.
• Leo: Doesn't think it will reduce significantly arbitrations but interesting idea.
  choosing best day for next devcall

Future updates:

- Topics for next call:

[leo816]

Support call 2022-06-01

Topics

Attendants: leo816, pazza, w000000t, jmacxx, mwithm

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations:
• Pazza: Bug with payment information missing has rarely happened again.
• Pazza and leo: mediation has been as usual.
• w000000t wanting to write an article about importing old data from non-working directory into a fresh data directory, as several users report not being able to start bisq out of the blue, but a fresh directory works; discussing about methods to go about this, jmacxx reports it's usually sufficient to delete tor folder instead of doing custom operations on db files. w000000t will add a short wiki article for this procedure-- not needed, jmacxx already did it Application won't progress past Step 3/4 Hidden Service published bisq#3763
• Guide on the bisq wiki on how to fix problems with Tor. w0000t will take care of it
• Bugs: Nothing out of the ordinary.

2. Suggestions/Observations:

• Add a change to ban de revolut sort code for faster payments.
  Discussing Ban Revolut Sort Code '040075' from being used for Faster Payment trades. bisq#6218 would be a safety measure to avoid trade flow interruptions. jmacxx poses issue with just "banning accounts" which might look like not being neutral on Bisq's part. Leo considers either it is banned, or penalties being given to users who cannot manage to pay. w000000t also thinks there could be placed a warning for users about the issue, also for using revolut as sepa, but leaving them responsible to get a penalty if the payment doesn't work.
  jmacxx: banning is easier than showing a notification after a check
  MwithM: we would be banning an account that we don't know will not work, and maybe will resume normal function in the future
  pazza: banning is especially useful if new users join and don't know about the proposal, and create that account that's at risk of not working

• Add statement about "every BTC is fungible at Bisq" on the wiki proposals#375

• Add statement about "every BTC is fungible at Bisq" on the wiki
  (we all agreed on this one)
  On the proposal there wasn't much involvement, and one downvote, which wasn't explained.
  Thumbs down most probably not from pazza's mediation with user complaining about "unclean" utxo and wanting to cancel

Future updates:

- Topics for next call:

[leo816]

Support call 2022-06-09

Topics

Attendants: leo816, pazza, w000000t, jmacxx, opticbit

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations:
• Pazza: Bug with payment information missing has rarely happened again. it seems like a tor issue, no need to collect more logs on that matter.
• Pazza and leo: mediation has been as usual.
• Bugs: - After jmacxx noticed an onion address, leo checked it on his mediation and all tickets with him presented a weird behaviour, with high amounts of fiat value. It seems mediation was opened and then closed instantly without any messages gone back and forth. is it a bug or was the mediation closed right as it was opened?

2. Suggestions/Observations:

• Users complaining about mediation closures not being clear enough so they don't know if they were penalized or not, maybe make suggestions clearer?

• opticbit came as a guest on the call to talk over a mediation ticket that has a difficult solution. Reporting on CBM safety measures and shortcomings/scamming openings, discussing signing and insurance required for CBM. On this particular case, funds seem to have gotten lost/tampered with. Mediators have no real way of proving if the problem came from the buyer or the seller. deposits are on hold at the moment until this clears out with better evidence.

• user asking about mediators' SLA on matrix (he was answered by pazza already and seemed like an impatient user.

Future updates:

- Topics for next call:

[leo816]

Support call 2022-06-29

Topics

Attendants: leo816, pazza, w000000t, jmacxx, mwithm

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations:

• leo & Pazza: Triple the amount of tickets, due to the tor bug.

• Pazza: The wester union issue got solved after the seller cashed the payment.
  review the interact deposit report from a user. (someone should not be able to cancel the trade because he wants to receive the payment in a certain way, they should be willing to accept both methods.)

• jmacxx: tor being problematic explains many errors also due to other services that depend on tor connection to operate

• jmacxx: comments on autodeposit, there's a claim to higher security that doesn't actually live up to itself 100%; adding autodeposit path into bisq is going to increase complication without really adding anything too useful.

2. Suggestions/Observations:

• jmacxx working on next release

• w000000t: same issues all past week mostly about tor, and tor induced hiccups
  things appear to be getting better network-wise by looking at trades history

• jmacxx: workaround by choosing only seednodes that are showing as normally responding, rather than letting bisq choose a random one, including the ones with issues; maybe we can release guide to do it manually, w000000t can probably write a wiki article to that extent

• pazza: seller received fiat payment during dispute, wanted to close the trade, buyer wasn't responding, seller didn't want to penalize the buyer also in order to possibly avoid arbitration; asking about buttons action during mediation, in case suggestion is the same as what the normal trade payout would be.

• jmacxx: normally working seednodes have reached, at the time of speaking, a high % of the total, so as of now there shouldn't be the need to alert higher levels and devs about acting on tor issues

Future updates:

- Topics for next call:

[leo816]

Support call 2022-07-20

Topics

Attendants: leo816, pazza, w000000t, jmacxx, mwithm

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations:
• leo & Pazza: Same as always, busy but mediation tickets have decreased a little compared to the last few weeks.
• People not seeing the mediation proposal, probably due to the tor issue. Pazza more present in matrix and reddit.
• mwithm: nothing new. Support cases as always.
• w000000t: nothing new. Support cases as always.

2. Suggestions/Observations:

• jmacxx: Same as usual. Working on private offers (new feature) but got hung up on the IU phase and was not happy with it.
• w000000t: Have a message sent to the user's onion address who had the revolut issue.
• Comments on the forum about chargeback risks are blown out of proportion. Neither Pazza nor Leo have seen that issue in the past.

Future updates:

- Topics for next call:

• What is the protocol for the burningman? currenntly sitting in +4 btc.

[leo816]

Support call 2022-07-27

Topics

Attendants: leo816, pazza, w000000t, jmacxx

Weekly bullet point list:

1. Priorities/ Short term objectives

• Mediations:

• jmacxx: One weirds case with a user that took a bunch of trades at the same time but it seems the user's machine freezed for 3-4 days. During that time the messages are not going through. Chimp has to look into the logs to evaluate what happened.

• pazza: did a lot of manual payouts, and several mediation suggestions being accepted didn't get published requiring manual intervention, or arbitrations not starting properly
  regarding profit reports, 0.65% of trade fees being received, chimp would aim to 0.8%, MnM suggested to reduce the BSQ discounts

• leo : mediations decreased, but similar issues to pazza; an additional user asked to become part of the support team
  pazza asked jmacxx to work into a way to have traders "resend" the payout transaction during mediation when first attempt fails, rather than having to go on with manual payout

• People not seeing the mediation proposal, probably due to the tor issue. Pazza more present in matrix and reddit.

• w000000t reporting about past week's highlights, users asking about own node, voting process, BSQ dust

2. Suggestions/Observations:

• brief chat about BSQ swaps and concurrent swaps
• twitter drama about bisq twitter account retweeting a something about samourai

Future updates:

- Topics for next call:

• What is the protocol for the burningman? currenntly sitting in +4 btc.