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

[leowonderful]

Is it possible to use space on a usb to mine? If so, how?

[1714252541]

1714252541

[1714252541]

1714252541

[vbcs]

Also, if anyone wants to fund a project using AT and Burst using the crowdfund use case please send me a message to arrange it.

[unsoindovo]

Is it possible to use space on a usb to mine? If so, how?

hahahahaha

nice try!!!

read some page around...

with a few GB you do nothing...

to gain something try with at least 10TB..

check here:

http://burstcoin.eu/calculator
with 10TB you get 3350 burst day...

sorry for this clarification!!!

[leowonderful]

Soon, there'll be huge racks of external hard drives inside warehouses, with like more than 1PB of storage... Just like bit coin xc

[popolite11]

Soon, there'll be huge racks of external hard drives inside warehouses, with like more than 1PB of storage... Just like bit coin xc

There will also be a shortage of hard drives soon.

[bensam123]

Yeah, USB 2 has quite a bit of overhead, CPU wise, something people should consider...

Is there more then one different optimizing utility? How long does it take to optimize a drive? Is there a GPU assisted optimizer?

Why don't plotters do this automatically?

I'll give it a go on one of my 5TB drives and see if it improves the block mine time.

Any answers to the Qs?

[Merick]

Yeah, USB 2 has quite a bit of overhead, CPU wise, something people should consider...

Is there more then one different optimizing utility? How long does it take to optimize a drive? Is there a GPU assisted optimizer?

Why don't plotters do this automatically?

I'll give it a go on one of my 5TB drives and see if it improves the block mine time.

Any answers to the Qs?

https://burstforum.com/index.php?threads/plot-optimizer-v1-6-j6jq.268/ - Modification of DCCT Optimizer

https://burstforum.com/index.php?threads/plot-optimizer-gui-1-0-4.589/ - GUI for said Optimizer - beta

http://burstcoin.eu/download/3-dcct's-miner-and-plot-tools - DCCT Optimzer

These are the only Optimizers I am aware of.

There is no GPU optimizer because optimizing is not about doing any calculations or hashing but about re-organized the Nonces within the plot file. Maybe a GPU can do this better than a CPU but I have not seen anyone release anything.  Consider Plot optimization as similar to defragging your hard-drive.  The Optimizer takes all of your nonces and places them in a nice neat order so when the miner looks for a particular nonce the remaining search will be sequential instead of having to bounce around the drive in blocks that are equal to the stagger size. ( my basic understanding of the process)

Speed will be dependent on your CPU and drives.  Optimizing using a read on one drive and a write on another drive should be faster than read and writing on the same drive.  The J6 Optimizer allows for this method, were as the original DCCT optimizer is only capable of reading and writing to the same drive.  So when using the DCCT optimizer you have to have room on your drive for both the original plot file and the optimized plot file.  I use a old E5800 3GHz dual core Intel and it takes I think an 1hr / 100GB to optimize using DCCT.  (I forget the exact time, but this sorta of sounds right).

The GPU plotter will create an optimized plot file if you use the direct write method instead of the buffer write method.  The direct method has its draw backs with increased memory usage and slower speed.  I think so far it is customary to just plot using a comfortable stagger and then optimize.

Well, that's my take on your questions, maybe some-one else can give more detail or correct any of my possible inaccuracies.

Good-Luck

[fivebells]

I received a transaction from mininghere.  Anyone know what they're about?

Also, I just noticed the following error in my burst mining logs.  Looks like an AT might have broken something?

Code:

2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found
2015-01-25 11:21:25 INFO: get timestamp for tx with id -4762078490203704075 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

[bensam123]

https://burstforum.com/index.php?threads/plot-optimizer-v1-6-j6jq.268/ - Modification of DCCT Optimizer

https://burstforum.com/index.php?threads/plot-optimizer-gui-1-0-4.589/ - GUI for said Optimizer - beta

http://burstcoin.eu/download/3-dcct's-miner-and-plot-tools - DCCT Optimzer

These are the only Optimizers I am aware of.

There is no GPU optimizer because optimizing is not about doing any calculations or hashing but about re-organized the Nonces within the plot file. Maybe a GPU can do this better than a CPU but I have not seen anyone release anything.  Consider Plot optimization as similar to defragging your hard-drive.  The Optimizer takes all of your nonces and places them in a nice neat order so when the miner looks for a particular nonce the remaining search will be sequential instead of having to bounce around the drive in blocks that are equal to the stagger size. ( my basic understanding of the process)

Speed will be dependent on your CPU and drives.  Optimizing using a read on one drive and a write on another drive should be faster than read and writing on the same drive.  The J6 Optimizer allows for this method, were as the original DCCT optimizer is only capable of reading and writing to the same drive.  So when using the DCCT optimizer you have to have room on your drive for both the original plot file and the optimized plot file.  I use a old E5800 3GHz dual core Intel and it takes I think an 1hr / 100GB to optimize using DCCT.  (I forget the exact time, but this sorta of sounds right).

The GPU plotter will create an optimized plot file if you use the direct write method instead of the buffer write method.  The direct method has its draw backs with increased memory usage and slower speed.  I think so far it is customary to just plot using a comfortable stagger and then optimize.

Well, that's my take on your questions, maybe some-one else can give more detail or correct any of my possible inaccuracies.

