I am sorry about the delay,  but I want to ask a couple questions.

First, did the original plot file get automatically deleted when it was done optimizing?
If not,  then it did not complete properly.

Second, did you use any memory optimizers with the delay function?
If you did not use the memory optimizer, did you just the delay function?
Memory optimizers can delete important cache or the delay function may have allowed Windows to delete something important.

Third, how many scoops did you see processed at once?
It has to be 2, 4, 8, 16, 32, 64, ..., 2048, or 4096.

Lastly, is every plot file you optimize coming out corrupted? I have had success with the windows optimizer so I want to figure out what factors I am not accounting for.  I tried to avoid making any changes to dcct's optimization algorithm.

Let me know if any of my suggestions correct your issue. I am also curious if version 1.1 from my previous post works better.

Soon will add this option and re-reading problem files

Ok, so hdd are still currently the best techonology.. if you can turn it off or on for extended periods of time, maybe energy efficiency isn't a big deal.

It's an interesting algorithm, couple thing I'm trying to figure out if someone could help me out:

How reliably can you be sure when it'll be your turn to mine?  I guess multiple people could potentially mine this block but it's just the person with the highest number wins or something like that?

Also, I mostly understand how you create the plots from reading the introduction.. how do you then verify that you pulled out the correct one and that you have rights to author the block to the rest of the network in a way that they can verify it.. seems to me like the rest of the network would almost have to do a lot of heavy duty hashing to copy the way you generated that number in the first place and arrive at the same number in order to verify it.  Must be some way around that?

This is meant as a quick start guide for those having issues with setting their system up on windows. This might be useful for those not familiar with the NXT platform...

First download this:
Wallet: https://mega.co.nz/#!ml4RTKBR!8g0-7RNjkIowgIJuhu-GHLXJRkKRxBlGh_tkbI4Sar4

Next download this:
POCMiner: https://mega.co.nz/#!b0pzHajA!ERk068l5NS6kR7zdLdTgltqyPw3Z60lwAWvgXtNQNTk

And lastly, ensure that you have the latest Java downloaded onto your PC. It seems as though incorrect java versions and correct java installation were the main causes of 50% of the problems listed in the beginning pages.

Step 1: Extract everything to the root of the drive you want to use (ie. the main driver directory). You should wind up with everything from the pocminer_v1 folder showing in the root directory, and with the Burst_1.0.0 folder in the root directory (containing the wallet program).
***you cannot extract this file to the root along with the miner, as they both contain files with the same names, and they will overwrite one or the other. Just leave the wallet in its own folder***

Step 2: Type a PASSWORD of your choosing into the passphrase text doc and save it.

Step 3: If using windows, replace the first word "java" in each of the .bat files with "C:\Windows\SysWOW64\java" and "save as" each of them as .bat files again.

Example for the run_generate .bat file:
Original; java -Xmx4000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate %*

modified: C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate %*

Step 3a: Many of the values in the original .bat files were causing issues for my computer, so I changed the -Xmx4000m (or whatever your # was) to a lower value like 1000 or 500 (ie. -Xmx1000m) and it began working. This will be entirely system dependent, and is like tweaking a normal miner's settings to find what works best.

Step 4: Double click the run_dump_address .bat file

Step 5: check the address .txt file and retrieve your your account #

Example for address is:
Found address: *whateverpassyouentered* -> *youraccount#*

Step 6: Copy your account number and paste it into the run_generate .bat file along with your plot description and how many threads you wish to use. plottostartwith=0 or 1 plottoendwith=800000 (for every 200 Gig section)

Example for this is:
C:\Windows\SysWOW64\java -Xmx1000m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner generate *youraccount#* *plot#tostartwith* *plot#toendwith* 1000 4

Step 7: Double click the run_generate .bat file and a command window should open, and you should see the computer begin to start creating plots, beginning with whatever you specified in your file.
*THIS TAKES A LONG TIME* (you can still start mining while creating plots, but don't expect your chances to be high within the first 8-10 hrs. It also took me personally about 8 hrs to plot my first 200 Gig section, so go watch a movie or get a bite to eat when this guide is done)

Step 8: Double click the run .bat and it will open briefly and then close.

Step 9: Open the Burst_1.0.0 folder and Double click the run .bat file there and let it install

Step 10: double click the Burst_Wallet internet shortcut file

Step 11: enter your password (which is the one you entered into the passphrase text file earlier). This should open your account "front end" gui.

Step 12: Go back to the root directory and double click the run_mine .bat file.

At this point you should have a total of 3 command line windows open...your computer should be generating plots in one command window, have initialized the Burst server and come to the nxt.apiServerEnforcePOST="true" line in another, and yet a thrid command window should be displaying your mining. The mining will repeatedly generate lines such as:

{"height":"2","generationSignature":"c26ef60f51aa5fc6225a481f08e51903085067a8a7d
558f94712d702f2a67bb4"}
{"height":"3","generationSignature":"a62b500a5dfc7f5e614fcf4917d83ffccd01e9c9643
d7d0e982c75043d27baff"}
Error reading file: 10818239041755946932_1_800000_500
{"height":"3","generationSignature":"a62b500a5dfc7f5e614fcf4917d83ffccd01e9c9643
d7d0e982c75043d27baff"}
{"height":"3","generationSignature":"a62b500a5dfc7f5e614fcf4917d83ffccd01e9c9643
d7d0e982c75043d27baff"}
New best: 10818239041755946932:160093
Submitting share
{"result":"deadline: 508"}

This is good, and it means YOU ARE NOW MINING. The "deadline" is a measurement of seconds until you may generate a block (provided no one else has already generated one). Yes, it is a bit of a race, but as your plot # increases, so do your chances of hitting/solving a block. I believe you can compare the size of your plot to what would be your hashrate if mining a normal scrypt coin.

Any other issues with a single step can be analyzed by typing "pause" on a seperate line in any of the .bat files, which will give you time to read and post whatever error you are experiencing.

If there is anything I left out feel free to let me know or just add to this. Donations to BURST-H2ZW-3H4D-RJBS-FCVGV
or 15977480701804512252

You can mine with ur gpu etc. But due to the whole scoop thing, if you mine with cpu/gpu it is highly inefficient. 1 in 4096 blocks a scoop becomes valid, were it 1 in 16000 then cppu's would be advantaged, were it 1 in 512 ssd's would be advantaged. You get the picture? BTW, i'm on irc, so come #burst-coin

Check out the op, diagram there, and also, blocks are 4 minutes

For each nonce/accountId combination a 256 kb chunk of data is pre-generated during the plotting process.
You can specify any ranges of nonces, just make sure they don't overlap. Otherwise same work will be done twice.
Plot files serve as a giant lookup table for further computation. Plot files can be stored on ANY device, hdds, sdds etc. Doesn't matter which device, only the available space matters.

For each block only 64 bytes (scoop) from each 256 kb chunk are really used. These 64 bytes are selected depending on block id (which is not known beforehand).

It's not possible to generate these 64 bytes on the fly. Only the entire 256 kb block can be generated, but only 64 bytes will be used. This makes the algo terribly inefficient for CPU/GPU mining.

As a result of final computation (during mining) a deadline is produced. A person with the shortest deadline will announce the next block once this deadline expires.
I hope this helped to clear things up a bit.


I did, haven't found any flaws. The algorithm looks very solid, couldn't find a way to abuse it.
I'm not a cryptography expert though.

Actually, there is no plotter to plot only 1 scoop, but it is possible. Also, there is no miner. Again, possible.