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

[bobafett]

Im the owner i only wrote that i would sell it if somebody makes me a good offer. Pool was short down because of a unexpectet error of the task. Now up again.

[Cobra98]

Im the owner i only wrote that i would sell it if somebody makes me a good offer. Pool was short down because of a unexpectet error of the task. Now up again.

Shit lol, just started mining another pool. Yours is still the best with most consistent payouts, back to your pool!

[kahir]

This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 30th unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.

[Elmit]

This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 30th unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.

But we were always told that we should HOLD the coins, ....

[DooMAD]

This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 30th unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.

Which exchange?  I'm guessing it's not Polo, as that's had BTC0.22486507 in the last 24 hours.

[okae]

This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 30th unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.

Which exchange?  I'm guessing it's not Polo, as that's had BTC0.22486507 in the last 24 hours.

the exchange that are going to de-listing burst is bittrex, you are free to check it here -> https://bittrex.com/Market/Index?MarketName=BTC-
BURST

btw if you are going to buy/sell burst there is others exchanges as you can see at the OP, polo for example.

[Blago]

This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 30th unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.

Which exchange?  I'm guessing it's not Polo, as that's had BTC0.22486507 in the last 24 hours.

C-CEX.com @CryptoCurrEncyX
Delisting list is being corrected all the time. If You don't see delisting red flag on coin - this coin will not be delisted.

[jwinterm]

This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 30th unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.

Which exchange?  I'm guessing it's not Polo, as that's had BTC0.22486507 in the last 24 hours.

C-CEX.com @CryptoCurrEncyX
Delisting list is being corrected all the time. If You don't see delisting red flag on coin - this coin will not be delisted.

https://bittrex.com/Market/Index?MarketName=BTC-BURST

[haitch]

This market is in danger of de-listing due to low trade volume and lack of user interest. It may be removed on October 30th unless the average daily trade volume for the last 7 days exceeds 0.2 BTC.

Which exchange?  I'm guessing it's not Polo, as that's had BTC0.22486507 in the last 24 hours.

C-CEX.com @CryptoCurrEncyX
Delisting list is being corrected all the time. If You don't see delisting red flag on coin - this coin will not be delisted.

https://bittrex.com/Market/Index?MarketName=BTC-BURST

The C-CEX delisting was avoided. The Bitrex delisting will also be avoided.

H.

[haitch]

Im the owner i only wrote that i would sell it if somebody makes me a good offer. Pool was short down because of a unexpectet error of the task. Now up again.

Shit lol, just started mining another pool. Yours is still the best with most consistent payouts, back to your pool!

Guess you haven't mined on ninja then .....

H.

[hendo420]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

[haitch]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

[ivanf]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

As I recall, by tweaking the plotter it's possible to store data for one block per file, creating a set of 4096 files and only reading one of them on each block. So, the required bandwidth can be 4096 times smaller.

[haitch]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

As I recall, by tweaking the plotter it's possible to store data for one block per file, creating a set of 4096 files and only reading one of them on each block. So, the required bandwidth can be 4096 times smaller.

So, instead of reading 9,142,272 nonces from one single, optimized file (and that's one of 50), I should read one nonce from each of 9,142,272 individual files? I somehow don't see that being more efficient ....

[ivanf]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

As I recall, by tweaking the plotter it's possible to store data for one block per file, creating a set of 4096 files and only reading one of them on each block. So, the required bandwidth can be 4096 times smaller.

So, instead of reading 9,142,272 nonces from one single, optimized file (and that's one of 50), I should read one nonce from each of 9,142,272 individual files? I somehow don't see that being more efficient ....

Create a plot [256 kb] -> store plot[0] to plots0.dat, store plot[1] to plots1.dat etc for each 4096 scoops.
Create a plot [256 kb] -> append plot[0] to plots0.dat, append plot[1] to plots1.dat etc
Create a plot [256 kb] -> append plot[0] to plots0.dat, append plot[1] to plots1.dat etc etc

This way there will be 4096 large files (plot0.dat ... plot4095.dat) which can be uploaded to the cloud. You decide how large these files will be, of course they can be split if necessary. They also will be badly fragmented when stored on HDD, but this doesn't matter because they will be uploaded one by one to the cloud anyway.

When mining block 1323, simply fetch scoops from plot1323.dat and so on. 4096 times less bandwidth because unneeded scoops won't be downloaded.

p.s. In normal mining mode only ONE scoop from 4096 scoops in each plot is used. It's inefficient but it was done this way because reading speed is not the bottleneck when using local HDDs and it allows avoiding fragmentation when plotting (leading to faster plotting as there's no defrag step).

[Irontiga]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

As I recall, by tweaking the plotter it's possible to store data for one block per file, creating a set of 4096 files and only reading one of them on each block. So, the required bandwidth can be 4096 times smaller.

So, instead of reading 9,142,272 nonces from one single, optimized file (and that's one of 50), I should read one nonce from each of 9,142,272 individual files? I somehow don't see that being more efficient ....

Create a plot [256 kb] -> store plot[0] to plots0.dat, store plot[1] to plots1.dat etc for each 4096 scoops.
Create a plot [256 kb] -> append plot[0] to plots0.dat, append plot[1] to plots1.dat etc
Create a plot [256 kb] -> append plot[0] to plots0.dat, append plot[1] to plots1.dat etc etc

This way there will be 4096 large files (plot0.dat ... plot4095.dat) which can be uploaded to the cloud. You decide how large these files will be, of course they can be split if necessary. They also will be badly fragmented when stored on HDD, but this doesn't matter because they will be uploaded one by one to the cloud anyway.

When mining block 1323, simply fetch scoops from plot1323.dat and so on. 4096 times less bandwidth because unneeded scoops won't be downloaded.

p.s. In normal mining mode only ONE scoop from 4096 scoops in each plot is used. It's inefficient but it was done this way because reading speed is not the bottleneck when using local HDDs and it allows avoiding fragmentation when plotting (leading to faster plotting as there's no defrag step).

You're right....ish.

By only plotting 1 scoop you would have to read 1pb in one block per 4096...

You can easily mine on aws using ec2 computing.

[hendo420]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

I can see getting this speed and then some out of a vps with a 10gbps connection. Amazon Cloud Drive does throttle uploads, but I don't think they throttle downloads. So reading whats on the amazon cloud drive would be nearly as fast as a physical hard drive with the right setup... in theory.

[haitch]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

As I recall, by tweaking the plotter it's possible to store data for one block per file, creating a set of 4096 files and only reading one of them on each block. So, the required bandwidth can be 4096 times smaller.

So, instead of reading 9,142,272 nonces from one single, optimized file (and that's one of 50), I should read one nonce from each of 9,142,272 individual files? I somehow don't see that being more efficient ....

Create a plot [256 kb] -> store plot[0] to plots0.dat, store plot[1] to plots1.dat etc for each 4096 scoops.
Create a plot [256 kb] -> append plot[0] to plots0.dat, append plot[1] to plots1.dat etc
Create a plot [256 kb] -> append plot[0] to plots0.dat, append plot[1] to plots1.dat etc etc

This way there will be 4096 large files (plot0.dat ... plot4095.dat) which can be uploaded to the cloud. You decide how large these files will be, of course they can be split if necessary. They also will be badly fragmented when stored on HDD, but this doesn't matter because they will be uploaded one by one to the cloud anyway.

When mining block 1323, simply fetch scoops from plot1323.dat and so on. 4096 times less bandwidth because unneeded scoops won't be downloaded.

p.s. In normal mining mode only ONE scoop from 4096 scoops in each plot is used. It's inefficient but it was done this way because reading speed is not the bottleneck when using local HDDs and it allows avoiding fragmentation when plotting (leading to faster plotting as there's no defrag step).

Or in my case - open plot file, seek to 1323 * 9,142,272 nonces from start, read next 9,142,272 nonces (which are all consecutive as it was written directly to the file). No difference in bandwidth, and certainly not 4096 times less bandwidth.

[haitch]

I can mount amazon cloud drive as a physical drive, which reads as somewhere around 1PB of storage, can I use this to mine this coin?

Theoretically yes, but your bandwidth to the cloud is going to be a limiting factor.

To get my plots to mine in an acceptable time window, I'm looking at 250-300+ MB/sec.

H.

I can see getting this speed and then some out of a vps with a 10gbps connection. Amazon Cloud Drive does throttle uploads, but I don't think they throttle downloads. So reading whats on the amazon cloud drive would be nearly as fast as a physical hard drive with the right setup... in theory.

In theory - if your miner has access to all that bandwidth. If you mine in the cloud it's possible, if you mine locally - highly improbable.

[Cobra98]

Im the owner i only wrote that i would sell it if somebody makes me a good offer. Pool was short down because of a unexpectet error of the task. Now up again.

Shit lol, just started mining another pool. Yours is still the best with most consistent payouts, back to your pool!

Guess you haven't mined on ninja then .....

H.

Is ninja a better pool?