Good-Luck

Thanks for the clarification... Not really digging the time table though. Based on what you said, optimizing would take longer then plotting.

Ah my god, that's what the direct write method was... I thought it just operated at reduced memory usage as both options aren't explained well. SOB.

[vbcs]

I received a transaction from mininghere.  Anyone know what they're about?

Also, I just noticed the following error in my burst mining logs.  Looks like an AT might have broken something?

Code:

2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found
2015-01-25 11:21:25 INFO: get timestamp for tx with id -4762078490203704075 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Probably some miners have outdated version and this is why you are receiving that error. I am getting also the same. Looking into it. We were getting the same error when doing test with burstdev with version 1.2.0 . We fixed that bug in 1.2.1 version

[go6ooo1212]

Guys , I found the perfect MB for mining BURST:
http://www.asrock.com/mb/Intel/Z87%20Extreme11ac/index.us.asp

[vbcs]

I received a transaction from mininghere.  Anyone know what they're about?

Also, I just noticed the following error in my burst mining logs.  Looks like an AT might have broken something?

Code:

2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found
2015-01-25 11:21:25 INFO: get timestamp for tx with id -4762078490203704075 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Probably some miners have outdated version and this is why you are receiving that error. I am getting also the same. Looking into it. We were getting the same error when doing test with burstdev with version 1.2.0 . We fixed that bug in 1.2.1 version

If a miner using the latest 1.2.1 version when mines the block gets the same error please report it.

[vbcs]

I received a transaction from mininghere.  Anyone know what they're about?

Also, I just noticed the following error in my burst mining logs.  Looks like an AT might have broken something?

Code:

2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found
2015-01-25 11:21:25 INFO: get timestamp for tx with id -4762078490203704075 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

Probably some miners have outdated version and this is why you are receiving that error. I am getting also the same. Looking into it. We were getting the same error when doing test with burstdev with version 1.2.0 . We fixed that bug in 1.2.1 version

If a miner using the latest 1.2.1 version when mines the block gets the same error please report it.

Just saw a new block and everything seems fine. So I was correct saying that some miners use an outdated version.

[bensam123]

Question about the J6 optimizer. Why would you want it to wait for free memory? What happens if it continues on? Does it optimize better with more memory available?

[mmmaybe]

IMPORTANT

EVERY MINER WHO HAS NOT UPDATED THEIR WALLET TO 1.2.1 MUST UPDATE AS SOON AS POSSIBLE!

LINK TO DOWNLOAD IS FOUND IN OP: https://bitcointalk.org/index.php?topic=731923.msg8272935#msg8272935

THANKS FOR COOPERATION

[coinits]

@mmmaybe

As described earlier, I have faith and active participation in BURST community, but really have no time and knowledge to help, also my English is horrible, but I hope for a "honored member" or "believer" ribbon Or just "Burster senior"

glad I made you smile and as far SETI, I will leave my house keys , wallets unlocked, passwords to cryptsy bittrex polo something, and trade for an encounter just the same,

seeing magnitude of "blockchain" discovery who is to say they are not already here

They have always been here. You don't think that humans invented microprocessors, lasers, microwaves, fiber optics on their own do you? All are reversed engineered alien technologies. True dat!

[mmmaybe]

How many lottery tickets do you have? I'v bought 12 tickets so far...

Need to win this not to go broke

EDIT: make that 15 now... Very addictive 

[Irontiga]

Mmmm... I was thinking to try mining with raspberry pi b+ to save electricity, and I don't it is possible now after reading you post above. I think that the reason why I did not see anyone mine burstcoin with raspberry pi yet...

Why don't you try, likr a proof-of-concept....? 

It would be quite interesting to know how a raspberry would do, especially as we call BURST "enegy-friendly".

I'm already planning a test I'll keep ya posted.

If crowetic already planned to start the raspberry test, and since I do not have a raspberry on hand yet, then I will wait for your proof-of-concept, 

I think that a raspberry pi has to low cpu-capacities for calculating those hashes. Maybe it'll work for <1TB, but not more. You also need a lot of cpu-power for the USB-Port (data transfer).

i think raspberry,
here is intendend to mine.
not to plot files...

to plot file you need  high end CPU o a good GPU.
i think 280X.
but with the latest CPU [i7 haswell] plotter i can see the performance are similar...
and more...
if you use CPU plotter you can rise stagger size to optimize plot...

What would be kewl is if we used a parallella 16

[unsoindovo]

How many lottery tickets do you have? I'v bought 12 tickets so far...

Need to win this not to go broke

EDIT: make that 15 now... Very addictive 

hem hem...

can someone present the Lottery service plz!?!??!

i'm interested!!!

there is a site where i can read something about lotto..

there are previous extractions already done??

there is a simply how-to who explain how to buy tickets??

it is just like buy assets shares?

[Merick]

IMPORTANT

EVERY MINER WHO HAS NOT UPDATED THEIR WALLET TO 1.2.1 MUST UPDATE AS SOON AS POSSIBLE!

LINK TO DOWNLOAD IS FOUND IN OP: https://bitcointalk.org/index.php?topic=731923.msg8272935#msg8272935

THANKS FOR COOPERATION

The banner still says 1.2.0 but  the actual downloaded file is 1.2.1