[bisq-network/roles] Growth Maintainer (#42)

[Christoph Atteneder]

## 2018.05 report
Moderation and organizing of three growth calls. This month we hold two growth meetings less as I was two weeks offline because I became a dad. General moderation of `#growth` channel (https://bisq.network/slack-invite).

Although it is a little bit of overlap with the [Analytics role](https://github.com/bisq-network/roles/issues/40), I'll provide a quick overview on the network growth and growth activities in May as suggested by @cbeams . 

The main growth activity this month was our [BTC/CAD liquidity week](https://github.com/bisq-network/growth/issues/43). As you can see in following graph the liquidity and trading activity in this market was quite stale over the last couple of months.
<img width="1250" alt="bildschirmfoto 2018-05-30 um 10 40 28" src="https://user-images.githubusercontent.com/170962/40709275-eb8a08ac-63f5-11e8-87a9-c58d4c761a0a.png">
It seems to be that already the announcement of the liquidity week beginning of May helped to spike up the interest in this market. We should check this behavior in our upcoming liquidity weeks as well. During the liquidity week we saw a great increase in number of trades (**+150%**) and in total BTC volume (**+169%**). Although the total volume traded **10,692 USD** (BTC traded in USD) and the total number of trades of **15** is low compared to other markets, it shows that this kind of marketing activity helps to bootstrap certain markets and to attract market makers.

At the moment our growth calls are mainly about liquidity weeks and updates about activities that could influence the growth of the network. As there are so many ways how this can be achieved feel free to add ideas in the [growth repository](https://github.com/bisq-network/growth) and run experiments on your own and get compensated as long as you follow the guideline in our issue template.

/cc https://github.com/bisq-network/compensation/issues/71

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/42#issuecomment-393084180
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180530/cec69828/attachment-0002.html>