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

Create more detailed offerbook metrics #22

Closed
3 of 5 tasks
freimair opened this issue Feb 24, 2020 · 1 comment
Closed
3 of 5 tasks

Create more detailed offerbook metrics #22

freimair opened this issue Feb 24, 2020 · 1 comment
Assignees
Labels
a:proposal bisq.wiki/Project_management#Proposal needs:triage bisq.wiki/Project_management#Triage to:Increase Liquidity

Comments

@freimair
Copy link
Member

freimair commented Feb 24, 2020

Description

In order to make more informed decisions in the field of growth efforts, we have to better understand our markets. @m52go came up with the idea that we need to understand why a particularly good day (in terms of trading volume) happened, so that we may learn to tweak the environment to make such a "good day" more likely. Understanding a bygone offer book seems like a good place to start. However, memorizing the whole offer book is impractical and a potential privacy leak.

Proposed solution

Thus, we agreed on 3 additional data histogram streams (for each market) to be included on https://monitor.bisq.network/ (based on this):

  1. trader distribution by offers
    This lets us make statements like
    • the top 20% of all traders produce 80% of all offers
    • 40% of traders only have 1 or 2 offers open
  2. trader distribution by volume
    • the top 20% of all traders have 90% of volume on offer
    • 60% of traders have < 0.2 BTC on offer
  3. volume per offer
    • 80% of offers cause only 10% of volume
    • there are no offers for volumes between 0.2 BTC and 1 BTC

These data also allows for statements like

  • there are offers for every volume, small to big
  • we have many traders with a good spread of volume per offer, if we loose a couple of these, the market is still healthy
  • a very small number of traders create most of the volume, if we loose a couple of these, the market might die

Implementation details

Note that these metrics are designed to give a quick idea on how the offer books looked like. The data is no simple statistical data stream providing averages, extrema or percentiles, instead, we use data binning. Here is an example graph showing "trader distribution by offers":

Screenshot from 2020-02-25 16-03-10

additionally, we know that the top trader has 12 offers.

data series index offers per trader textual description
0 1, 2 (0-2.4) traders which have less than 20% offers active than the top trader has by count
1 3, 4 (2.4-4.8) traders which have between 20% and 40% offers active then the top trader has by count
2 5, 6, 7 (4.8-7.2) traders, 40-60%
3 8, 9 (7.2-9.6) traders, 60-80%
4 10, 11, 12 (9.6-12) top 20% of traders, by offer count

The data of the 4 time stamps in the graph above are crafted for demonstration purposes:

  • T=4: there are 13 traders, all of them have 10, 11, or 12 offers. There is no "casual" trader.
  • T=3: there are 15 traders, one of them has 12 offers, all others have 1, 2 or 3 offers each.
  • T=2: there are 15 traders, every kind of trader is present, the most casual trader up to and including the most involved trader.
  • T=1: the actual measured BSQ buy market offer book of 2020-02-25 16:00 CET.

If these metrics turn out to be useful, we can think of creating the same set of data streams for trades.

Criteria for Delivery

Make the data visible as graphs on https://monitor.bisq.network/.

Tasks

Estimates

USD 750,00 as already stated

@freimair freimair changed the title [WIP] Create more detailed offerbook metrics Create more detailed offerbook metrics Feb 27, 2020
@ripcurlx ripcurlx added this to Backlog in Master Projects Board Feb 27, 2020
@cbeams cbeams moved this from Backlogged (approved w/o budget) to Proposed (not yet approved) in Master Projects Board Mar 2, 2020
@cbeams cbeams added the a:proposal bisq.wiki/Project_management#Proposal label Mar 4, 2020
@cbeams cbeams moved this from Backlog to Prioritized (approved w/ budget) in Master Projects Board Mar 4, 2020
@cbeams cbeams added the needs:triage bisq.wiki/Project_management#Triage label Mar 6, 2020
@chimp1984
Copy link

@ripcurlx @cbeams Can we close that project?

Master Projects Board automation moved this from Backlog to Done Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:proposal bisq.wiki/Project_management#Proposal needs:triage bisq.wiki/Project_management#Triage to:Increase Liquidity
Development

No branches or pull requests

4 participants