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

[timk225]

You people are still trying to make this shitcoin work?  Wow you're stupid.  I got out of it weeks ago and am far happier without the stress of this crapcoin on my mind.

[Trollollo]

Wow!You are back!Write please something else,just for fun!I like your comments so much!Are you still mining with 10 GB solo?LOL

[Nevril]

Update v1.0.4

Burst Long Term Price Support project
(BLTPS)

Changelog
v1.0.4 - 09/nov/2014
Text prepared for the transition to Phase 2 (v1.1.0)
Maximum amount of shares per person increased from 20 to 70
Specific Burst and Bitcoin addresses have been generated to handle the project
BLTPS shares are issued and Phase 1 supporters have details on how to buy them
Some ETAs have changed to be sooner than what initially expected

Remember that Phase 1 ends today.
As soon as the first wave of shares is sold, Phase 2 will start. It will still be possible to buy shares at the same price, until Phase 3.
This is a great opportunity for Burst to stabilize and grow. Make sure you get some!

[FakeAccount]

I have a question. If I have 2 different HD and on the first one my plot is XXX_1_800000_1000, on my second drive, can the plot look the same as on HD1 or do I have to do a plot from nonce 800001?
Thanks!

Plot from nonce 800000, not 800001. That would create a 1-nonce gap. 800000 is nonce count, not end nonce.
Also, I suggest using a higher stagger, 1000 will result in a lot of seeking.

UPD:
didn't notice start nonce is 1. I'd use something like:

XXX_0_800000_40000
XXX_800000_800000_40000
XXX_1600000_800000_40000
etc

why would a 1 nonce gap matter?

[majere]

why would a 1 nonce gap matter?

It doesn't matter, but it's easier to count this way.

[FakeAccount]

yeah, that's what I found, the windows re-plotter produces corrupted file.  it was incorrect size given stagger size etc...
localhost is fine.  I tested that with other files to make sure.

BURST miner, v1.141020
Programming: dcct (Linux) & Blago (Windows)
CPU support:  AES  SSE4  AVX  AVX2
Node: localhost (ip: 127.0.0.1)
Node: localhost (ip: 127.0.0.1)
Using plots:
Y:\plots\       files: 1         size: 1858 Gb
TOTAL: 1858 Gb

--- 21:14:39 ---    New block 29540, basetarget 2998332    ------------
*** Chance to find a block: 0.02970%
21:14:39 [xxxxxxxxxxxxxxxxxxx]  found deadline 790396957
21:14:39 [xxxxxxxxxxxxxxxxxxx]  found deadline 392940853
21:14:39 [xxxxxxxxxxxxxxxxxxx] sent DL: 392940853       4547d 22h 14m 13s
21:14:39 [xxxxxxxxxxxxxxxxxxx]  found deadline 165320872
21:14:39 [xxxxxxxxxxxxxxxxxxx]  found deadline 143340366
21:14:39 [xxxxxxxxxxxxxxxxxxx] sent DL: 143340366       1659d 0h 46m 6s
21:14:39 [xxxxxxxxxxxxxxxxxxx]  found deadline 27461602
21:14:39 [xxxxxxxxxxxxxxxxxxx] sent DL: 27461602        317d 20h 13m 22s
21:14:39 Confirmed DL: 5446372073854    63036713d 19h 37m 34s
21:14:39 [xxxxxxxxxxxxxxxxxxx]  165320872 > 27461602  discarded
21:14:39 Confirmed DL: 6091147647021    70499394d 1h 30m 21s
21:14:39 [xxxxxxxxxxxxxxxxxxx]  790396957 > 27461602  discarded
21:14:39 Confirmed DL: 6134291670940    70998746d 4h 35m 40s
21:14:39 [xxxxxxxxxxxxxxxxxxx]  found deadline 2275525
21:14:39 [xxxxxxxxxxxxxxxxxxx] sent DL: 2275525 26d 8h 5m 25s
21:14:40 Confirmed DL: 5975898902375    69165496d 13h 19m 35s
21:14:40 [xxxxxxxxxxxxxxxxxxx]  found deadline 1561449
21:14:40 [xxxxxxxxxxxxxxxxxxx] sent DL: 1561449 18d 1h 44m 9s
21:14:40 Confirmed DL: 4101564822843    47471815d 1h 54m 3s
21:14:42 [xxxxxxxxxxxxxxxxxxx]  found deadline 915567
21:14:42 [xxxxxxxxxxxxxxxxxxx] sent DL: 915567  10d 14h 19m 27s
21:14:42 Confirmed DL: 5635954431523    65230954d 1h 38m 43s
21:14:48 [xxxxxxxxxxxxxxxxxxx]  found deadline 59908
21:14:48 [xxxxxxxxxxxxxxxxxxx] sent DL: 59908   0d 16h 38m 28s
21:14:48 Confirmed DL: 3470582522731    40168779d 4h 45m 31s
21:14:53 Thread "Y:\plots\" done! [~14 sec] (1 files)
[100%] 1858 GB. deadline 3470582522731s  sdl:7/0(0) cdl:7(0) ss:8(0) rs:8(0)
...

