[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[Pilotseye]

I cannot understand why it keeps giving me this error!
The plot is located in the directory D, however, does not work!

and specially note the \\ just one \ isn't enough 

[chris190]

I cannot understand why it keeps giving me this error!
The plot is located in the directory D, however, does not work!

and specially note the \\ just one \ isn't enough  

Same error with 2!

[go6ooo1212]

The path of your plots should be like this:
D:\\local path\\plots

Try it...

[chris190]

The path of your plots should be like this:
D:\\local path\\plots

Try it...

It does not work! 

[Pilotseye]

I cannot understand why it keeps giving me this error!
The plot is located in the directory D, however, does not work!

and specially note the \\ just one \ isn't enough  

Same error with 2!

did you make a symlink (mklink) from another drive to this plot folder?
cause that won't work, at least for it didn't do, so I had to point directly
to the drive where the original plot folder is located - give it a try

[cyberspacemonkey]

I like to announce a new version of my Linux miner/plotter/plot optimizer:

https://bchain.info/dcct_miner.tgz
sha256: eca303c3f2fb46a698797eab707bcc927614cfdd135c8e17114b52a6c962d641

How to use it
Download and unpack it:
wget https://bchain.info/dcct_miner.tgz
tar -xvzf dcct_miner.tgz

Then compile it:
make

of if you use 32-bit Linux:
make linux32

If you really can't compile it use the ones in "bin".

Now you have 3 tools:

The C plotfile generator

This tool creates plotfiles. In simple mode use it like this:

Code:

./plot -k <public key> -d /path/to/storage

This will fill the entire disk with a single plot file using a random start nonce, 80% of available memory and max. threads.

Or specify:

Code:

./plot -k <public key> -s 100000 -n 500G -m 10G -t 3

for starting nonce 100000, 500GB plot size, 10GB memory usage and 3 threads.

The plot optimizer utility

The new version is a LOT faster!

If you created your plots with a small stagger size, processing them takes a long time. You might miss your deadline if its found too late!
The utility optimizes your already created files making them a lot faster to read.

How to use it?

Code:

./optimize plots/1234567890_0_100000_1000

Or process your whole plot directory:

Code:

./optimize plots/*

You can limit the memory usage, for example to 1GB:

Code:

./optimize -m 1G plots/*

It will replace your plot files with optimized ones.

This does not work for incomplete plotfiles.

The miner

You want to use your plotfiles to generate coins, this is where the miner is used.

For solo mining put your passphrase in a file called "passphrases.txt". It supports only one passphrase and uses the files first line.
Avoid spaces before/after your passphrase.

Then start the miner:

Code:

./mine <node ip> [<plot dir> <plot dir> ..]

For example:

Code:

./mine 127.0.0.1 /mnt/disk1/plots /home/user/plots /mnt/usb1/plots

Each directory is read by a separate thread. If you use multiple HDD's try to use one directory per HDD, this is fastest.

The miner creates some nice output:

Code:

2872 MB read/11488 GB total/deadline 50134s (49664s left)
New block 8674, basetarget 9388869
2872 MB read/11488 GB total/deadline 21573s (21476s left)
New block 8675, basetarget 9260523
2872 MB read/11488 GB total/deadline 3040s (2823s left)
New block 8676, basetarget 9461804
2872 MB read/11488 GB total/deadline 1122s (1018s left)
New block 8677, basetarget 9502439

When seconds left approach zero, you likely found a block.

The miner also supports pool mining:
For uray's pool use:

Code:

./mine_uray.sh [<plot directory>]

For dev's pools (share based)

Code:

./mine_dev_v1.sh [<plot directory>]

or

Code:

./mine_dev_v2.sh [<plot directory>]

I keep getting this:

Code:

Could not get mining info from Node. Will retry..             
917 MB read/3671 GB total/deadline 1426805s (1426631s left)           
New block 14088, basetarget 2407011                          
21 MB read/85 GB total/deadline 711256s (711246s left)                   
Walet reported no deadline.
917 MB read/3671 GB total/deadline 117016s (116939s left)           
New block 14089, basetarget 2360711                          
317 MB read/1271 GB total/deadline 73700s (73684s left)              
Walet reported no deadline.
917 MB read/3671 GB total/deadline 73700s (73307s left)           
New block 14090, basetarget 2395043                          
0 MB read/0 GB total/no deadline                 
Walet reported no deadline.

Is this normal? If not, how to fix it? Please help!

[chris190]

Now it works, I'm a genius!
I had to change the letter from upper case to lower case, not D but d!  

and it works very well! 

[Pilotseye]

Now it works, I'm a genius!
I had to change the letter from upper case to lower case, not D but d! 

didn't make any difference for me, but hey you got it to work finally, genius 

[fanepatent]

http://burstpool.ddns.net looking for miners. Everyone is welcome.

[cyberspacemonkey]

Now it works, I'm a genius!
I had to change the letter from upper case to lower case, not D but d! 

didn't make any difference for me, but hey you got it to work finally, genius 

 

I'm finding a lot of blocks with this version wow! 

How do I add more than one directory path in the conf file? can you give me an example?

[fivebells]

I'm finding a lot of blocks with this version wow! 

How much space do you have committed to plots?  What frequency are you finding them at?

[chris190]

Now it works, I'm a genius!
I had to change the letter from upper case to lower case, not D but d!  

didn't make any difference for me, but hey you got it to work finally, genius  

 

I'm finding a lot of blocks with this version wow!  

How do I add more than one directory path in the conf file? can you give me an example?

Sure, it's very simple!

Just add the paths separated by a comma

{
    "poolUrl" : "burst-pool.cryptoport.io",
    "submissionMaxDelay" : 30,
    "submissionMaxRetry" : 3,
    "socketTimeout" : 60,
    "plots" :  
    [
       "d:\\burst-pool-miner\\plots",
        "c:\\path\\plots",
        "e:\\path\\plots"
   ]
 }

How much space do you have committed to plots?  What frequency are you finding them at?

14.35 TB

[Pilotseye]

Now it works, I'm a genius!
I had to change the letter from upper case to lower case, not D but d! 

didn't make any difference for me, but hey you got it to work finally, genius 

 

I'm finding a lot of blocks with this version wow! 

How do I add more than one directory path in the conf file? can you give me an example?

from mining.conf included in burst-miner-win64-1.0.7z

    [
       "c:\\pocminer_v1\\plots",
       "c:\\plots"
   ]

[oktay50000]

anyone can modify the code so we can use this on other pools?

[cyberspacemonkey]

Now it works, I'm a genius!
I had to change the letter from upper case to lower case, not D but d! 

didn't make any difference for me, but hey you got it to work finally, genius 

 

I'm finding a lot of blocks with this version wow! 

How do I add more than one directory path in the conf file? can you give me an example?

from mining.conf included in burst-miner-win64-1.0.7z

    [
       "c:\\pocminer_v1\\plots",
       "c:\\plots"
   ]

Is it better to use different plot directories with the same miner? or is it faster if we open a new miner per every hard rive?

[fanepatent]

Now it works, I'm a genius!
I had to change the letter from upper case to lower case, not D but d! 

didn't make any difference for me, but hey you got it to work finally, genius 

 

I'm finding a lot of blocks with this version wow! 

How do I add more than one directory path in the conf file? can you give me an example?

from mining.conf included in burst-miner-win64-1.0.7z

    [
       "c:\\pocminer_v1\\plots",
       "c:\\plots"
   ]

Is it better to use different plot directories with the same miner? or is it faster if we open a new miner per every hard rive?

I don't how this is written but I don't think it uses a separate thread for each folder/drive. So basically it would read plots faster with 3 different instances of the miner each pointed to a separate folder/drive than a single miner for all 3.
Maybe Uray will come up and confirm.
I have been using it under linux and it is pretty fast.
But, Dcct's miner seems a bit faster. Both were pointed at the same 3 x 2 Tb drives

[cyberspacemonkey]

On dcct's new miner I keep getting this:

Code:

Could not get mining info from Node. Will retry..             
917 MB read/3671 GB total/deadline 1426805s (1426631s left)           
New block 14088, basetarget 2407011                          
21 MB read/85 GB total/deadline 711256s (711246s left)                   
Walet reported no deadline.
917 MB read/3671 GB total/deadline 117016s (116939s left)           
New block 14089, basetarget 2360711                          
317 MB read/1271 GB total/deadline 73700s (73684s left)              
Walet reported no deadline.
917 MB read/3671 GB total/deadline 73700s (73307s left)           
New block 14090, basetarget 2395043                          
0 MB read/0 GB total/no deadline                 
Walet reported no deadline.

Is this normal? If not, how do I fix it? Please help!

[OmegaReaper]

http://burstpool.ddns.net looking for miners. Everyone is welcome.

Should my conf file look like this?  


{
    "poolUrl" : "127.0.0.1:8125 burstpool.ddns.net:8124",
    "submissionMaxDelay" : 30,
    "submissionMaxRetry" : 3,
    "socketTimeout" : 60,
    "plots" :
    [
       "c:\\pocminer_v1\\plots",
       "c:\\plots"
   ]
 }

*Note: If I take the localhost out I get the passphrase error in the miner. I have no passphrases in the miner. Please advise. thanks!

[fivebells]

The plot optimizer utility

The new version is a LOT faster!

What makes this faster?  The read and write loops look exactly the same, except for getting rid of pread, which I assume is for compatibility rather than speed.

[fivebells]

Is it better to use different plot directories with the same miner? or is it faster if we open a new miner per every hard rive?

I get better results with separate miners, but you have to use a C-based miner because multiple java-based miners can hose the memory.