Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dec 13th growth call #16

Closed
ripcurlx opened this issue Dec 13, 2017 · 6 comments
Closed

Dec 13th growth call #16

ripcurlx opened this issue Dec 13, 2017 · 6 comments
Assignees

Comments

@ripcurlx
Copy link
Contributor

  • Date: Wed Dec 13th
  • Time: 11:15a–12:15p Pacific / 8:15p–9:15p Central European
  • Place: Zoom conferencing, see Call Details below

If you want to help Bisq grow, then this is the meeting to attend!

Everyone is welcome, and there's no need to RSVP or register, but if you do plan to attend, please add a 👍 below so we have an idea how many people will be there.

Note also that you can subscribe to the Bisq DAO Google Calendar to get notifications about this call and other Bisq events. See https://bisq.network/calendar.

Agenda

You'll find the general agenda of our growth calls here: https://github.com/bisq-network/growth/blob/master/docs/growth-meeting.md

As decided on last weeks growth call we will focus all our efforts for the next two months on increasing liquidity on the Bisq network.

Before we can grow the number of overall traders on the Bisq network, we first need to make sure that we have plenty of liquidity available in major trading pairs, esp. EUR and USD.

This means that anyone who considers themselves a potential 'market maker' or 'liquidity provider' is especially welcome on this call, to help us brainstorm ways to make Bisq an attractive place to be for you. We already have a number of ideas, and are looking to get your feedback.

Note that while we're happy to have pro and semi-pro traders serve as liquidity providers, we're also looking for anyone who simply has a need to sell BTC on a regular basis, e.g. for basic cash flow purposes.

This weeks growth call is all about the learnings of our first experiment (#12)

Call details

Join from PC, Mac, Linux, iOS or Android here: https://zoom.us/j/886127835

Or join with a touch on the iPhone :
US: +16699006833,,886127835# or +16468769923,,886127835#
Or join by phone:
Dial in:
US: +1 669 900 6833 or +1 646 876 9923
Meeting-ID: 886 127 835
International numbers available: https://zoom.us/zoomconference?m=5g8IvHLeIBIjeXlPhV3XWVE4cczQAtmu

Comments welcome

Please add comments below with any questions you have or regarding any other topics you'd like to discuss on this call. See also the open issues in this repository.

Hope to see you there!

@ripcurlx
Copy link
Contributor Author

Please review experiment pipeline and last weeks metrics to be up-to-date for today’s growth meeting.

@cbeams cbeams changed the title 2017.12.13 growth call Dec 13th growth call Dec 13, 2017
@cbeams
Copy link
Member

cbeams commented Dec 13, 2017

Please also review the learnings from last week's experiment, starting with #12 (comment)

@cbeams
Copy link
Member

cbeams commented Dec 13, 2017

Note to all, @csacher won't be on the call, but he plans to watch the recording later tonight and has offered to take notes while he does and then paste a link to / transcribe them here afterward.

@cbeams
Copy link
Member

cbeams commented Dec 13, 2017

Please also review the learnings from last week's experiment, starting with #12 (comment)

Actually, I just realized when reading the agenda for these meetings at https://github.com/bisq-network/growth/blob/master/docs/growth-meeting.md, that we will go through the learnings as part of the call, so no need to try to rush through reading them!

@cbeams
Copy link
Member

cbeams commented Dec 13, 2017

Additional agenda suggestions

In addition to the standard agenda, here are a few things I'd like to discuss, if we have time:

  • Should we continue doing open invites on Twitter to these calls? I did it last week, but I didn't do it this week
  • 5-minute timeboxed discussion of whether participating in this kind of liquidity experiments is something we want to submit and vote on BSQ compensation requests for (if it goes beyond 5 mins, we'll take it to Slack or elsewhere).

@csacher
Copy link

csacher commented Dec 13, 2017

Call notes

(transcribed from the GDoc)

Date: Wed Dec 13th
Time: 11:15a–12:15p Pacific / 8:15p–9:15p Central European
Place: Zoom
Recordings: Part 1 and Part 2

Learnings from last week:
#12

Recap of last weeks experiment:
Outcome is not final (not included today), even without today: 64% increase EUR volume in the last 6 days compared to USD 16% growth. Still have to wait until the trades are settled.

Two factors that affected the result last week:
positively: the price, negatively: spam/congestion

Learnings

  • When fees are high the use case for Bisq is limited
  • In times of high fees → moving to other currencies is an option
  • We need a better communication in times of spam attacks, high fees, congestion to notify users about the current situation
  • Distribution of nodes has proved to cause difficulties (more than expected)
  • Bisq is more like a future contract (make clear that users agree on price and time in future)
  • Manfred is working on fixing some issues (eg. timeouts), until this is done, rather don’t do another experiment

Ideas

  • For people who are participating in the growth project it should be possible to submit compensation requests
  • Bisq interface should give an overview over fees (mining and bisq), gains & losses
  • Trades are also taken if the distance of price is high (2%)

Outcome

  • No push until next week, waiting for tech part to be ready
  • Prepare content for contacting traders at localbitcoins.com (tell that triangular scams are not working at Bisq) → create document (guideline) @flix is owner of the document
  • Landing Page: adding triangular scams information on bisq.network, also that trades are taken up to 2.5%
  • Next meeting on Thursday, 21st December (11:15a–12:15p Pacific / 8:15p–9:15p Central European)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants