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

[crowetic]

-[BURST.GA POOL ANNOUNCEMENT and BETA TESTERs NEEDED for NEW POOL CODE!! PM ME! (I put this all here for people who don't like to read...)]-

Hello everyone!


This is the announcement of the new pool code coming into function on the burst network. I have hired a fantastic developer with the nick of 'catbref' who has been amazing. He has whipped up a completely new pool code from the ground up, not only for me, because I requested it, but also for the miners of BURST, to give them more variety and choices of where to mine, and settings. It will be great!

So, what we need from you now, is this!!

1. I am going to need a group of beta testers. This group of beta testers will be the closed beta group for the second pool server, which will eventually be turned into burst.ga's EU pool cousin. This group will have direct access to tell the dev what they would like to see, any issues, and ideas for improvement, or whatever they want to suggest!

2. The beta testers will need to have an account at www.burstforum.com as that is where the conversation about the beta test will go down. So, what you will need to do, if you don't have an account at burstforum already, and you want to get involved in the closed beta, go make an account there, and let me know your account name when you PM me to let me know you want to be part of the beta group.

3. That's pretty  much it for the beta test group, just send me a PM and let me know that you'd like to be part of the closed beta group, and I will provide you with the server IP and reward assignment account for the pool once the closed beta is starting.



The future of http://burst.ga and ByteEnterprises pools


(ByteEnterprises is what Irontiga and I call our venture, in case you weren't aware of that. We have a really great team of people working with us, and we will give you more information on ByteEnterprises once we do the asset changes and things that are going down right now in the background.)


1. burst.ga, as it is currently, will cease (in favor of new code). Once the new code is up and running, and we've gone from closed beta to open beta, and everything seems to be working as it should, we will be shutting the server for burst.ga down, updating the code, and putting it back up as the new coded pool, it will be the US burst.ga pool, just as it is now, but with the new code.
2. We will be doing the closed beta of the new code.
3. We will move the closed beta into an open beta. The open beta server will be an EU dedicated server.
4. Once we have finished all of our beta testing, we will be moving all pools to the new code, (well, both, not 'all',) and running happily off into the sunset.



So, another thing I want everyone to know...


BURST for the win!

Sorry, not just that, but also...

we will have more stats, more features, and more awesomeness than other pools. We will be setting up the two pools to work better for different sized miners, with more stats for them and super badass awesomeness.

The new code can already estimate the "hashpower" AKA size of a miner, and divides the shares in a sweet visual aspect, and I'm sure everyone will enjoy the capabilities of the new code.
Also, my closed beta testers will have access to the developer directly in the convo that I will start on burstforum, and they will be able to make suggestions of changes, additions, etc. As well as give their experience on the pool, and what they think were issues. So we can work together with the dev to fix everything and take care of any issues.

Thanks and happy new year to all! 2015, the YEAR OF BURST!

[1713911659]

1713911659

[b3da]

I rewrited big part of my Burst mining summary.
It should be usable for all miners, including those switching between solo and pools.
You can view your reward assignment history in simple table now.
I will be working on it more, as I can find some spare time :0)
hope some of you find it bit useful..

[Hellsgremlin]

Ok so I have about 4 drives currently plotted and about 6 more to go. Just want to make sure im doing this correctly

When plotting a drive should i start each drive at nonce 0 or pickup where the last drive ended?

for example should i be doing
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 800001 - 1600000 Drive 3: Nonce 1600001 - 2400000
Or
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 0 - 800000 Drive 3: Nonce 0 - 800000

Please im concerened i might be doing this wrong as i have a 1 TB Plot on a different computer that has been Getting better payouts then my Currently 10TB's Machine

[Vorksholk]

Ok so I have about 4 drives currently plotted and about 6 more to go. Just want to make sure im doing this correctly

When plotting a drive should i start each drive at nonce 0 or pickup where the last drive ended?

for example should i be doing
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 800001 - 1600000 Drive 3: Nonce 1600001 - 2400000
Or
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 0 - 800000 Drive 3: Nonce 0 - 800000

Please im concerened i might be doing this wrong as i have a 1 TB Plot on a different computer that has been Getting better payouts then my Currently 10TB's Machine

For the same address, never overlap nonces--this would be similar to having multiple GPUs using the same nonces to mine.

However, if each drive is mining to a different address, then they can use the same nonces as you used on other drives for other addresses.

[xizmax]

Ok so I have about 4 drives currently plotted and about 6 more to go. Just want to make sure im doing this correctly

When plotting a drive should i start each drive at nonce 0 or pickup where the last drive ended?

for example should i be doing
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 800001 - 1600000 Drive 3: Nonce 1600001 - 2400000
Or
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 0 - 800000 Drive 3: Nonce 0 - 800000

Please im concerened i might be doing this wrong as i have a 1 TB Plot on a different computer that has been Getting better payouts then my Currently 10TB's Machine

Hehe, I'm close to superstition that some plots are "luckier" than others myself

Must be weird coincidences. However, as Vorksholk said, do not overlap them for the same account

[Hellsgremlin]

Ok so I have about 4 drives currently plotted and about 6 more to go. Just want to make sure im doing this correctly

When plotting a drive should i start each drive at nonce 0 or pickup where the last drive ended?

for example should i be doing
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 800001 - 1600000 Drive 3: Nonce 1600001 - 2400000
Or
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 0 - 800000 Drive 3: Nonce 0 - 800000

Please im concerened i might be doing this wrong as i have a 1 TB Plot on a different computer that has been Getting better payouts then my Currently 10TB's Machine

For the same address, never overlap nonces--this would be similar to having multiple GPUs using the same nonces to mine.

However, if each drive is mining to a different address, then they can use the same nonces as you used on other drives for other addresses.

LoL,  I have 9TB to Replot!
Could have been worst.... Could have been 20tb      TY for stopping me before things got out of hand

[Irontiga]

Ok so I have about 4 drives currently plotted and about 6 more to go. Just want to make sure im doing this correctly

When plotting a drive should i start each drive at nonce 0 or pickup where the last drive ended?

for example should i be doing
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 800001 - 1600000 Drive 3: Nonce 1600001 - 2400000
Or
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 0 - 800000 Drive 3: Nonce 0 - 800000

Please im concerened i might be doing this wrong as i have a 1 TB Plot on a different computer that has been Getting better payouts then my Currently 10TB's Machine

For the same address, never overlap nonces--this would be similar to having multiple GPUs using the same nonces to mine.

However, if each drive is mining to a different address, then they can use the same nonces as you used on other drives for other addresses.

LoL,  I have 9TB to Replot!
Could have been worst.... Could have been 20tb      TY for stopping me before things got out of hand

I think we're a bit late for that, 9 tb is pretty out of hand lol

[Irontiga]

Hey, @burstdev

I am making a new blockex, but whenever i test with a certain account, it just takes ages to try and load, and then gives an error after crashing my wallet. The specific account that i know to do this is BURST-L28E-WSYC-F4N3-B82AC

What is wrong with it? Is it's pool accountness giving it too many tx.'s or something? I really don't know why the wallet would crash tho....

[0bert]

Hey@all!

I am new to Burst and i want to mine some coins, at least try it. 
I will study the guide now/soon, just did a quick scan...

I have a GTX 670, so i guess i should use the GPU Plotter.

But which miner do you recommend? It doesn't matter or some differences between them?

Maybe most important:
How many TB i should take to start... ? (Guide said 2TB, but it's old...  )
(Some small payouts on poolmining after 24h lately would be enough to begin with...  )

Anything else i should know?
Thanks for you help!

Greets 0bert

[12gaFacelift]

Ok so I have about 4 drives currently plotted and about 6 more to go. Just want to make sure im doing this correctly

When plotting a drive should i start each drive at nonce 0 or pickup where the last drive ended?

for example should i be doing
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 800001 - 1600000 Drive 3: Nonce 1600001 - 2400000
Or
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 0 - 800000 Drive 3: Nonce 0 - 800000

Please im concerened i might be doing this wrong as i have a 1 TB Plot on a different computer that has been Getting better payouts then my Currently 10TB's Machine

For the same address, never overlap nonces--this would be similar to having multiple GPUs using the same nonces to mine.

However, if each drive is mining to a different address, then they can use the same nonces as you used on other drives for other addresses.

I do not understand the "never overlap nonces" so here is my question, how to do with multiple hard drive, at the moment i have 5 hard drive with 1tb each.

drive 1 : 0 - 3700000
drive 2 : 0 - 3700000
drive 3 : 0 - 3700000
drive 4 : 0 - 3700000
drive 5 : 0 - 3700000

all of them are mining with the same adress at the same pool :-s

if this is not the right wait can you help me to make it better.

Thanks

[xizmax]

Hey@all!

I am new to Burst and i want to mine some coins, at least try it.  
I will study the guide now/soon, just did a quick scan...

I have a GTX 670, so i guess i should use the GPU Plotter.

But which miner do you recommend? It doesn't matter or some differences between them?

Maybe most important:
How many TB i should take to start... ? (Guide said 2TB, but it's old...  )
(Some small payouts on poolmining after 24h lately would be enough to begin with...  )

Anything else i should know?
Thanks for you help!

Greets 0bert

I mine with a very small plot, some 300gb and I get some small payments let's say an average of 100 coins a day (way below roi but I do it for fun), so 2TB is okay.

GPU plot > optimize > mine

If you're on nix preferred miner is dcct (or that is the word on the street IIRC, I'm using windows)
On windows it's blago's miner and uray's miner

Study the guide, it is not half bad. I managed to set it up on my own. I was, and still am, a noob. Therefore it should not be too difficult.

If you get stuck, ask away

Ok so I have about 4 drives currently plotted and about 6 more to go. Just want to make sure im doing this correctly

When plotting a drive should i start each drive at nonce 0 or pickup where the last drive ended?

for example should i be doing
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 800001 - 1600000 Drive 3: Nonce 1600001 - 2400000
Or
Drive 1: Nonce 0 - 800000 Drive 2: Nonce 0 - 800000 Drive 3: Nonce 0 - 800000

Please im concerened i might be doing this wrong as i have a 1 TB Plot on a different computer that has been Getting better payouts then my Currently 10TB's Machine

For the same address, never overlap nonces--this would be similar to having multiple GPUs using the same nonces to mine.

However, if each drive is mining to a different address, then they can use the same nonces as you used on other drives for other addresses.

I do not understand the "never overlap nonces" so here is my question, how to do with multiple hard drive, at the moment i have 5 hard drive with 1tb each.

drive 1 : 0 - 3700000
drive 2 : 0 - 3700000
drive 3 : 0 - 3700000
drive 4 : 0 - 3700000
drive 5 : 0 - 3700000

all of them are mining with the same adress at the same pool :-s

if this is not the right wait can you help me to make it better.

Thanks

That is kinda bad, you are effectively mining with only 1TB.

When mining with the same account and multiple drives you "add" nonces accross drives. So,
drive 1: 0 - 370000
drive 2: 370001 -  740000
drive 3: 740001 - 1110000 and so on

I'm afraid you need to replot

EDIT: Btw we really need a good gui, or at least a new guide

[pinballdude]

Hey, @burstdev

I am making a new blockex, but whenever i test with a certain account, it just takes ages to try and load, and then gives an error after crashing my wallet. The specific account that i know to do this is BURST-L28E-WSYC-F4N3-B82AC

What is wrong with it? Is it's pool accountness giving it too many tx.'s or something? I really don't know why the wallet would crash tho....

Hi irontiga, that address is uray's US pool, so it probably has loads and loads of transactions in it.

Can you craft an url with a API query that crashes the wallet, then others can try and see what happens. Perhaps all You need is just to up the amount of memory the wallet can use (the x something parameter when the wallet is started)

[b3da]

..
...
Can you craft an url with a API query that crashes the wallet, then others can try and see what happens. Perhaps all You need is just to up the amount of memory the wallet can use (the x something parameter when the wallet is started)

burst?requestType=getAccountTransactions&account=BURST-L28E-WSYC-F4N3-B82AC

[0bert]

Hey@all!

I am new to Burst and i want to mine some coins, at least try it.  
I will study the guide now/soon, just did a quick scan...

I have a GTX 670, so i guess i should use the GPU Plotter.

But which miner do you recommend? It doesn't matter or some differences between them?

Maybe most important:
How many TB i should take to start... ? (Guide said 2TB, but it's old...  )
(Some small payouts on poolmining after 24h lately would be enough to begin with...  )

Anything else i should know?
Thanks for you help!

Greets 0bert

I mine with a very small plot, some 300gb and I get some small payments let's say an average of 100 coins a day (way below roi but I do it for fun), so 2TB is okay.

GPU plot > optimize > mine

If you're on nix preferred miner is dcct (or that is the word on the street IIRC, I'm using windows)
On windows it's blago's miner and uray's miner

Study the guide, it is not half bad. I managed to set it up on my own. I was, and still am, a noob. Therefore it should not be too difficult.

If you get stuck, ask away

Thank you, good infos!
First i would start on windows, so blago's or uray's miner, alright!

btw:
Does it matter how fast my hdd is? Or just bigger is better?
What about SSD?  (just curious, don't want to use it)

Greets

[xizmax]

Hey@all!

I am new to Burst and i want to mine some coins, at least try it.  
I will study the guide now/soon, just did a quick scan...

I have a GTX 670, so i guess i should use the GPU Plotter.

But which miner do you recommend? It doesn't matter or some differences between them?

Maybe most important:
How many TB i should take to start... ? (Guide said 2TB, but it's old...  )
(Some small payouts on poolmining after 24h lately would be enough to begin with...  )

Anything else i should know?
Thanks for you help!

Greets 0bert

I mine with a very small plot, some 300gb and I get some small payments let's say an average of 100 coins a day (way below roi but I do it for fun), so 2TB is okay.

GPU plot > optimize > mine

If you're on nix preferred miner is dcct (or that is the word on the street IIRC, I'm using windows)
On windows it's blago's miner and uray's miner

Study the guide, it is not half bad. I managed to set it up on my own. I was, and still am, a noob. Therefore it should not be too difficult.

If you get stuck, ask away

Thank you, good infos!
First i would start on windows, so blago's or uray's miner, alright!

btw:
Does it matter how fast my hdd is? Or just bigger is better?
What about SSD?   (just curious, don't want to use it)

Greets

Some testing I read in this thread indicates that any reasonably new drive is fast enough. I don't believe people tried with ancient 4,2k rpm drives.

So it's a matter of bigger is better, hence SSD's hold no advantage atm

[Kartojal]

.......

First i would start on windows, so blago's or uray's miner, alright!

btw:
Does it matter how fast my hdd is? Or just bigger is better?
What about SSD?  (just curious, don't want to use it)

Greets

Some people reports that Blago miner is better than Uray, and you can use your SSD to plot more fast on it, and then move the plot to the desired HDD.

[burstcoin]

Hey, @burstdev

I am making a new blockex, but whenever i test with a certain account, it just takes ages to try and load, and then gives an error after crashing my wallet. The specific account that i know to do this is BURST-L28E-WSYC-F4N3-B82AC

What is wrong with it? Is it's pool accountness giving it too many tx.'s or something? I really don't know why the wallet would crash tho....

Just tried this, and it locked up firefox for a few minutes, but it eventually loaded. The wallet kept running unaffected and was reporting new blocks throughout. The massive tx count makes it a rather difficult query probably for any pool. You may want to try using the firstIndex and lastIndex parameters to reduce the amount reported each try, or just access the db directly instead of going through the client.

That request pulls 220962 transactions, and creates 177MB of json.

[coinits]

Hey, @burstdev

I am making a new blockex, but whenever i test with a certain account, it just takes ages to try and load, and then gives an error after crashing my wallet. The specific account that i know to do this is BURST-L28E-WSYC-F4N3-B82AC

What is wrong with it? Is it's pool accountness giving it too many tx.'s or something? I really don't know why the wallet would crash tho....

Just tried this, and it locked up firefox for a few minutes, but it eventually loaded. The wallet kept running unaffected and was reporting new blocks throughout. The massive tx count makes it a rather difficult query probably for any pool. You may want to try using the firstIndex and lastIndex parameters to reduce the amount reported each try, or just access the db directly instead of going through the client.

That request pulls 220962 transactions, and creates 177MB of json.

Do you have something I can read as to the db structure and type?

Thanks

[mo35]

Been using Blago`s miner since it apeared, best miner out there, but occasionaly it crashes. I noticed its only happening , when there is new block flood (like miner barely started to read plot and no confirmations received yet , and then new block pops up), btw its not happening always. Still not nice to wake up and see crashed miner. Anyone else experiencing this behaviour and is there any fix for that.

thx

[Blago]

Been using Blago`s miner since it apeared, best miner out there, but occasionaly it crashes. I noticed its only happening , when there is new block flood (like miner barely started to read plot and no confirmations received yet , and then new block pops up), btw its not happening always. Still not nice to wake up and see crashed miner. Anyone else experiencing this behaviour and is there any fix for that.

thx

PM to me your config, screenshot of start miner's window (if not solo-mode), miner version.