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


Core development statistics since last week:
– Files modified: 117
– New insertions (+): 2,989
– New deletions (-): 659
Total since the release of 1.3.6cg: 96,617 insertions (+), 139,372 deletions (-).

  • Development of the 2.0.0 version is still going strong, as you can see by looking at the numerous GitHub commits. The new wallet should be considerably more reliable and high-quality, as it is being basically rebuilt from the ground up.
    • What the PoC Consortium developers are currently doing is a lot of bugfixing and stabilization, and a config file revamp and merging. Brabantian is working on implementing unit tests, with a current coverage of 7.4% compared to the 0% we had less than two weeks ago.
    • PoC2 support is also being implemented by Quibus: in short he added support for PoC2 plotfiles that can be activated at a given block height. According to rico666, “blocks have been already mined with PoC2 on the testnet”. PoC2 is implemented to counter a potential attack allowing malicious miners to mine certain scoops with PoW and very little disk space. While this attack vector is only theoretical at this point, the PoC Consortium believes we have to fix it to give more credibility to Burst’s consensus algorithm. PoC2 will be backward compatible with the current PoC1 as long as the mining software understands both fileformats.
Sonarcloud analysis of the Burst master repository
  • A new infographic has been published, explaining how the Burst capabilities will evolve in 2018, after all the necessary hard forks:

  • In the meantime, we are noticing a strong and growing community support for the Dymaxion: the network observer shows that 74.6% of nodes run the 1.3.6cg wallet at the time of this report. This is a very encouraging signal, but we have to do even better. If you are still using 1.2.9 or older, make sure to update to the latest version. Follow this step-by-step tutorial if you want to run a full node to support the network.
  • On the non-wallet front the PoC Consortium pools are being battle-tested in real life. A few bugs were fixed but overall it is going in the right direction. “From our experience the new Go code is around 5x as fast as the lexicon pool, and it scales better on multi-CPU systems. It seems also faster than the Ninja Pool code, but we are missing hard numbers on that still”, according to rico666.


  • The How to & Tutorials section of is going to be replaced with a brand new documentation soon, probably this week. The goal is to provide a great quality source of up-to-date step-by-step tutorials that can be maintained by the community. In the meantime, current tutorials on have been updated.
  • All the online wallets are now using the 1.3.6cg version.


  • The well-known Hackernoon blog reposted an article about Burst by Andrew Scott.
  • Reddit user BurstJack has been working on Burst’s smart contracts for months now. He recently released a smart contract simulator.
  • Bombtrack released a quality video tutorial about Burst mining. Check out his channel for good Burst-related animations and videos.
  • You want to contribute for Burst but you don’t know what to do? Join the Burst Discord group and connect with the community to discuss ways to improve this fantastic cryptocurrency and to spread the word!


We are approaching the release of the 2.0.0 core version, which will formally mark the start of the intensive makeover that will take place over 2018 for Burst. Having a new wallet basically recoded from the ground up is a prerequisite to building something as ambitious as the Dymaxion on top of it. This week may have not been particularly exciting from the outside – still, great progress is happening now more than ever.

Thank you and see you next week,

Tom Créance (@Gadrah)

If I forgot something in that report, let me know and I will make sure to mention it next week.




Subscribe now to our newsletter


  1. >Dynamic fees and block size

    Is there a place with more info on the proposed rules as to how this would adjust? It seems like there’s potentially a very fine balance between the two, and that even doing something as simple as adjusting them at the same time would make it very hard to find that balance, in the same way that many people find it difficult to find the right temperature on their shower if they have a balancing valve as the hot is increasing at the same time as the cold is decreasing and visa-versa. There’s also the fact that different players might want different rules, like miners would likely, in general, want to restrict transactions more than other stakeholders.

Leave a Reply