Add cycle 8 results post #332
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cbeams
suggested changes
Jan 17, 2020
There was a problem hiding this comment.
Looks good, @m52go. Several small changes suggested.
Related, I wonder what you think about beginning to cross-post these monthly updates to the bisq-contrib@ list. I'm concerned that not enough BSQ stakeholders are following the blog, and I know that (at least at one point) a great many of them were members of the contrib mailing list. We can discuss elsewhere, so as not to digress, but wanted to mention it here in context.
|
Perfect, thanks.
… On Jan 17, 2020, at 6:50 AM, Steve Jain ***@***.***> wrote:
@m52go commented on this pull request.
In _posts/2020-01-16-cycle-8-results.md:
> @@ -0,0 +1,53 @@
+---
+layout: post
+title: "Bisq DAO Cycle 8: Results"
+author: Steve Jain
+excerpt: "Cycle 8 of the Bisq DAO ended at block 609 186 on December 21 2019. This post covers its results. <br><br>"
+en-only: true
+---
+
+This post summarizes the results of Cycle 8 of the Bisq DAO.
+
+It comes a bit later than usual, as Cycle 8 wasn't a pretty one. During the cycle, some significant issues were made apparent in the human side of the network: a lack of management and budgeting resulted in suboptimal resource allotment needed for growth, which resulted in a ballooning BSQ supply, which resulted in an erosion of confidence in BSQ, which ultimately resulted in a sharp downturn in the BSQ price.
I tweaked it in the new commit to "a lack of management and budgeting resulted in suboptimal resource allotment needed for growth, which seemed to reflect in a lower BSQ price."
Let me know if that's closer to what you had in mind.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Really late as I intended for this post to cover management and budgeting changes that have been in development, along with more detailed issuance information, but it turns out a separate post will be made with those details next week.
Subsequent reports (Cycle 10 onward) will include more granular issuance information along with relative performance evaluation enabled by budgets and project-wide priorities.