Sent deadlines != confirmed deadlines. Daemon is not synced or plot-file is corrupted.

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.

original file got deleted. (which I didn't like since I had to re-create oroginal file again... maybe it would be better to create a parameter to control this?)

i did not use any delaying.  just specified 1 gig of memory

2 scoops

don't know if every plot.  can try on another plot, but first need to make a copy of it since I don't want to lose the original plot, so this will take some time.

using this works OK: Optimizer.exe 30 Y:\plots -m 4g X:\plots\XXXXXXXXXXXXXXXXXXX_XXXXXXXXX_XXXXXXX_XXXX

re-plotted file is working OK.  correct deadlines are found, submitted and verified. sorry it took a while to test on a different file with different parameters. this was tested not using 1.6 but prior ver.

[m3ta]

You people are still trying to make this shitcoin work?  Wow you're stupid.  I got out of it weeks ago and am far happier without the stress of this crapcoin on my mind.

As long as you keep posting, it means you didn't "get out of it" and you're the stupid one.
But by all means, do go on. It's nice to have a clown around.

[Pilotseye]

You people are still trying to make this shitcoin work?  Wow you're stupid.  I got out of it weeks ago and am far happier without the stress of this crapcoin on my mind.

he's just jealous 

[q327K091]

You people are still trying to make this shitcoin work?  Wow you're stupid.  I got out of it weeks ago and am far happier without the stress of this crapcoin on my mind.

he's just jealous 

correct + he missed the boat on bitcoin, people are adding storage as we speak, there is a fund running to stabilize price, I am very optimistic you should be too, but you need to wait over depression era in crypto.. in general, not just BURST.. keep on mining accumulate , steady as she goes

[traderman]

Does the stagger size affect the mining speed in any way?

[majere]

Does the stagger size affect the mining speed in any way?

It affects the amount of seeking = HDD lifetime.
Also, lots of seeking leads to slower reading of files, may miss shorter blocks with small stagger.
Treat stagger as "how many subfiles this file consists of".
10 files with ideal stagger (file size==stagger size) roughly equals 1 file with stagger 1/10 of filesize.

[pinballdude]

hey guys where can i take servers with big HDDs at a good price? Can you suggest me any server site?

My intention is to buy 2 or 3 servers and let them mining burst 24\24 7\7, but i've just one question: can i set burst mining on a different OS than Windows?

Easiest way to do it, pm us and we can work good stuff out.

https://burstforum.com/index.php?threads/ann-bytecloud.312/

And never mind there being other os for mining....use Linux....much, much better!!

I am using windows 7, and while it actually works now for me, it is obvious that windows simply cannot cope with the tech requirements. I even have a growing list of applications that are no-go if my burst mining has to run at 100%. Anyone planning to mine more than 10 TB on one computer should seriously consider using linux to avoid the problems related to the windows paging and virtual memory system forcing processes to crash, when you start reading serious amounts of data. Another windows (out of the box) problem is that time might drift - the standard windows way of keeping time synced with the internet does not work well,unless perhaps if you have a domain server that itself have commercial stuff on it to keep internet time correctly.  If you dig in deeper with burst, it is also a hassle to compile on a non-modified windows, and the list goes on.

I'm only staying on windows in an attempt to gain knowledge and spread this knowledge to others who might not have the option of shifting over to linux. And because i',m stubborn.

[traderman]

Gotcha, thanks for the help!

Does the stagger size affect the mining speed in any way?

It affects the amount of seeking = HDD lifetime.
Also, lots of seeking leads to slower reading of files, may miss shorter blocks with small stagger.
Treat stagger as "how many subfiles this file consists of".
10 files with ideal stagger (file size==stagger size) roughly equals 1 file with stagger 1/10 of filesize.

[pinballdude]

You people are still trying to make this shitcoin work?  Wow you're stupid.  I got out of it weeks ago and am far happier without the stress of this crapcoin on my mind.

If you can get the basetarget to 10'000'000 i will donate you 10K burst and keep sending you 10K burst every week you can hold it down there.  Limit is 100K burst, then we'll have to renegotiate.

basetarget is 3'000'000 right now, so you'll have to really beef up your burst whining if you want to earn any.

What's in it for me?  i'd love to mine more burst, and if the basetarget go up there, i will get WAY more blocks.

Also, if you want to argue about why the BURST price should be lower, you need to study a little, your current arguments seem a little childish to me.

how about  :

calculating the final amount of coins, and the resulting market cap, and then contemplate if the current price is reasonable for so many coins - are we already fully priced?

you can argue that BURST only have one core developer and if he for some reason stops developing, BURST will probably crash and it is not a given that the remaining people involved with BURST have enough knowledge to take over - We are updating from Nxt source regularily, and those updates are not at all trivial. We also seem to not have any kind of unit tests or general testing environment, so new developers taking over will have a hard time figuring if they break something or not.

you can argue that harddisk mining is not economical in some way, or perhaps not fair in some way.

You can argue that something else comes along that is more profitable when you have free harddisk space. How many miners would stay here, if a new coin came along that was double profitable per TB

Now, i have helped you a lot, please hang in there, but i would prefer good arguments instead of just babble. Criticism is good, it makes us better identify areas that might need to be improved.

imagine a freight train in the distance, and a monkey standing at the side of the tracks, throwing bananas onto the train to stop it.. you are the money, the banana is your arguments, and the freight train... that's BURST.  You won't delay it one second, but you have a certain amount of entertainment value.

Seriously, if you want BURST price to go down so you can buy more of it, create a serious list of issues and reasons, place it in a post, and link to that post from new posts every time you figure out a new reason why BURST might go down in price. As BURST is 90% Nxt if not more, you should have no trouble finding issues with Nxt and then just put these on your list.

To everyone else i say : buy the dips, make this monkey work for you ;-)

