Open cbeams opened 4 years ago
This is the first cycle report on this newly-created role issue. I've been playing this role since its inception in January along with the other new team lead roles, but we only just now got the actual role issues in place. In any case, cycle reports here should be a good opportunity to sum up what's happened over the cycle with the support team, what's needed and what to look forward to.
So far as I can tell, the coverage calendar is working out well and we've got pretty decent shift coverage. For a while there it seemed like we may have actually overdone it and brought on too many support agents, but with the recent spate of issues, I'm not sure that's the case. If you have any feedback on how we're doing here, please speak up.
This cycle was the first with @bisq-network/l1-support-agents @Bayernatoor, @huey735 and @MwithM, all of whom played the support intern role between Cycles 10 and 11. Welcome all!
@bisquser has stepped down as a mediator, and @wiz and @Bisq-knight have recently bonded into the role, meaning that the @bisq-network/mediators team now consists of @leo816, @wiz and @Bisq-knight. Thanks @bisquser for your efforts, and welcome to the new team members!
If you haven't already seen it, please review @wiz's proposal for how much each support role will be compensated at https://github.com/bisq-network/proposals/issues/200.
One of the projects started in the wake of the Q1 update was to establish support issue case tracking (https://github.com/bisq-network/projects/issues/5). Unfortunately, this effort got stalled and hasn't been picked back up to date. Without it, we don't have any real metrics around how many support cases we're dealing with or how well we're dealing with them. I have simply been unable to push the ball forward on this due to time constraints, and that probably won't change any time soon. If someone on the team is interested in taking over this project, please speak up.
Another change we made out of the Q1 update was to create a private bisq.support subteam where agents and devs could work together in private, sharing case information with each other on an as-needed basis. This seems to have been a positive addition and the subteam is pretty lively with activity. This is in addition, of course, to the existing, public #support
channel in the main bisq Keybase team, which also seems to be thriving with activity servicing user requests.
One of the projects we did complete out of the Q1 update was to establish a critical bugs board and process (https://github.com/bisq-network/projects/issues/16). However, without the support case tracking process in place, I'm not sure how much value the support team is getting out of / putting into the critical bugs board. The idea has been to reference critical bugs (and other issues) in our support case tracking GitHub issues, so that we have some kind of running count of how many support cases are related to each bug, helping us to prioritize which ones to fix first. In any case, if you're a support agent, please consider adding comments to critical bug issues when you encounter them with users, whether or not we have the support case tracking process in place. See https://bisq.wiki/Critical_Bugs for more details.
When trades fail for technical reasons like transactions failing to broadcast, we have a policy of reimbursing traders for their lost Bisq trading fees and Bitcoin mining fees. For quite a while, @KanoczTomas played the informal role of handling these reimbursement requests, but has stepped down and has now handed the work off to @leo816. I will create a new "Lost fee reimbursement agent" role very shortly, and will assign it to @leo816. This will not be a bonded role. Indeed, it requires the agent to put up the reimbursement funds out of pocket and then be reimbursed by the DAO in BSQ. Fortunately, these amounts are never very large.
@RefundAgent is now in the process of stepping down from this role, and it is of urgent importance that we find someone to take their place. @m52go has recently written up documentation on the Refund Agent role and its relationship to the Burning Man / Donation Address Holder role. See https://github.com/bisq-network/admin/issues/70#issuecomment-607890856 for details.
@wiz and @cbeams will be meeting soon to further define the Refund Agent / Arbitration role. If you are interested in owning this role, please let one of us know.
Yet another project out of the Q1 update was rolling out the new Bisq wiki, principally for the reason of creating a kind of knowledge base for Bisq support. There has been quite a bit of activity on the wiki since, and many articles have been written. We still haven't officially rolled it out, but I think we're getting close to a place where we should do that. The main outstanding items are putting together a suitable main page that guides the users to the different major kinds of content. If someone is interested in doing this, or more generally owning the project to roll out the wiki, please speak up.
Also, @kemccall has come on board to fill the Wiki Editor role. This role is still being defined, but please keep an eye out for anything Ken has to say, and feel free to reach out to him. The main idea of the Wiki Editor role is to have someone responsible for the overall structure and standards on the wiki. Think about how Wikipedia Editors work, and you'll get the idea. Ken is not a subject matter expert on Bisq (yet), but he is a seasoned professional technical writer and editor, so should be able to add a lot of value in helping us keep our content clean and consistent.
I may have missed something above. If there's an important topic I haven't covered here, i.e. something outstanding in support that needs to be addressed, please speak up. Thanks everyone for your efforts.
/cc bisq-network/compensation#533
/cc bisq-network/compensation#573
I would like to formally apply for this role. Given that @cbeams is stepping down from this role, and as he previously announced that I would taken over this role on several meetings, I believe that my experience on the support team makes me a good candidate for this role. my current roles are:
@leo816 wrote:
I would like to formally apply for this role.
Thanks, Leo. All, I think the process of handing this role off should include defining it more clearly. When we created this role, I took it on and started several initiatives to improve support. These included:
I've just updated and in some cases closed each of those projects to reflect their current state. The one outstanding project is rolling out the Bisq wiki. Would the new support team lead take over and own this project? What other regular duties would the support team lead carry out?
Note that outside of the owning the projects mentioned above, the only duty I've been carrying out as the Support Team Lead is reviewing support team members' compensation requests. Nominally, I've been responsible for the support budget as well, but outside of compensation request reviews, the only budget-related action I've taken there is approving the recent proposal to normalize mediator and support agent compensation rates.
Note also that the Donation Address Holder (burning man) and Arbitrator (refund agent) roles fall under the Support Team, so the support team lead needs to be on point for making sure things are going well with these critical roles, checking the accounting for their reports, etc.
I'd like to hear from members of the @bisq-network/support team what they would want to see from a team lead going forward. I have spent very little time on the role outside of the projects and duties mentioned above, and I wouldn't want to hand the role off in its current state assuming that it's the way things should be.
And I'd like to open up the candidacy for this role to anyone who thinks they would be a good fit for it. It's true that Leo and I have talked about him owning the role a number of times, but it's actually not a decision that I want to make on my own; if you're interested in owning this role, please speak up and make a case why you'd be a good fit, what you'd want to get done, how you'd expect to be compensated, etc.
The best way to do this would be to create a proposal issue titled "@yourusername to assume Support Team Lead role" and to include in the description of that issue why you're a good fit, etc. We can then vote on any such issues in the next cycle.
In any case, the first task for whoever owns the role should be to update the Support Team Lead wiki documentation to reflect what owning the role will look like going forward.
Almost all of the criteria for delivery for the wiki is complete, and in the current state is already very helpful. In a few weeks I think it could be considered ready for delivery. Another point I'd like to comment is that the calendar is that I've not been using the support calendar very much, and I wonder if it's really necessary to have it now.
I've added these two duties that I think the Support Team Lead should have:
Manage new internship proposals and evaluate their performance once the period is over.
Review and supervise the "on duty" schedule. (making sure everyone is available when needed)
Per the approval of bisq-network/proposals#230, I have un-assigned myself as owner of this role, and assigned @leo816 as the new owner. @leo816, please go ahead with cycle reports here starting in the current cycle (14). Cheers!
- Created a draft protocol for Mediators to use
Where?
- Created a draft protocol for Mediators to use
Where?
On the keybase bisq.support subteam keybase://chat/bisq.support#general/2535
When support tickets are closed and then reopened I find users can receive my messages but can't answer back on most cases. This is an issue when funds get stuck on the multisig and I need to get both party's private keys or we are trying to get hold of a user who may have received the wrong payout.
I edited some parts about the private key on the Manual Payout that were missing on the Bisq.wiki
It's not possible to write messages for tickets that have been closed.
To reopen a ticket the shortcut ctrl+u has to be used which reopens the ticket but it doesn't reload the ticket view. If the user has no other tickets they need to restart their application after doing ctrl+u to get a field to enter messages.
@leo816 FYI https://github.com/bisq-network/bisq/pull/4446 implemented lots of improvements.
N of Issues cycle 15: 85 38 Wiz 24 B Knight 23 Leo816
1) 20% Both parties agreed to cancel
2) 30% trader provided the wrong information
3) 50% User took longer to confirm/answer
N of Issues cycle 16: 111 44 Wiz 38 B knight 29 Leo816
1) 25% Both parties agreed to cancel
2) 20% trader provided the wrong information
3) 40% User took longer to confirm/answer
4) 15% buyer could not make the payment
N of Issues cycle 17: 128 52 Wiz 36 B knight 40 Leo816
1) 20% Stuck in Stage 2
2) 25% Banking issues, buyer couldn't make the payment
3) 55% BTC seller took longer to confirm/answer
Summary: the btc seller took longer to respond/ confirm the payment for
N of Issues cycle 18: 89 31 Huey 21 B Knight 37 Leo816
1) 25% Stuck in Stage 2
2) 15% Banking issues (zelle and revolut)
3) 60% User behaviour- took longer to confirm/ answer (disagreements)
N of Issues cycle 19: 184 36 Huey 75 B Knight 73 Leo816 Pending report Wiz
1) 40% Stuck in Stage 2
2) 10% Banking issues
3) 40% User took longer to confirm/ answer
4) 10% Failed Trades
Overall trend: Even though the number of issues have increased over 100% since the previous cycle we should also take into account that the volume of trades in Euros for example has also experience a significant increase. the main issue I see is that BTC sellers can still not confirm a payment after 10 days and then release without incurring in a penalty. This is less common because users usually end up coming back and confirming but it can worsen the user experience when it does happen. The biggest issue as to why people are opening disputes has to do with not being able to confirm that they've received the payment
the main issue I see is that BTC sellers can still not confirm a payment after 10 days and then release without incurring in a penalty. How many such cases have happened in the last cycles? Is it only on specifics markets, is it same users?
If its too high we could consider a soft-ban list. mediators publish onions of such users and traders can use that for local in-app bans.
Started Support Weekly calls The idea behind this is to improve communication between Support Agents, Mediators, Refund Agent and developers. The Support team needs to be aware all at once of the ongoing changes and report any bugs or problem that users may be facing. Since Bisq is decentralized and anonymous the communication level was very low. Hopefully this slowly helps solve this and enables us to raise issues faster. https://github.com/bisq-network/roles/issues/83#issuecomment-777782707
Included Castorj as support intern He has been doing a great job so far, we encourage him to continue learning and helping bisq. I've received 2 other proposals to join the support team, currently evaluating and we will likely have one more support intern next cycle.
Constantly in conversations with @jmacxx and @huey735 on how to improve mediation (notifications, managing complicated cases, XMR verification, penalties, mediator action protocol, flagging users) Mention to @pazza83 who has been extremely helpful with penalty unification and giving overall feedback to improve the user experience.
Overall keeping track of the performance of the support team If a mediator can't manage the increase in number on cases and users complain there has to be a substitution as it has happened in the past. All depends on the individual and their different circumstances, we are looking for the best people who have enough time to contribute and work for bisq.
Merged this support case issue request by huey735 https://github.com/bisq-network/support/pull/561
Looking into the future With the introduction of the API and the phone app development being not so far into the future, I have concerns of scalability when the mass adoption arrives. We need to have "on call" mediators that are inactive but that can reactivate their key as soon as mediation levels go over a certain amount. Right now this would mean @wiz and @Bisq-knight (If they are willing) would reactivate their mediation keys as soon as mediation doubles from the current levels. Since Arbitration levels are significantly lower, there would have to be a serious increase for there to be several back up Refund Agents, but it would also be safer to have a back up refund agent in case transaction levels spike.
Analysis of Mediation Cases If I continue the mediation progression report from 3 months ago this would mean:
Per @wiz's request, I've added @huey735 as an assignee to this role issue, indicating that he is the secondary owner, with @leo816 remaining the primary owner.
Included @wallclockbuilder as support intern He has been doing a great job so far. I've received 2 other proposals to join the support team, currently evaluating and we will likely have one more support intern next cycle since one support agent has also left this cycle.
Constantly in conversations with @jmacxx and @huey735 on how to improve mediation
https://github.com/bisq-network/bisq/pull/5207
Overall keeping track of the performance of the support team An important issue this cycle was related with a support team member deciding to leave because he felt that he spent more hours working than his compensation reflected. After this, I added a short description on the compensation part inside the role of Support Agent on https://bisq.wiki/Support_Agent#Compensation We continue to discuss what progression of increase should be given to these fixed rates.
Merged several pull requests by huey735 https://github.com/bisq-network/support/pull/885
Analysis of Mediation Cases If I continue the mediation progression report from 3 months ago this would mean:
@wallclockbuilder rejected as support agent He stopped answering after his first intern period
@BtcContributor joined as support intern He has been working great so far, joined his first weekly support call this week and giving valuable feedback.
@pazza83 joined as mediator Been working well as mediator, both @huey735 and myself have been trying to give some guidance when adopting the role
Constantly in conversations with @jmacxx , @huey735 , @pazza83 and @MwithM on how to improve user experience
https://github.com/bisq-network/bisq/pull/5207
Overall keeping track of the performance of the support team I'm currently reviewing different candidates to join the support team, I'm not hiring any new people until we have a clear image of exactly how much we can spend each cycle and where our budget limit should be. Working on that with other team members right now.
Analysis of Mediation Cases (Report button is unabled and Huey's report is missing so unclear what the mediation cases this cycle have been but from what I've seen I would say 100 mediation cases this cylce is a good estimate)
If I continue the mediation progression report from 3 months ago this would mean:
@huey735 stepping down as mediator
Began Dev Calls Along with @jmacxx our aim is to improve communication with the dev team and have a better roadmap for bisq.
@BtcContributor joined as support agent He has been working great so far, joined his first weekly support call this week and giving valuable feedback.
Constantly in conversations with @jmacxx , @huey735 , @pazza83 and @MwithM on how to improve user experience
Overall keeping track of the performance of the support team I'm currently reviewing different candidates to join the support team, I'm not hiring any new people until we have a clear image of exactly how much we can spend each cycle and where our budget limit should be. This has improved with some draft PNL that have been made in these previous cycles Working on that with other team members right now.
Analysis of Mediation Cases We have had 107 mediation cases this cylce.
If I continue the mediation progression report, it would look like this:
No reports were made of the last calls but all took place. The main topics of discussion were:
Main points from this cycle:
@huey735 hasn't answered back @huey735 has been missing for over 2 months, I hope he is fine and we would love to have him back as he has been a great help for bisq.
Continued with Dev Calls Along with @jmacxx our aim is to improve communication with the dev team and have a better roadmap for bisq. reports: https://github.com/bisq-network/projects/issues/60#issuecomment-944501972
@BtcContributor continued as support agent Has been having around 4-5 cases a week, mainly focused on keybase but was encouraged to also keep an eye on the forum. his reported suggestion as improvements to the wiki: https://shrib.com/#Bronson9V9N8R4
@pazza83 taking over the comptroller role We think is key to have a clear picture of Bisq's overall balance as it may not be clear from cycle to cycle. Pazza took the initiative to create the comptroller role and this was the first official cycle: https://github.com/bisq-network/roles/issues/111#issuecomment-950284730
Constantly in conversations with @jmacxx and @pazza83 on how to improve user experience
Both of them are working really well with bisq, always giving feedback and available for calls to help sort out bugs or problems users might have.
Overall keeping track of the performance of the support team weekly update on all members of the support team, tracking their workload and receiving applicants for support interns.
Analysis of Mediation Cases We have had 139 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The main topics of discussion were:
Main points from this cycle:
Continued with Dev Calls Along with @jmacxx our aim is to improve communication with the dev team and have a better roadmap for bisq. reports: https://github.com/bisq-network/projects/issues/60#issuecomment-964032003
@BtcContributor continued as support agent Has been having around 6-7 cases a week, mainly focused on keybase but also keeping an eye on the forum.
The comptroller role Pazza took the initiative to create the comptroller role and this was the second cycle: https://github.com/bisq-network/roles/issues/111#issuecomment-968339246 Since automatic reporting finally was implemented, (https://bisq.network/dashboard/) our next question is whether we still need this role or not. It seems there were some discrepancies in the results but its most likely due to the difference in taking months or cycles as starting point. I believe we should still keep it but feel free to comment this report if you think otherwise.
Constantly in conversations with @jmacxx and @pazza83 on how to improve user experience
Both of them are working really well with bisq, always giving feedback and available for calls to help sort out bugs or problems users might have.
Overall keeping track of the performance of the support team Weekly update on all members of the support team, tracking their workload and receiving applicants for support interns. I had one applicant this cycle, seeing the profit bisq is making two cycles in a row, I will consider adding one more support intern if the applicant is good enough.
Analysis of Mediation Cases We have had 104 mediation cases this cycle. (don't have all the information but this is an estimate given the info that I have from my side.
If I continue the mediation progression report, it would look like this:
The main topics of discussion were:
Main points from this cycle:
Continued with Dev Calls Our aim is to improve communication with the dev team and have a better roadmap for bisq. reports: https://github.com/bisq-network/projects/issues/60#issuecomment-997016890
@w0000000t Joined as support intern He was already helping on the support channel on Keybase even before becoming a support intern. He has been extremely helpful and providing great insight to users. Very active in general and has brought a lot of value just in his first cycle. Was accepted to now become a support agent for the coming cycles.
Updated the table of dispute resolution Now as mediators, we have more options for specific cases and can add the percentage of penalty which makes the process easier and harder to make mistakes.
Constantly in conversations with @jmacxx and @pazza83 on how to improve user experience
As I mentioned last cycle, both of them are working really well with bisq, always giving feedback and available for calls to help sort out bugs or problems users might have. At the beginning of this cycle we had a weird issue with a user and @jmacxx was ready as always to have a call and sort it out.
Overall keeping track of the performance of the support team Weekly update on all members of the support team, tracking their workload and receiving applicants for support interns.
Applicants to join the Support Team I had two more applicants this cycle, I've rejected both. As of right now the calendar is fully covered and the level of knowledge of those applicants wasn't high enough. Also current support agents are not overwhelmed with work, if that changes we will reconsider adding more people to the team
[WIP] Analysis of Mediation Cases We have had 104 mediation cases this cycle. (don't have all the information but this is an estimate given the info that I have from my side.
If I continue the mediation progression report, it would look like this:
Overall I'm really happy with the support team we've built. Communication is getting better, we are having less bugs and have more users. Everyone in the team is working really well and users tend to be very happy with the way they are treated and how weird situations are handled.
The main topics of discussion were:
Main points from this cycle:
Continued with Dev Calls Our aim is to improve communication with the dev team and have a better roadmap for bisq. reports: https://github.com/bisq-network/projects/issues/60#issuecomment-1036613336
@w0000000t accepted as support agent He has continued to be extremely helpful and providing great insight to users. Very active in general and has brought a lot of value just in his second cycle. He will be taken into consideration to become a mediator (if he accepts) when needed.
Updated the table of penalties @MwithM @w0000000t @pazza83 and @jmacxx all contributed in the decision making regarding penalties and judging different situations. Most common scenarios were put in the table of penalties making everything simpler for the mediator and for the users https://bisq.wiki/Table_of_penalties Other situations have to be judged by the mediator and the arbitrator upon evidence from both parties.
Constantly in conversations with @jmacxx and @pazza83 @MwithM and @w0000000t on how to improve user experience
As I mentioned last cycle for pazza and james, all of them are always giving feedback and available for calls to help sort out bugs or problems users might have.
Overall keeping track of the performance of the support team Weekly update on all members of the support team, tracking their workload and receiving applicants for support interns.
Applicants to join the Support Team I haven't had new applicants reach out this cycle. With bisq2.0 we will have to grow our team to meet the rise in demand for support agents.
[WIP] Analysis of Mediation Cases We have had 147 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
This cycle hasn't been too busy, no requests to join the team and calls have been productive. From the support calls we've made several proposals, some of which I will link below. (We've been noticing that some proposals get stuck there and there is no activity afterwards. perhaps we should make clear that the writer of the proposal should incentivize action or some kind of deadline before it gets taken down):
Continued with the Weekly Support calls https://github.com/bisq-network/support/issues/916#issuecomment-1074530447
The main topics of discussion were:
Main points from this cycle:
Increase Compensation for the Support Team As linked above, I created this proposal because Bisq needs to reward consistency and people that are invested in making the project work.
Continued with Dev Calls Our aim is to improve communication within the dev team and have a better roadmap for bisq. This includes constant updates with the work being done on Bisq 2.0 reports: https://github.com/bisq-network/projects/issues/60#issuecomment-1057878984
Constantly in conversations with @jmacxx and @pazza83 @MwithM and @w0000000t on how to improve user experience
Happy with the commitment and work from the team
Overall keeping track of the performance of the support team Weekly update on all members of the support team, tracking their workload and receiving applicants for support interns. As mentioned above, no applicants this cycle. Im not actively looking for interns but this cycle might start putting it more out there.
Analysis of Mediation Cases We have had 136 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
This cycle has been much busier than last one. Our main focus on the latest topics have been trade penalties and making sure they are fair while some users try to take advantage of newbies. We are doing out best to not incentivize this kind of use.
The main topics of discussion were:
Main points from this cycle:
Continued with Dev Calls Our aim is to improve communication within the dev team and have a better roadmap for bisq. The main focus on last calls have been towards the work being done on Bisq 2.0 https://github.com/bisq-network/projects/issues/60#issuecomment-1113160914
Constantly in conversations with @jmacxx and @pazza83 @MwithM and @w0000000t on how to improve user experience
Happy with the commitment and work from the team. The support team is currently the best team on bisq.
Overall keeping track of the performance of the support team Weekly update on all members of the support team, tracking their workload and receiving applicants for support interns. As mentioned above, no applicants this cycle. Im not actively looking for interns but this cycle might start putting it more out there. No new applicants this cycle.
Analysis of Mediation Cases We have had 136 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has been stable, a little bit lower than the previous. Main discussion had to with bonded roles. Some roles require to deposit large bonds that contributors may not have at their disposal and that even if they did, that itself doesn't guarantee a complete alignment with bisq's interests. Ultimately it's a trusted role. We are working to finds ways to improve this to eliminate any risks.
The main topics of discussion were:
Main points from this cycle:
Continued with Dev Calls (no report was made this cycle as things discussed on the call followed over to a group on matrix) Our aim is to improve communication within the dev team and have a better roadmap for bisq. The main focus on last calls have been towards Bonded roles and the work being done on Bisq 2.0 https://github.com/bisq-network/projects/issues/60#issuecomment-1113160914
API The API work has been stopped for Bisq 1 and the main focus for ghubstan is now to find people to use the current API. He is promoting all the upgrades that have been made up until now in order for users to give back feedback. Also with bisq 2.0 so close in the horizon, it doesn't make sense to keep spending resources on something that will be obsolete soon.
Constantly in conversations with @jmacxx and @pazza83 @MwithM and @w0000000t on how to improve user experience
Refund Agent was also able to join a few of the calls and suggested to have a lower minimum payout on mediation disputes to avoid a percentage of them ending up in arbitration. https://github.com/bisq-network/support/issues/916#issuecomment-1124027604
Overall keeping track of the performance of the support team Weekly update on all members of the support team, tracking their workload and receiving applicants for support interns. We are not looking to expand the team and had no applicants this cycle. Happy with the commitment and work from the team. The support team is the best team on bisq. Logs are constantly sent to jmacxx who is quick to respond and give feedback on the error messages.
Analysis of Mediation Cases We have had 193 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle have increased particularly this last week due to the tor connection issue, as mentioned in other reports, the tor issue is unrelated to bisq and we are still waiting for an update form tor. For now the only solution for traders is to shut down and re-start the app. Even though the tor bug ocurred as we were making our monthly reports and therefore it won't show in detail the increase in mediation tickets, on cycle 38 we will be able to see how big the increase was.
The main topics of discussion were:
Main points from this cycle:
Continued with Dev Calls Last call was an update from chimp on bisq 2.0 and a screen sharing of what it will look like. Progress has been great and the prototype looks amazing. There has also been some bug fixing from Devin on the mobile app because some users were complaining. https://github.com/bisq-network/projects/issues/60#issuecomment-1166225667
API Ghubstan has been working on some bots, also has in mind the sub-projects requested by chimp, he will take them on as soon as he is done with what he is doing now. Now working on some java API bots. https://github.com/bisq-network/bisq-api-reference
Constantly in conversations with @jmacxx and @pazza83 @MwithM and @w0000000t on how to improve user experience
Refund Agent was also able to join a one of the calls and has been in constant comunication with mediators to discuss specific tickets and how to evaluate them.
Overall keeping track of the performance of the support team Weekly update on all members of the support team, tracking their workload and receiving applicants for support interns. Happy with the commitment and work from the team. Pazza is keeping up with mediations and also providing great input with the P/L summary. Jmacxx is more active than ever on the support channel and has made an effort to be more active during this spike in customer support, also logs are constantly sent to him who is quick to respond and give feedback on the error messages. w0000t is probably the most active contributor, he is constantly available and always showing initiative to do more. mwithm has also been active and providing good value as always. The support team is the best team on bisq.
Analysis of Mediation Cases We have had 192 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle have decreased with regards to last cycle as the tor issue is now under control and volume of trades was seen reduced over the last few days. Even though the mediation cases number appears to have increased, the number is higher due to the fact that from my side there were a lot of unfinished cases that were settled this cycle Even though the tor bug occurred as we were making our monthly reports and therefore it won't show in detail the increase in mediation tickets, on cycle 38 we will be able to see how big the increase was.
The main topics of discussion were:
Main points from this cycle:
Continued with Dev Calls Just one dev call this cycle, mainly an update from chimp about bisq 2.0 so there was no report https://github.com/bisq-network/projects/issues/60#issuecomment-1166225667
API no update from the API this cycle.
Overall keeping track of the performance of the support team This cycle I've received several requests to join the team, I've rejected several as there is no urgent need to grow the team, nevertheless, an old contributor reached out to join the team again and he will likely be joining soon after we coordinate the schedule. My job consists of a weekly update on all members of the support team, tracking their workload and receiving applicants for support interns. Happy with the commitment and work from the team. this cycle there has been less work and less bugs but everyone is working well
Analysis of Mediation Cases We have had 201 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has increased with regards to the previous one and although the tor issue is now under control we are still experiencing more than average manual payouts that need to be done by mediators. 223 tickets is a record level which hopefully means there overall volume of bisq has increased.
Main points from this cycle:
Continued with Dev Calls Just an initial call and then they were also postponed in August https://github.com/bisq-network/projects/issues/60#issuecomment-1166225667
API no update from the API this cycle.
Overall keeping track of the performance of the support team This cycle there was less volume of users reaching out or requests to join the team, nevertheless the inflow of messages is constant, bugs, comments, issues... etc. Although this cycle was more relaxed there was still many important issues discussed which can't be disclosed at this time.
Analysis of Mediation Cases We have had 201 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has decreased with regards to the previous one and we are no longer experiencing such a high number of manual payouts that need to be done by mediators. 223 tickets was a record level which now has dropped to 159. Growth calls were postponed but planing on retaking the weekly calls as scheduled.
Main points from this cycle:
Continued with Dev Calls We just had one call this cycle. https://github.com/bisq-network/projects/issues/60#issuecomment-1166225667
API no update from the API this cycle. This will have to wait for the Bisq 2.0 development.
Overall keeping track of the performance of the support team This cycle there was less volume of users reaching out or requests to join the team, nevertheless the inflow of messages is constant, bugs, comments, issues... etc. Although this cycle was more relaxed there was still many important issues discussed which can't be disclosed at this time.
Analysis of Mediation Cases We have had 159 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has decreased with regards to the previous one and we are no longer experiencing such a high number of manual payouts that need to be done by mediators. 159 tickets from last cycle now has dropped to 143.
Main points from this cycle:
Continued with Dev Calls We just had one call this cycle. No more updates since Bisq 2.0 is not yet ready for deployment, on the call we talked about https://github.com/bisq-network/projects/issues/60#issuecomment-1166225667
Overall keeping track of the performance of the support team This cycle support messages have increased, the inflow of messages is constant, bugs, comments, issues... etc. Although this cycle was more relaxed in terms of debates there was still many important topics regarding the new trade protocol https://github.com/bisq-network/proposals/issues/390
Analysis of Mediation Cases We have had 143 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has increased significantly with regards to the previous one. Manual payouts still have to be made on a regular basis. 143 tickets from last cycle now increased to 280.
Main points from this cycle:
Dev Calls No dev call this cycle. No more updates since Bisq 2.0 is not yet ready for deployment.
Growth Calls
On growth calls this cycle we discussed ideas regarding Bitcoin 2023 https://github.com/bisq-network/growth/issues/273
Also plans to boost liquidity for the upcoming bisq 2.0 upgrade https://github.com/bisq-network/growth/issues/274
Overall keeping track of the performance of the support team As seen by the overall mediation tickets, support messages via different platforms have also increased significantly, the inflow of messages is constant, bugs, comments, issues... etc. We've had requests to join the team that we are currently evaluating and we had a user present a growth proposal via call. Waiting for the update of the new trade protocol and for bisq 2.0 updates.
Analysis of Mediation Cases We have had 280 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has remained high after last cycle's increase. Manual payouts still have to be made on a regular basis. 280 tickets from last cycle whereas this cycle they were 273.
Main points from this cycle:
Dev Calls No dev call this cycle. No more updates since Bisq 2.0 is not yet ready for deployment.
Growth Calls On growth calls this cycle we discussed ideas regarding Bitcoin 2023 More pending these following weeks
Also plans to boost liquidity for the upcoming bisq 2.0 upgrade might be postponed, it seems we might not reach the target but either way it will be a great way of pushing volume on to bisq. https://github.com/bisq-network/growth/issues/274
Overall keeping track of the performance of the support team As seen by the overall mediation tickets, support messages via different platforms have also increased significantly, the inflow of messages is constant, bugs, comments, issues... etc. We had a new support intern called ckdc that we are currently evaluating and is working quite well so far.
Analysis of Mediation Cases We have had 273 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has decreased from last cycle's ATH. 229 mediation tickets this cycle whereas on the previous one we reached a maximum of 280. Number of manual payouts have increased.
Main points from this cycle:
Dev Calls Bisq 2.0 is not yet ready for deployment so no updates this cycle
Growth Calls Growth calls this cycle were with the Bitcoin2023 team to work with the details of how we will be taking part. More pending these following weeks
Also plans to boost liquidity is now taking more traction as we get closer to the 20th of March, it seems we might not reach the target with bisq2.0 deplyed but either way it will be a great way of pushing volume on to bisq. https://github.com/bisq-network/growth/issues/274
Overall keeping track of the performance of the support team The support intern ckdc has been rejected to continue as support agent and we have taken 3 new support interns that are working well, those are: @darawhelan @luis3672 @suddenwhipvapor they are approved to continue as support agents on the coming cycle.
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 273 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of cases this cycle has decreased from last cycle's ATH. 184 mediation tickets this cycle whereas on the previous one we reached a maximum of 280. Number of manual payouts have increased.
Main points from this cycle:
Market Day It's getting closer to the 20th and we will do a livestream as well to make more noise about what will be happening https://github.com/bisq-network/growth/issues/274
Dev Calls Bisq 2.0 is not yet ready for deployment so no updates this cycle
Growth Calls Growth calls this cycle were with the Bitcoin2023 team to work with the details of how we will be taking part. More pending these following weeks. Everything is pretty much ready for the conference
Overall keeping track of the performance of the support team The new support agents are working well and all of their compensation request's have been accepted (@darawhelan @luis3672 @suddenwhipvapor ) with the exception of luis3672 who will be making their first CR next cycle. There are other applicants but under review as there is no hurry to add more people to the team.
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 183 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has remained stable after the decrease from last cycle's. 101 mediation tickets on my end, waiting for Pazza's but the total amount should be quite far from this two cycles ago when we reached a maximum of 280. Number of manual payouts have remained stable with 3 on my end and - from Pazza.
Main points from this cycle:
Market Day https://github.com/bisq-network/growth/issues/274 Market day was a success 350 trades in total which means there were only three days in our history where we saw more trades than 20th of March 2023. Special thanks to @flix1 who made a huge effort in pushing this initiative paying market makers on new critical markets https://github.com/bisq-network/growth/issues/274#issuecomment-1478602371 not only that but he was the one that created the initial issue back in 2018 https://github.com/bisq-network/growth/issues/67 Livestream recorded: https://www.youtube.com/watch?v=u75tqjkvxU8 also a quick mention to other people that helped: @apemithrandir @ripcurlx @verdeja
Dev Calls Bisq 2.0 is not yet ready for deployment so no updates this cycle
Growth Calls Growth calls this cycle were regarding the Market day and with the Bitcoin2023 team to keep nailing down the details of how we will be taking part. Everything is almost ready. Starting a weekly growth call with @Jayboi23, @RadishXN and @verdeja who will help to kickstart the growth team.
Overall keeping track of the performance of the support team The new support agents are working well: @darawhelan @luis3672 @suddenwhipvapor and @luis3672 will be making their first CR this cycle.
There are other applicants but under review as there is no need to add more people to the team. I plan to step away from my support agent role in the near future to leave new contributors take on more responsibilities.
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 183 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has increased from last cycle's. 102 closed mediation tickets on my end, but +45 open, on pazza's side he has also experienced an increase with 128 and 27 open that means a total 303 which is a reasonable increase, mainly due to the network congestion which has left some users with their trades on the mempool until today. Number of manual payouts have remained stable with 2 on my end and 1 from Pazza.
Main points from this cycle:
Dev Calls We had a follow up call on Bisq 2.0 and it's looking better each day. Hopefully we have a final release soon.
Growth Calls Growth calls this cycle were regarding the Market day and with the Bitcoin2023 team to keep nailing down the details of how we will be taking part. Everything is almost ready.
Overall keeping track of the performance of the support team The new support agents are working well: @darawhelan @luis3672 @suddenwhipvapor and @luis3672 . User strayorigin is starting off with the support role, he has shown a great commitment through the cycles without even being part of the team. Welcome!
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 303 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has decreased from last cycle's. 95 closed mediation tickets on my end, but +20 open, on pazza's side he has also experienced a decreased with 89 and 18 open that means a total 184 which is a reasonable decrease and great news. Number of manual payouts have remained stable with 1 on my end and 2 from Pazza.
Main points from this cycle:
Dev Calls We had a follow up call on Bisq 2.0 and it's looking better each day. Hopefully we have a final release soon.
Growth Calls Helping contributors who are keen in helping to be constant.
Overall keeping track of the performance of the support team The new support agents are working well: @darawhelan @luis3672 @suddenwhipvapor and @luis3672 . This will be strayorigin's first cycle as a full support agent, he has shown a great commitment through the cycles without even being part of the team. Welcome!
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 148 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has increased from last cycle's. 102 closed mediation tickets on my end, but +28 open, on pazza's side he has also experienced an increase with 97 and 19 open that means a total 199 which is a mild increase from las cycle. The number of manual payouts have increased drastically from 3 last cycle to a total of +15 this cycle, particularly towards the end of the cycle
Main points from this cycle:
Dev Calls We had a follow up call on Bisq 2.0 and it's looking better each day. Hopefully we have a final release soon.
Growth Calls Growing bisq markets in countries like nigeria with contributors who are keen in being constant when publishing offers.
Overall keeping track of the performance of the support team The Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor and @luis3672 . Strayorigin's has been showing a great level of understanding and effort when providing support through the channels.
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 199 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has increased from last cycle's. 110 closed mediation tickets on my end, but +60 open, on pazza's side he has also experienced an increase with 112 and 24 open that means a total 222 which is a mild increase from las cycle. The number of manual payouts has slightly increased from last cycle to a total of +32 this cycle, particularly towards the end of the cycle.
One call with regards to different Bitcoin companies that have reached out since Miami to study potential synergies.
Main points from this cycle:
Dev Calls We had a follow up call on Bisq 2.0 and it's looking better each day.
Growth Calls Growing bisq markets in countries like nigeria with contributors who are keen in being constant when publishing offers.
Overall keeping track of the performance of the support team The Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor and @luis3672. Strayorigin's has been showing a great level of understanding and effort when providing support through the channels. He has worked on a tutorial about the SPV resync
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 222 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
One call with regards to different Bitcoin companies that have reached out since Miami to study potential synergies.
Main points from this cycle:
Dev Calls We had a follow up call on Bisq 2.0 and we are closer than ever
Growth Calls Growing bisq markets in Nigeria
Overall keeping track of the performance of the support team The Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 222 mediation cases this cycle.
If I continue the mediation progression report, it would look like this:
Cycle 52 The number of mediation tickets this cycle has increased from last cycle's. 163 closed mediation tickets on my end, but 24 open, on pazza's side he has also experienced an increase with 139 and 11 open that means a total 302 which is a considerable increase from las cycle. The number of manual payouts has slightly increased from last cycle to a total of +12 this cycle.
Cycle 53 The number of mediation tickets this cycle has decreased from previous cycle's. 39 closed mediation tickets on my end, but 30 open, on pazza's side he has also experienced an decreased with 116 and 36 open that means a total 155 which is a considerable decrease from las cycle. The number of manual payouts has slightly increased from last cycle to a total of +14 this cycle.
The high decrease in mediation cases on Cycle 53 is mainly due to late reporting on cycle 52 which made the number much higher on the previous cycle and much lower on this one. On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. If we add the open cases we have (66 tickets), the total number would go up. No bugs out of the ordinary, the number of manual payouts we have had to performed have continued increase through time. I've had more than usual trades with no payment information, I would say about 4 or 5 this cycle.
Main points from this cycle:
Dev Calls We have had follow up call on Bisq 2.0. Main tasks include coordinating and managing different roles that will be crucial for the deployment.
Growth Calls Growing bisq markets in Nigeria. @Jaiboy is in charge on that front and creating a following on Nostr although it's been difficult for him to grow and find guidance. I'm doing my best to instruct him but it requires time.
Overall keeping track of the performance of the support team The Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 155 mediation cases this cycle and 302 on the previous one. I explain on the third paragraph of this report why the discrepancy and even though it looks like a considerable decrease, it's more stable than it looks.
If I continue the mediation progression report, it would look like this:
Cycle 54 The number of mediation tickets this cycle has increased from last cycle's. 153 closed mediation tickets on my end, but 22 open, on pazza's side he has also experienced an increase with 117 and 14 open that means a total 270 which is a considerable increase from las cycle. The number of manual payouts has slightly increased from last cycle to a total of +12 this cycle.
The high increase in mediation cases on Cycle 53 is mainly due to late reporting on cycle 52 which made the number much lower on the previous one. On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. The total number of open tickets has decreased (34 tickets), the total number would go up. No bugs out of the ordinary, the number of manual payouts we have had to performed have continued increase through time. I've had only one trade with no payment information, I would say about 4 or 5 this cycle.
We have found a web editor for bisq 2 that can replace the previous role holder. Demo seems on point and we are closer than ever for the released.
Main points from this cycle:
Dev Calls We have had follow up call on Bisq 2.0. Main tasks include coordinating and managing different roles that will be crucial for the deployment.
Growth Calls Growing bisq markets in Nigeria. @Jaiboy is in charge on that front and creating a following on Nostr although it's been difficult for him to grow and find guidance. I'm doing my best to instruct him but it requires time.
Overall keeping track of the performance of the support team The Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin
Calls have been done through matrix as usual. Improving the bisq 2.0 wiki.
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand.
Analysis of Mediation Cases We have had 270 mediation cases this cycle and 155 on the previous one.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has decreased from last cycle's. 110 closed mediation tickets on my end, and 16 open, on pazza's side he has also experienced an increase with 94 and 17 open which means a total 204 which is a considerable increase from las cycle's 270. The number of manual payouts has slightly increased from last cycle to a total of +30 this cycle.
On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. The total number of open tickets has remained constant (33 tickets). Out of the ordinary this cycle there have been two variables, 1) the number of manual payouts we have had to performed has increased to an all time high (+30) and 2) The amount of trades with the bug of having no payment information for either the buyer or the seller is also at an all time high, I would say about 10-15 on this cycle from my side only.
First demo of the web site for bisq 2.0 - https://github.com/bisq-network/bisq2/issues/1033#issuecomment-1910657508
No record of the calls were taken this cycle We've had weekly calls as usual getting updates from all of the support team + some growth calls discussing different topics.
Main points from this cycle:
Dev Calls Coordinating roles for bisq 2.0 - We will have a call this week to discuss this.
Growth Calls Growth Team lead will be appointed this role from now on. He will be in charge of that team from now on.
Overall keeping track of the performance of the support team The Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin @MwithM The team has been handling all kinds of users and continue to be extremely helpful and respectful. Calls have been done through matrix as usual. Improving the bisq 2.0 wiki.
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand, no need to add extra members for now.
Analysis of Mediation Cases We have had 204 mediation cases this cycle and 270 on the previous one.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has increased from last cycle's. 124 closed mediation tickets on my end, and 24 open, on pazza's side he has also experienced an increase with 119 and 18 open which means a total 243 which is a considerable increase from las cycle's 204. The number of manual payouts has slightly increased from last cycle to a total of +22 this cycle.
On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. The total number of open tickets has remained constant (33 tickets). Out of the ordinary this cycle there have been two variables, 1) the number of manual payouts we have had to performed has decreased but remained constant (+22) and 2) The amount of trades with the bug of having no payment information for either the buyer or the seller also remains at an all time high, I would say about 10 on this cycle from my side only.
First demo of the web site for bisq 2.0 - https://github.com/bisq-network/bisq2/issues/1033#issuecomment-1910657508
No record of the calls were taken this cycle This cycle we had a coordinaton call with regards to bisq 2.0 and the different roles that have been taken up. We've had weekly calls as usual getting updates from all of the support team + some growth calls discussing different topics.
Main points from this cycle:
Dev Calls Coordinating roles for bisq 2.0 - We will have a call this week to discuss this.
Growth Calls Growth team is now fully operational, Solomon has taken the lead and I trust that he will do a great job.
Overall keeping track of the performance of the support team The Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin @MwithM The team has been handling all kinds of users and continue to be extremely helpful and respectful. We had some discussions about an interaction on telegram were users were being unpolite and an improvement from jayboi with regards to his answers on Nostr Calls have been done through matrix as usual.
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand, no need to add extra members for now.
Analysis of Mediation Cases We have had 234 mediation cases this cycle and 204 on the previous one.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has increased from last cycle's. 150 closed mediation tickets on my end, and 40 open, on pazza's side he has also experienced an increase with 144 and 21 open which means a total 294 closed and +350 if we count the open tickets which is a considerable increase from las cycle's 243. The number of manual payouts has slightly increased from last cycle to a total of +33 this cycle (11 more than last cycle).
On average we are doing around 150 mediation tickets a month each which means closing 5 tickets a day. The total number of open tickets has also increased a little on my end (40 tickets).
Out of the ordinary this cycle there have been two variables, 1) the number of manual payouts we have had to performed has increased again to 33 2) The amount of trades with the bug of having no payment information for either the buyer or the seller remains at an all time high, I have had 15 on this cycle from my side only.
Bisq 2.0 Market Day April 3rd - https://github.com/bisq-network/growth/issues/295
No record of the calls were taken this cycle This cycle we had an update call with regards to bisq 2.0.
We've had the support weekly calls as usual getting updates from all of the support team + some growth calls discussions regarding the market day and the liquidity issue.
Main points from this cycle:
Dev Calls Coordinating roles for bisq 2.0, bugs, improvements, potential issues and market making.
Growth Calls Due to the decentralized nature, growth team is experiencing issues when trying to get things done.
Overall keeping track of the performance of the support team Not much change from last cycle, the Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin @MwithM The team has been handling all kinds of users and continue to be extremely helpful and respectful.
Calls have been done through matrix as usual.
Regarding support, we are at an all time high with mediation, bisq 2.0 has also required quite a lot of work. So I predict that we will shortly need new team members for the support team to keep up with the demand. So far support messages via different platforms have remained constant about bugs, comments, issues... etc.
Analysis of Mediation Cases We have had 294 mediation cases this cycle and 234 on the previous one.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has decreased from last cycle's. 85 closed mediation tickets on my end, and 65 open, on pazza's side he has also experienced a significant decrease with 110 and 25 open which means a total 195 closed and +300 if we count the open tickets which is a considerable decrease from las cycle's 290. The number of manual payouts has slightly increased from last cycle to a total of +35 this cycle (2 more than last cycle).
On average we are doing around 145 mediation tickets a month each which means closing around 5 tickets a day. The total number of open tickets has also increased a little on my end (60 tickets).
Out of the ordinary this cycle we've just had the number of manual payouts that has increased again to 35.
Bisq 2.0 Market Day - https://github.com/bisq-network/growth/issues/295 Was mentioned on the last report but given the kickstart, now there are consistently offers and still not huge amounts but slowly building up.
Bisq wiki update I have been creating more educational content regarding bisq 2.0 Specially heading up to the market day.
No record of the calls were taken this cycle This cycle we had a few updated calls with regards to bisq 2.0.
We've had the support weekly calls as usual getting updates from all of the support team + some growth calls discussions regarding the market day perfromance and the liquidity issue on bisq 2.
Main points from this cycle:
Dev Calls No dev call this cycle. Coordinating roles for bisq 2.0, bugs, improvements, potential issues and market making.
Growth Calls Currently speaking to different organizers to maybe sponsor some events but currently undecided on any one conference. Due to the decentralized nature, growth team is experiencing issues when trying to get things done.
Overall keeping track of the performance of the support team Not much change from last cycle, the Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin @MwithM The team has been handling all kinds of users and continue to be extremely helpful and respectful.
Calls have been done through matrix as usual.
Regarding support, we have experienced a decrease from last cycle's all time high mediation tickets, bisq 2.0 has also required quite a lot of work. So I predict that we will shortly need new team members for the support team to keep up with the demand. So far support messages via different platforms have remained constant about bugs, comments, issues... etc.
Analysis of Mediation Cases We have had 294 mediation cases this cycle and 234 on the previous one.
If I continue the mediation progression report, it would look like this:
The number of mediation tickets this cycle has remained steady from last cycle's. 108 closed mediation tickets on my end, and 35 open, on pazza's side he has also experienced a similar amount with 106 and 27 open which means a total 214 closed and almost 300 if we count the open tickets which is almost the same as las cycle's
The number of manual payouts has slightly increased from last cycle to a total of 29 this cycle
On average we are doing around 145 mediation tickets a month each which means closing around 5 tickets a day. This cycle is a little below average although we are still missing the report from the new mediator which should increase that number
Out of the ordinary this cycle we've had impersonators through all matrix channels that have created similar user ids and have sent private messages to people asking for their private key. We have made an effort responding as many messages as we could to get people to avoid these scammers but there is only so much we can do. In most cases they are not even in the bisq channels using those user names, so we can't kick them out of the rooms.
luis3672 stepping in as mediator for bisq 1 He is already a mediator for bisq 2 and has now also taken the role of mediator for bisq 1. I will stop contributing in bisq very shortly so I am trying to do the transition as smooth as possible.
No record of the calls were taken this cycle
We've had the support weekly calls as usual getting updates from all of the support team + some growth calls discussions regarding the market day perfromance and the liquidity issue on bisq 2.
Main points from this cycle:
Dev Calls No dev call this cycle. Coordinating roles for bisq 2.0, bugs, improvements, potential issues and market making.
Overall keeping track of the performance of the support team Not much change from last cycle, the Support agents are working well: @darawhelan @luis3672 @suddenwhipvapor @luis3672 and @Strayorigin @MwithM The team has been handling all kinds of users and continue to be extremely helpful and respectful.
Calls have been done through matrix as usual.
Regarding support, we have experienced an increase in demand from the matrix channels and mediation tickets are very similar from last cycle's.
Analysis of Mediation Cases We have had 214 mediation cases this cycle,
If I continue the mediation progression report, it would look like this:
Docs: https://bisq.wiki/Support_Team_Lead Teams: @bisq-network/support, @bisq-network/team-leads