<blockquote>
<p><em>This is a Bisq Network proposal. Please familiarize yourself with the <a href="https://docs.bisq.network/proposals.html" rel="nofollow">submission and review process</a>.</em></p>
</blockquote>

<h3>TL;DR</h3>
<p>Currently, the <a href="https://bisq.network/blog/cycle-7-results/" rel="nofollow">End-of-cycle report</a> currently lists the amount of BSQ that was issued and an approximate amount that was burned. I propose that we expand the BSQ Issuance information to include the breakdown of where the issued BSQ was "spent".</p>
<h3>Motivation</h3>
<blockquote>
<p>I use the term "spent" in this proposal to reference issued BSQ that causes inflation.</p>
</blockquote>
<p>There are two major questions that I had when evaluating the end-of-cycle report:</p>
<ol>
<li>Where is the project spending money right now?</li>
<li>Does that spending match the priorities of the project?</li>
</ol>
<p>Currently, it is hard to find where the money is being spent so evaluating whether or not the values are inline with the project priorities is hard. Currently, an interested party has to go through every compensation report, decode the initiative that each person participated in, and group them together. Then, they can analyze the data.</p>
<p>But, I believe that having 1 person do this (and potentially updating the compensation request template to require contributors to fill in this information) will give much more transparency to the project in terms of how much Bisq is spending on each initiative.</p>
<p>With that information more accessible, it should make it easier to identify areas where more investment is needed or incentives should be changed to ensure the priorities of the project are also the priorities of the contributors. Or, where funding should be reduced because the ROI isn't there.</p>
<h3>Implementation</h3>
<p>I propose a simple broad set of categories that can always be expanded or reduced as appropriate. Each of these would be a sub-bullet under the "X BSQ Issued" line that already exists in the end-of-cycle report. The goal would be to start collecting the information so future proposals or discussions can happen backed with real data.</p>
<p>I've gone through the last few cycles and I think this list covers the major pieces. Feel free to comment if you think something should be added or removed. Or, if you have a particular use case that isn't covered in one of these sections.</p>
<ol>
<li>Software Development (devs, maintainers, etc)</li>
<li>Testing</li>
<li>Marketing</li>
<li>Translations</li>
<li>Support</li>
<li>Infrastructure (Node operators, hosting, donation address owner salary, etc)</li>
</ol>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/proposals/issues/150?email_source=notifications&email_token=AJFFTNSADXFGQBO6KYSNBI3QYJQ6NA5CNFSM4J2BFLC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IADHP5Q">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNQUIB5VZUOXZDJFAODQYJQ6NANCNFSM4J2BFLCQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNS5QGBXZ5B5G4RNEJ3QYJQ6NA5CNFSM4J2BFLC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IADHP5Q.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/proposals/issues/150?email_source=notifications\u0026email_token=AJFFTNSADXFGQBO6KYSNBI3QYJQ6NA5CNFSM4J2BFLC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IADHP5Q",
"url": "https://github.com/bisq-network/proposals/issues/150?email_source=notifications\u0026email_token=AJFFTNSADXFGQBO6KYSNBI3QYJQ6NA5CNFSM4J2BFLC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IADHP5Q",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>