[vipervince2002]

. . .

original file got deleted. (which I didn't like since I had to re-create oroginal file again... maybe it would be better to create a parameter to control this?)

i did not use any delaying.  just specified 1 gig of memory

2 scoops

don't know if every plot.  can try on another plot, but first need to make a copy of it since I don't want to lose the original plot, so this will take some time.

using this works OK: Optimizer.exe 30 Y:\plots -m 4g X:\plots\XXXXXXXXXXXXXXXXXXX_XXXXXXXXX_XXXXXXX_XXXX

re-plotted file is working OK.  correct deadlines are found, submitted and verified. sorry it took a while to test on a different file with different parameters. this was tested not using 1.6 but prior ver.

I am glad to hear it is working now. 1.6 was only a small update to prevent deleting and the plot file should not be any different from the previous versions.

[einsteinium.biz]

FREE publicity, get it while it's still free,

for your coin,
for your product,
for your service,
for yourself!

If you have a press release about Burst and want us to publish it, we will.
If you have an article about Burst coin and you want us to publish it, we will.

If you have Burst  tee-shirts and want us to sell it, and want us to only accept Burst coin for payment, we will.

If you want to have a small size banner advertising Burst coin in our publication we could do that too.


ALL OF THE ABOVE ABSOLUTELY FREE!!!   well at least for the month of NOVEMBER -- who passes up on free publicity?

[hvidgaard]

I am using windows 7, and while it actually works now for me, it is obvious that windows simply cannot cope with the tech requirements. I even have a growing list of applications that are no-go if my burst mining has to run at 100%. Anyone planning to mine more than 10 TB on one computer should seriously consider using linux to avoid the problems related to the windows paging and virtual memory system forcing processes to crash, when you start reading serious amounts of data.

I have a Windows box mining 20TB, and no problem using it at the same time for my day job as a developer. No idea what you have tweaked to make performance subpar.

Another windows (out of the box) problem is that time might drift - the standard windows way of keeping time synced with the internet does not work well,unless perhaps if you have a domain server that itself have commercial stuff on it to keep internet time correctly.

Windows by default sync time every 5 days, can be changed if your clock drift too much. Again, not a problem, particularly considering that you have to install NTP and enable it on Linux to have the functionallity at all.

If you dig in deeper with burst, it is also a hassle to compile on a non-modified windows, and the list goes on.

It's a hassle to install VS or GCC for C/C++, or JDK for Java and compile it? It's not any different from Linux except dependencies, and that really isn't a problem. Besides, JDK is much more of a hassle on Linux than it is on Windows.

[crowetic]

Updates on status of http://burst.ga pool

Hello everyone! I have been working very diligently to make sure we have everything setup perfectly, and redundantly. This is what I have come up with so far...

We will have 3, possibly 4 servers for this redundancy.

Server 1 will be a small linux VM (in a data center) that will function as the balancer/failover server. The point of this is so that the miners never have to change the IP they're pointing to, and thus never have to worry about restarting, etc. Good for miners!

Server 2 will be the main pool server, it will be running on a dedicated rackserver in a data center. This server will be the main pool server, and shouldn't hardly ever be down.

Server 3 will be the backup pool server. (This is currently the server the pool is running on.) This server is a rackserver running VMWare ESXi. This server's only purpose is to be the temporary backup in the case that the main server goes down. This server will not have payments enabled once the final setup is completed, so payments will only happen when on the main server. But we are hoping that the backup server hardly ever gets used. That's the ideal scenario, only use it when absolutely necessary, to keep miners connected until the main server comes back up. that's it.

RIGHT NOW...

I am setting up a test backup server, and will be using the current server as the main server for a few days. the purpose of this is to test the balancer server we've setup.

So, miners will need to restart their client this one time, in order to get connected to the balancer server, after that restarts should no longer be necessary.

I will let everyone know when we actually make the changes, and the restart of the miners is necessary. Stay tuned. Thanks!

[crowetic]

Okay, we're going to make the changes, so any of our miners once you notice issues, restart the miners, and you should be good to go, shouldn't be any more restarts required after this. Thanks!

My partner will be making the IP changes soon, so if you notice the miner not working right, just restart it, and everything should be great after that!


edit: Not exactly sure how long it will take him to read my message and make the changes, so I will post another message once I know it's been done for sure.

[TetraHect0rCannabinol]

You people are still trying to make this shitcoin work?  Wow you're stupid.  I got out of it weeks ago and am far happier without the stress of this crapcoin on my mind.

If you can get the basetarget to 10'000'000 i will donate you 10K burst and keep sending you 10K burst every week you can hold it down there.  Limit is 100K burst, then we'll have to renegotiate.

basetarget is 3'000'000 right now, so you'll have to really beef up your burst whining if you want to earn any.

What's in it for me?  i'd love to mine more burst, and if the basetarget go up there, i will get WAY more blocks.

Also, if you want to argue about why the BURST price should be lower, you need to study a little, your current arguments seem a little childish to me.

how about  :

calculating the final amount of coins, and the resulting market cap, and then contemplate if the current price is reasonable for so many coins - are we already fully priced?

you can argue that BURST only have one core developer and if he for some reason stops developing, BURST will probably crash and it is not a given that the remaining people involved with BURST have enough knowledge to take over - We are updating from Nxt source regularily, and those updates are not at all trivial. We also seem to not have any kind of unit tests or general testing environment, so new developers taking over will have a hard time figuring if they break something or not.

you can argue that harddisk mining is not economical in some way, or perhaps not fair in some way.

You can argue that something else comes along that is more profitable when you have free harddisk space. How many miners would stay here, if a new coin came along that was double profitable per TB

Now, i have helped you a lot, please hang in there, but i would prefer good arguments instead of just babble. Criticism is good, it makes us better identify areas that might need to be improved.

imagine a freight train in the distance, and a monkey standing at the side of the tracks, throwing bananas onto the train to stop it.. you are the money, the banana is your arguments, and the freight train... that's BURST.  You won't delay it one second, but you have a certain amount of entertainment value.

Seriously, if you want BURST price to go down so you can buy more of it, create a serious list of issues and reasons, place it in a post, and link to that post from new posts every time you figure out a new reason why BURST might go down in price. As BURST is 90% Nxt if not more, you should have no trouble finding issues with Nxt and then just put these on your list.

To everyone else i say : buy the dips, make this monkey work for you ;-)

Nicely Put ++

Nothing in life is free, nothing in life can evolve without a cause and most importantly... things can get better, you just have to try