[bisq-network/roles] Comptroller (Issue #111)

Chris Beams notifications at github.com
Sat Oct 23 13:57:01 CEST 2021


> > * I like the simple breakdown of numbers you've started with here. I think it would be worth having a single rolled up, USD denominated revenue number that sums up the BSQ and BTC revenue numbers above, but this is a minor point.
> 
> I am not sure what you mean with this? Can you expand?

I just mean that when a reader sees the two line items below:

|  August 2021 | USD | BTC | BSQ |
| ------------- | ------------- | ------------- | ------------- |
| BSQ trade revenue fees  | $8,562 | 0.18759448 BTC | **546.81 BSQ** |
| BTC trade revenue fees  | $35,096 | **0.76895773 BTC** | N/A |

They must mentally add up the items to get a "rolled up revenue number", making it hard to answer the basic question "how much did we take in this month?".

I think it's good to see a single, top-line revenue number, denominated in USD, but it can have the calculated BTC and BSQ equivalents right next to it, just for reference.

Basically, it's this top-line revenue number that I would want to track over time. Is that number going up or down, cycle-over-cycle?

Being able to break the top-line revenue number down into BTC and BSQ parts is of course important information too, but I wouldn't want to miss making the top line number explicit and easily trackable.




> > * It would be good to see the actual BSQ number in the BSQ trade revenue fees line item. Same with contributor costs. Since these are actually denominated in BSQ, it would be good to see a third column "BSQ" that lists these values. Perhaps you could **bold** the values for each row that represent the original denomination.
> 
> Included, and updated.

Thanks for adding the BSQ column. Instead of putting 'N/A' in the "BTC trade fee revenues" row, however, I'd suggest putting the calculated equivalent BSQ number there too. Just like we do in the other rows with calculated BTC and USD values.

-- 
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/111#issuecomment-950141585
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211023/45c279e2/attachment.htm>


More information about the bisq-github mailing list