[bisq-network/compensation] For Cycle 10 (#482)

dmos62 notifications at github.com
Sat Feb 8 12:53:01 UTC 2020


## Summary

 - BSQ requested: 1470 (= 900 EUR @ 0.67 USD/BSQ and 0.91 USD/EUR)
 
 <!--
 Don't forget to make your compensation request in the actual Bisq DAO! See the following link for details:
 https://docs.bisq.network/compensation.html
 -->


## Contributions delivered

Out of the PRs below, I am requesting compensation for only the first one. The first pull request below was submitted during Cycle 9, before the new compensation rules were introduced (compensated contributions must align with priorities). @ripcurlx discussed it with me and led me to believe that seeking compensation on this cycle shouldn't be a problem, rationale being that it was submitted before compensation policy was changed.

The second DAO charts PR was submitted during Cycle 10; therefore, I'm not asking for its compensation.

### Changes to DAO charts:
- [#3890](https://github.com/bisq-network/bisq/pull/3890) Improve readability of the daily burnt BSQ chart, 1350 BSQ:
This is the first set of changes to these charts that primarily affected the daily burnt BSQ chart, but also forced the monthly issued BSQ chart's Y-axis to include zero. Changes to the daily BSQ burnt chart helped with outlier distortion and general noisiness in the data series.

- [#3910](https://github.com/bisq-network/bisq/pull/3910) Add new BSQ issued v. burnt chart, 0 BSQ:
This PR introduced a monthly chart for comparing BSQ issue against BSQ burn. According to donated use-cases in a dedicated [issue thread](https://github.com/bisq-network/bisq/issues/3753), this was the most common use for the DAO charts.

### Other:
- [#3745](https://github.com/bisq-network/bisq/pull/3745) Rename "Spread" tab to a more general "Details": 0 BSQ

This is a minute change; not asking for compensation.

## Contributions in progress

- [#3273](https://github.com/bisq-network/bisq/issues/3273) Show warning if user has a pruned Bitcoin node locally running
Working on detecting and handling when a local bitcoin node is used and configured to prune and/or not accept bloom filter queries. Discovered how the Bitcoin protocol (and bitcoinj in turn) exposes this information. Now trying to figure out how to handle it and where to put this logic.

This is my first venture into the setup and messaging parts of Bisq. It's somewhat intimidating and relaxing at the same time, because while the system isn't small or simple, I find the codebase to be well kept and easy to read.

-- 
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/compensation/issues/482
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200208/b6646796/attachment.html>


More information about the bisq-github mailing list