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

[uray]

New update 1.0.2
https://mega.co.nz/#!C0hEmRKD!pf70p7VucqfYyUpqOXZgWTOYu2r_vs4d8g5yRnfrQ5Y
Please update before block 2700

Changes:
New difficulty adjustment starting on 2700
New ui

Mirror added : https://s3-ap-southeast-1.amazonaws.com/burst-mirror/burst_1.0.2.zip

[alibabacool]

the difficulty continues to increase ...

look at the chart:

https://www.dropbox.com/s/2ibjd5nq7px36uw/burst.png

but nobody has a clue how to relate the difficulty of this type of mining to the classic scrypt or x11?
I mean in scrypt already 1 or 2 of difficulty is useless in only undermine ...
here what is the threshold beyond which no longer deserves to undermine?

Tell me, please, how you watch the difficulty?

Just open web wallet and click on NRS link

Thank you!

[unsoindovo]

ok...
wallet 1.0.2 with blockchain downloaded again all OK.
all my coins are save :-)

just a question.

i need to know how to configure this setup.
i have the first pc for generating plots with 100% CPU usage.
i want to use my second pc for mining.
How i can modify the comand line of run_mine.bat to use remote "plots" folder?
how i can pass //192.168.0.10/c$/burst/miner/plots to miner parameter?

thank you very much!!!!

[JhoniOne]

who knows what it is ?

Code:

{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b
0b52ae827b9c1ab6b95071a357f20d6fbae4c963f9782b26"}
[INFO] [08/18/2014 00:54:50.677] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [1] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [2] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [3] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.679] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [4] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [5] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [6] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [7] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [8] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [9] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [10] dead letters encountered, no more dead letters
 will be logged. This logging can be turned off or adjusted with configuration s
ettings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b

[unsoindovo]

who knows what it is ?

Code:

{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b
0b52ae827b9c1ab6b95071a357f20d6fbae4c963f9782b26"}
[INFO] [08/18/2014 00:54:50.677] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [1] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [2] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [3] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.679] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [4] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [5] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [6] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [7] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [8] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [9] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [10] dead letters encountered, no more dead letters
 will be logged. This logging can be turned off or adjusted with configuration s
ettings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b

i don't know but i have same erro "akka" :-)

dev can you answer us?

thank you!

[callmejack]

ok...
wallet 1.0.2 with blockchain downloaded again all OK.
all my coins are save :-)

just a question.

i need to know how to configure this setup.
i have the first pc for generating plots with 100% CPU usage.
i want to use my second pc for mining.
How i can modify the comand line of run_mine.bat to use remote "plots" folder?
how i can pass //192.168.0.10/c$/burst/miner/plots to miner parameter?

thank you very much!!!!

the simplest way may be to map a network folder and start the bat from there.
as far as i know the startlocation has to have plots folder.
maybe you can also use the mklink command to create a link pointing toyou plots folder on the other machine.
http://technet.microsoft.com/en-us/library/cc753194.aspx

i run all on a cluster filesystem to generate the plots with many nodes and this works fine.
but this is linux based.

[unsoindovo]

ok...
wallet 1.0.2 with blockchain downloaded again all OK.
all my coins are save :-)

just a question.

i need to know how to configure this setup.
i have the first pc for generating plots with 100% CPU usage.
i want to use my second pc for mining.
How i can modify the comand line of run_mine.bat to use remote "plots" folder?
how i can pass //192.168.0.10/c$/burst/miner/plots to miner parameter?

thank you very much!!!!

the simplest way may be to map a network folder and start the bat from there.
as far as i know the startlocation has to have plots folder.
maybe you can also use the mklink command to create a link pointing toyou plots folder on the other machine.
http://technet.microsoft.com/en-us/library/cc753194.aspx

i run all on a cluster filesystem to generate the plots with many nodes and this works fine.
but this is linux based.

on MSDN i read "Applies To: Windows 8, Windows Server 2008, Windows Server 2012, Windows Vista"
i have windows 7 but i can try it ;-)

thank you for now!

[callmejack]

who knows what it is ?

Code:

