The Weekly Burst Report is a report published every Sunday meant to centralize and outline the important Burst information of the week.

Weekly key data

PoCC development statistics (public repositories)

– Files modified: 24 
– New insertions (+): 3,589 
– New deletions (-): 1,782 

Note: this solely indicates the GitHub activity on already released projects. It doesn’t reflect the work the PoCC puts into its private repositories.

Blockchain metrics

– Blockchain transaction volume: 11,881 / -59.8% 
– Total wallets: 147,560 / +0.1% 
– Burst held in Poloniex & Bittrex: 57.8% / -0.1% 

Network metrics

– Estimated Network Size (weekly average): 272 PB / +7.1% 
– Public Nodes: 461 / -31.3% 

Trading metrics

– High / Low: $0.017 / $0.010 USD 
– Trade volume / change: $4,143,130 / +120.1% 
– Market Capitalisation/ change: $22,825,079/ -9.9% 
– Weekly High vs All Time High (%): 13% / +2% 

Metrics by @Koru

Development

  • The PoC Consortium released a new software: Scavenger, a Burst miner written in Rust. Cooperating with Burst developer JohnnyDeluxe, who contributed countless ideas and optimization strategies as well as massive improvements to the Shabal code base, they created what they claim is “the fastest Burst miner to date”. During internal tests, they observed reading times “two and a half times faster than with CreepMiner”. With Scavenger, the PoC Consortium completes its line of Burst mining software that already included a pool software and the Engraver plotter. Keep in mind Scavenger is currently in Beta.

  • You might have observed a drop in the number of public nodes since the release of the latest BRS 2.2.2 wallet version. PoC Consortium developer rico666 explains: “BRS 2.2.2 is called “Stabilizator”, because these nodes are capable of delivering correctly signed blocks where BRS 2.2.1 (and everything before that) aren’t. This means, BRS 2.2.2 can pull the network/blockchain, but it also means that people who haven’t updated to 2.2.2 get blacklisted by other peers when they e.g. deliver a wrongly signed block that contains a transaction that e.g. has leading/trailing whitespace in some attached comment. The blacklisted nodes are more likely to get excluded from the net/fork, get stuck or whatever.”
    • Moral of the story: everyone, please update to BRS 2.2.2 if you have not already. Qbundle one-click upgrade is available for Windows users.
  • Reddit user u/blankey1337 created BurstAlerts, “the first alert system built for Burst”. It allows you to get an email notification whenever you send or receive Burst. Try it out on burstalerts.com.

Miscellaneous

  • Why BRS 2.2.2 went great, and how you can help Burst – check out this great post by @nixops.

Conclusion

Another week, and another Weekly Burst Report. This series have been going for nearly a year now, and I would like to take this 46th conclusion to personally thank each of you, the Burstcoinist readers who have been following the report all this time. We are only at the beginning of this crazy adventure – many more exciting news are ahead of us. I certainly am looking forward to covering them as Burst further evolves and grows.

Thank you and see you next week.

Tom Créance (@Gadrah)


Disclaimer: The Burstcoinist does not endorse and does not take responsibility for any project mentioned in a Weekly Burst Report.

Want your Burst-related project to appear in the Weekly Burst Report? Contact me and I can mention it in the next episode.


Also published on Medium.

Subscribe

Subscribe now to our newsletter

6 comments

    1. Hello,

      If you paid more attention, you would have noticed the quotation marks around “the first Burst alert system”. You would even have clicked on the link, and found that this is a direct quote from the post of u/blankey1337.

      Now, you could even have went to the bottom of the report to find this disclaimer: “The Burstcoinist does not endorse and does not take responsibility for any project mentioned in a Weekly Burst Report.”

      Now, you are right – it seems that this is not the first Burst alert system. But there were no “lies” in the above report, only one factual (and insignificant) error.

      Regards

    2. As you have chosen to use the plural form “so many lies” – you might care to mention at least a 2nd example of “a lie”. Drama much?

  1. Hello,

    I enjoy reading the Weekly Burstcoin Report and appreciate that it is so well written. Together with the newly designed Burst website, these two resources definitely put forward an impressive public face for the project and community. Thanks. I am not sure if everyone new to Burst does this, but I read each report chronologically from the beginning. Doing so presents a clear and concise presentation of burst’s long and colorful history in a context that might be missed or misunderstood if solely researched based on snips and pieces of opinions, perspectives, and comments scattered around the internet.

    I have been looking for a way to contribute something to the project that would be significant other than just hoarding coins and a few terabytes of disk mining. I have an idea that would use my editing skills, research skills, perspective as relatively new to cryptocurrency, and most importantly an abundance of time that seems like it would fulfill a need that Burst has now and will have even more so in the future related to new user adoption and limiting the demand for new user support resources across all platforms and forums.

    I would love to send you a short proposal for such a project. I would post it here, but like all ideas, it may seem good to me, but . . .

    1. Hi Adam, you can contact me anytime on Telegram (@Gadrah) or on Discord (Gadrah#7008). Looking forward to learning more about your project.

Leave a Reply

Your email address will not be published. Required fields are marked *

*
*