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

Development

Core development statistics since last week:
– Files modified: 24
– New insertions (+): 983
– New deletions (-): 606

  • When the PoC Consortium released the BRS 2.0.0 core version last week, it was made clear right away that there could be a few remaining bugs due to the magnitude of the code refactoring. The developers worked hard this week to eliminate most reported issues – “we would like to thank all the early adopters who supported development by testing 2.0.0”, states PoC Consortium member rico666.
    • The BRS 2.0.1 core version is now out, and it offers better performance, stability and security compared to any release so far. This version is thought for a broader audience, but still not as backend for pools – pool operators should wait for the next version before updating.
    • The PoC Consortium confirmed that Qbundle v2.0 is going to be released this Monday. It will be based on BRS 2.0.1 and it will allow the majority of users to upgrade to the latest version with one click.
    • We can also expect a BRS 2.0.2 core version before the first fork.
  • A small bonus: the PoC Consortium released a Discord bot that automatically reports forged blocks.
  • The bigger picture – a PoC Consortium developer’s interesting insight on the future Burst Dymaxion use cases:

Websites

Other

  • Want to see an inspiring display of community engagement? Reddit user u/pskrzyni81 decided to represent Burst at the Blockchain & Cryptocurrency – BNFT Panel in Long Beach Convention CA last weekend. He handed out Burst flyers, and even ended up joining a booth! This is of course a great example to follow – we would love to see Burst being represented by community members more often in this kind of events.
  • Have you ever wished you could have a truly unique and memorable Burst Address? With adrownedcoast’s Burst Vanity Address Generator written in Python, you can generate custom Burst addresses using the 4 leading characters of the address after “BURST”. Check it out on GitHub.
  • MinerGate published a great article on Burst’s consensus protocol: Why Proof-of-Capacity could be the future of cryptocurrency.
  • There will be a new community meme competition starting from April 1st. Get ready!
  • The first episode of the Harvey Harddrive community comic series is out: the origin of it all.

Conclusion

With the release of BRS 2.0.1 (and soon Qbundle 2.0), the refactored wallet is effectively going to be the foundation of the future Burst – we will need the community to upgrade in a timely manner in order for the transition to BRS 2.2.0 (the first fork) to be as smooth as possible. As always, stay informed and proactive.

Thank you and see you next week.

Tom Créance (@Gadrah)


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


Also published on Medium.

Subscribe

Subscribe now to our newsletter

4 comments

  1. Hello,

    Since upgrading to Qbundle 2.0, the Blago Miner no longer will execute from the Burstcoin wallet. You must launch the exe manually with admin privileges to get it to function. Will this be addressed in an upcoming hotfix?

    Thanks.

  2. I mentioned BURST in my independent author’s interview on Smashwords; viewed by over 35, 000 people so far:

    “”Our massively interconnected yet fiercely independent future will favor prepared (your responsibility) and adaptive (your opportunity) minds.” – Allan R. Wallace

    That one makes me think first of this emerging indie book marketplace, then next onto the freedoms to be acquired through initial decentralization technologies like Bitcoin and Burstcoin. There is so much more coming.”

    This interview does not contain links, but even glancing recognition of Burst’s future impact is important.

    I occasionally drop BURST references elsewhere. I’m thrilled with $Burst developer’s dedicated efforts to enhance Burst’s integrity and usefulness.
    Thank you.

Leave a Reply

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

*
*