{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b
0b52ae827b9c1ab6b95071a357f20d6fbae4c963f9782b26"}
[INFO] [08/18/2014 00:54:50.677] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [1] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [2] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.678] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [3] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.679] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [4] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [5] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.681] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [6] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [7] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [8] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [9] dead letters encountered. This logging can be t
urned off or adjusted with configuration settings 'akka.log-dead-letters' and 'a
kka.log-dead-letters-during-shutdown'.
[INFO] [08/18/2014 00:54:50.682] [default-akka.actor.default-dispatcher-5] [akka
://default/user/$a/$d/$a] Message [pocminer.ScoopReader$msgReadScoops] from Acto
r[akka://default/user/$a/$d#838902195] to Actor[akka://default/user/$a/$d/$a#-10
30186561] was not delivered. [10] dead letters encountered, no more dead letters
 will be logged. This logging can be turned off or adjusted with configuration s
ettings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
{"baseTarget":"88890105","height":"2278","generationSignature":"ca7473b02358e33b

i don't know but i have same erro "akka" :-)

dev can you answer us?

thank you!

i get this also if the io load is high. i run with many 2gb files so its not such essential for me.
i think its a timeout setting in java to receive data.
check if your hdd has bad sectors.

[burstcoin]

The akka warning happens if you are still reading plot files when the client sees a new block. It's just warning that still ongoing stuff is being killed off, which is intended behaviour, since there's no point still mining on an old block.

[omgbossis21]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

[JhoniOne]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

read above about "mklink"

[hvidgaard]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

Since the miner only reads from a single directory, you either have to run an instance for every folder with plots (usually 1 per drive), or link them all into one folder.

[callmejack]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

for the mining itself it may still be better to run several instances cause the plotfiles are read sequentially as i know.
so if you have a hash with a timeout of 15 seconds first seen after 100 seconds it may not be as useful as if its seen earlier ;-)
also if you are limited by ntfs to work with 2tb volumes the simplest solution is to run a miner instance for each volume instead of linking the plotfiles to a centralized location.

[unsoindovo]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

[CryptoSurfer]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

Only important for generating plotfiles.

[Sagre]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

CPU Power only Matters when generating Plots.


Another question by me:

The instance to generate plots with #myAdress #startingPlot #plotsToCreate #??? #Threads
That does the #??? Number stand for? And is it a problem, if some of my plots got different #???  numbers?

[hvidgaard]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

CPU Power only Matters when generating Plots.


Another question by me:

The instance to generate plots with #myAdress #startingPlot #plotsToCreate #??? #Threads
That does the #??? Number stand for? And is it a problem, if some of my plots got different #???  numbers?

It's stagnation, really just how many plots it will generate before flushing to the disk. Higher number uses more RAM during plot generation, personally I use 1024, so I can get away with using 1gb RAM for the generation.

[Sagre]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

CPU Power only Matters when generating Plots.


Another question by me:

The instance to generate plots with #myAdress #startingPlot #plotsToCreate #??? #Threads
That does the #??? Number stand for? And is it a problem, if some of my plots got different #???  numbers?

It's stagnation, really just how many plots it will generate before flushing to the disk. Higher number uses more RAM during plot generation, personally I use 1024, so I can get away with using 1gb RAM for the generation.

Perfect, thank you

[Zig-Zag]

WTS 330k Burst
PM me with an (reasonable) offer

[callmejack]

Still curious am I supposed to run one instance for plots on each drive?  As in if I plots on c and e this run a run_mine.bat file from each drive?

read above about "mklink"

But for mining it is important CPU Power?
Or CPU Power is really important just for generate plots?

to generate the plots you require more cpu resources than for mining.
parsing the plotfiles also produces cpu load.
in most cases the cpu waits for the disk io but if your storage is fast enough the cpu may become the bottleneck.
i am running on a gbit network cluster filesystem providing constantly 30mb/s to the miner.
the miner consumes about 5% cpu load and 20-30% io waits.
this 5% relates to 8 threads which means the miner may use up to 12.5% cpu load before it becomes the bottleneck.
for a 4 minute blocktime my calculation says this setup works up to 16tb plots.
if the storage could provide more than 60mb/s the cpu of this setup is the bottleneck.
so before i have 16tb plots during the next days i have to redesign my storage layout to work with several miner instances.