Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

I've been mining BURST for a couple of months now and have written a number of articles about it already. When I began pool mining, it was a slow and confusing road to travel without a good central location for information, but I slowly pieced as much together as I could. However, the main interface for a mining pool was still quite confusing so I decided to try and find out more about it and document what I understood so others could have a go-to reference for this information.

The pool interface is far from even a barely passable UX design, but it's functional and it works (once you know what everything does!) So lets see what the typical pool UI looks like and I'll explain each of the sections where I placed numbered dots over the screenshot below...

1 - This is the pool's name, quite self-explanatory.

2 - The pool's BURST address, which is used when setting the reward recipient. This is also the wallet address that will pay you your share of the pool's earnings.

3 - Assigned miners is the count of all miners that have set the pool's BURST address as their reward recipient. Active miners are the miners that are submitting nonces to the pool and actually mining.

4 - The number of the current block being mined.

5 - The currently mined block's scoop ID. This takes a bit more of an explanation...
BURST blocks are validated using deadlines. The deadline is calculated using information from the blockchain state. Specifically, the base target (difficulty), the block height, and the previous block's generation signature are used. The scoop is calculated by hashing the generation signature and block height and performing a modulo 4096 division on the result. This gives a number between 0 and 4095. The scoop number determines which part of the plot is read to find the shortest deadline.

6 - Time remaining to mine the current block. This is calculated by taking the best currently submitted deadline and subtracting how long the current block has been mined for so far. This time will decrease dramatically in the first few seconds of a new block mining as miners submit their best deadlines.

7 - Elapsed time for mining the current block.
Adding the elapsed time and the remaining time gives the best submitted deadline. For example in the screenshot above - 45s + 18m 26s = 19m 11s, which is the best deadline as submitted by 'Busby Burst'.

8 - BURST address or account name for the best/worst/first/last miner in the pool for the current block. This is updated as the pool receives nonce submissions.

9 - General stats on the mining progress, how many miners sent nonces, how many were rejected by the pool and various details on pool balance and running time. Note that there can be more nonces submitted than the number of miners who responded since it is possible to submit multiple nonces while mining. Typically mining software will submit the best nonce it finds and will resubmit another nonce if it finds one with a better deadline e.g. if you have multiple plot files.

10 - Similar stats as in (9) but for the previous block.

11 - Pie chart showing the current block's reward distribution between all of the miners that submitted a nonce. The share is calculated based on how close each of the miner's submitted deadlines are to the best deadline. The number of slices in this chart should be equal to the number of miners that have submitted a nonce.

12 - Data for the pie chart showing account name, mining software used, the deadline and share percentage and reward.

That covers just about all of the pool UI. There are other tabs available that I've not gone into any detail on but if there is enough interest in this article, I can write similar ones describing what's going on in the other tabs too.

If you found this information useful and want to send a small donation of Burst, you can send it to me here:


Have comments or feedback on what I wrote? Please share them below! Found this useful? Consider sending me a small tip.
comments powered by Disqus
Other posts you may like...
Hi! You can search my blog here ⤵
Or browse the recent top tags...

Recent Blog Posts

How to fix Google Cloud SDK dev server error - No module named ipaddr

Adorable but totally metal - Metal Earth 3D Guardians of the Galaxy Groot model kit

Riverside Expressway Cam shut down permanently

Inserting Google DFP ads with Backbone, Underscore and jQuery

How to resolve the domain is already mapped to a project error in Google App Engine

A quick look at the Nyko Super MiniBoss wireless controllers for the SNES mini

Loading and displaying a collection from bootstrapped data in Backbone.js

Add this handy function to your Bash profile file to display the compiled JDK version for a .class file

How does PCBWay stack up as a low budget PCB fab

Resolving the Cannot reference X before supertype constructor is called compiler error in Java

Recent Galleries

BMB-012 Nanoblock T-Rex Skeleton Model assembly

Tiny Arcade revision 6 kit assembly and decal application

Atari Lynx repair - Part 5 - McWill LED screen mod installation

Atari Lynx repair - Part 4 - screen cover replacement

Atari Lynx repair - Part 2 - re-capping the motherboard

Atari Lynx repair - Part 3 - broken speaker replacement

Atari Lynx repair - Part 1 - introduction and case disassembly

Building a custom Atari Lynx game box storage shelf unit in a day

Protecting old Atari Lynx game boxes with snug fit plastic sleeves

Monument Valley 2 is released and does not disappoint

Blogs and Friends

Matt Moores Blog
Georgi's FlatPress Guide
Perplexing Permutations
The Security Sleuth
Ilia Rogatchevski
Travelling Fairy

Blog Activity

Blog Activity