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

[uray]

I'm really interested in finding what the relationship is between difficulty and the total size of the burstcoin mining network. As an analogy, the bitcoin mining network knows that they have an approximate hash rate of 200 petahash right now. It would be interesting and useful to know the total number of bytes dedicated to mining BURST. This would allow miners to more accurately predict their earnings, and it would also allow the entire community to know the economic cost of mounting a 51% attack.

I asked the dev about this, and they said:

A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).

A general difficulty -> TB amount could likely be found but I don't know it.

So, this confirms that the difficulty figure is arbitrary, and not directly related to the number of bytes in the network. However, since it self-adjusts for a 4-minute block time, I believe there should be a linear relationship between the average difficulty and the number of bytes in the burstcoin mining network.

Current estimates (based on my own findings and what others have been saying) indicate that 1 TB will mine about 2000 BURST per day. Based on this, the total number of bytes mining burst is approximately 1800 TB, which equals 1.8 x 10^15 bytes.

Currently, the difficulty is 2182485975211560, and the block height is 6246. This makes the average difficulty equal to 3.49 x 10^11.

Based on these figures, and the assumption that there is a linear relationship between average difficulty and total bytes mining, the formula for figuring out the total number of bytes mining is:

Code:

(cumulative_difficulty / block_height) * 5151 = number of bytes on the burstcoin mining network

Using this formula with current figures, we get a network size of 2182485975211560 / 6246 * 5151  = 1.8 x 10^15 bytes.

I'd love to work to improve on this formula! Any feedback is welcome.

you can see detailed block info at http://burst.cryptoport.io



on block 6250, Base Target = 16086365

if burst scaling factor is equal to Nxt Base target,
then we assume that this number is the scaling factor dev said,
and its look correct because overtime this number is reducing

based on dev said difficulty calculation is 2^64/scaling_factor
so on block 6250,

difficulty is 2^64/16086365 = 1.1467317 x 10^12
this number is total nonce required to solve a block
since 1 nonce is equal to 256KB = 0.25 MB
we can convert this nonce count into MB by

1.1467317 x 10^12 x 0.25 = 286,682,915,527 MB
= 279963784.7 GB
= 273402.1 TB

so it need 266 Peta Bytes to solve every block, that is your plot always resulting deadline of < 1 seconds
since blocktime is adjusted to 240 secs, minimal data required is
273402.1 TB / 240 = 1139 TB

assuming we have 1 TB, your chance to found a block is one every 1139 blocks
which is equal to 1139 x 240 = 273360 seconds
= 3.16 days

conclusion :
 you will get 1 block every 3 days on 1 TB plots

i dont know if my calculations are correct, but its close, i have 15 TB, and the average i found a block is close to 0.33 block / days / TB

[CryptoSurfer]

I'm really interested in finding what the relationship is between difficulty and the total size of the burstcoin mining network. As an analogy, the bitcoin mining network knows that they have an approximate hash rate of 200 petahash right now. It would be interesting and useful to know the total number of bytes dedicated to mining BURST. This would allow miners to more accurately predict their earnings, and it would also allow the entire community to know the economic cost of mounting a 51% attack.

I asked the dev about this, and they said:

A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).

A general difficulty -> TB amount could likely be found but I don't know it.

So, this confirms that the difficulty figure is arbitrary, and not directly related to the number of bytes in the network. However, since it self-adjusts for a 4-minute block time, I believe there should be a linear relationship between the average difficulty and the number of bytes in the burstcoin mining network.

Current estimates (based on my own findings and what others have been saying) indicate that 1 TB will mine about 2000 BURST per day. Based on this, the total number of bytes mining burst is approximately 1800 TB, which equals 1.8 x 10^15 bytes.

Currently, the difficulty is 2182485975211560, and the block height is 6246. This makes the average difficulty equal to 3.49 x 10^11.

Based on these figures, and the assumption that there is a linear relationship between average difficulty and total bytes mining, the formula for figuring out the total number of bytes mining is:

Code:

(cumulative_difficulty / block_height) * 5151 = number of bytes on the burstcoin mining network

Using this formula with current figures, we get a network size of 2182485975211560 / 6246 * 5151  = 1.8 x 10^15 bytes.

I'd love to work to improve on this formula! Any feedback is welcome.

you can see detailed block info at http://burst.cryptoport.io



on block 6250, Base Target = 16086365

if burst scaling factor is equal to Nxt Base target,
then we assume that this number is the scaling factor dev said,
and its look correct because overtime this number is reducing

based on dev said difficulty calculation is 2^64/scaling_factor
so on block 6250,

difficulty is 2^64/16086365 = 1.1467317 x 10^12
this number is total nonce required to solve a block
since 1 nonce is equal to 256KB = 0.25 MB
we can convert this nonce count into MB by

1.1467317 x 10^12 x 0.25 = 286,682,915,527 MB
= 279963784.7 GB
= 273402.1 TB

so it need 266 Peta Bytes to solve every block, that is your plot always resulting deadline of < 1 seconds
since blocktime is adjusted to 240 secs, minimal data required is
273402.1 TB / 240 = 1139 TB

assuming we have 1 TB, your chance to found a block is one every 1139 blocks
which is equal to 1139 x 240 = 273360 seconds
= 3.16 days

conclusion :
 you will get 1 block every 3 days on 1 TB plots

Nice explanation! Is it possible to show the amount of TB used real-time (refreshes every block) ?

[uray]

I'm really interested in finding what the relationship is between difficulty and the total size of the burstcoin mining network. As an analogy, the bitcoin mining network knows that they have an approximate hash rate of 200 petahash right now. It would be interesting and useful to know the total number of bytes dedicated to mining BURST. This would allow miners to more accurately predict their earnings, and it would also allow the entire community to know the economic cost of mounting a 51% attack.

I asked the dev about this, and they said:

A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).

A general difficulty -> TB amount could likely be found but I don't know it.

So, this confirms that the difficulty figure is arbitrary, and not directly related to the number of bytes in the network. However, since it self-adjusts for a 4-minute block time, I believe there should be a linear relationship between the average difficulty and the number of bytes in the burstcoin mining network.

Current estimates (based on my own findings and what others have been saying) indicate that 1 TB will mine about 2000 BURST per day. Based on this, the total number of bytes mining burst is approximately 1800 TB, which equals 1.8 x 10^15 bytes.

Currently, the difficulty is 2182485975211560, and the block height is 6246. This makes the average difficulty equal to 3.49 x 10^11.

Based on these figures, and the assumption that there is a linear relationship between average difficulty and total bytes mining, the formula for figuring out the total number of bytes mining is:

Code:

(cumulative_difficulty / block_height) * 5151 = number of bytes on the burstcoin mining network

Using this formula with current figures, we get a network size of 2182485975211560 / 6246 * 5151  = 1.8 x 10^15 bytes.

I'd love to work to improve on this formula! Any feedback is welcome.

you can see detailed block info at http://burst.cryptoport.io



on block 6250, Base Target = 16086365

if burst scaling factor is equal to Nxt Base target,
then we assume that this number is the scaling factor dev said,
and its look correct because overtime this number is reducing

based on dev said difficulty calculation is 2^64/scaling_factor
so on block 6250,

difficulty is 2^64/16086365 = 1.1467317 x 10^12
this number is total nonce required to solve a block
since 1 nonce is equal to 256KB = 0.25 MB
we can convert this nonce count into MB by

1.1467317 x 10^12 x 0.25 = 286,682,915,527 MB
= 279963784.7 GB
= 273402.1 TB

so it need 266 Peta Bytes to solve every block, that is your plot always resulting deadline of < 1 seconds
since blocktime is adjusted to 240 secs, minimal data required is
273402.1 TB / 240 = 1139 TB

assuming we have 1 TB, your chance to found a block is one every 1139 blocks
which is equal to 1139 x 240 = 273360 seconds
= 3.16 days

conclusion :
 you will get 1 block every 3 days on 1 TB plots

Nice explanation! Is it possible to show the amount of TB used real-time (refreshes every block) ?

yes its possible,but i need dev confirmation how to correctly calculated it

[CryptoSurfer]

yes its possible,but i need dev confirmation how to correctly calculated it

Haven't seen the Dev around for some time. Must be busy working on the v2 pool.
We should also ask the Dev to update the OP with the features of this tool.
Also i am curious where Wullfcastle is hanging around.

[familiaverde]

We really need that v2 pool ... if we want more ppl to mine this coin .... it is very hard to get 1 block

[uray]

We really need that v2 pool ... if we want more ppl to mine this coin .... it is very hard to get 1 block

to be honest, we need more people buying this coins, instead of mining it  ! LOL LOL
difficulty is gone crazy !

[familiaverde]

We really need that v2 pool ... if we want more ppl to mine this coin .... it is very hard to get 1 block

to be honest, we need more people buying this coins, instead of mining it  ! LOL LOL
difficulty is gone crazy !

Dont worry we will have a lot of people buying this coin after we hit a bigger exchange ... nobody need expensive electricity bills anymore ... we need aother alternative to mine coins and this is the best untill now .

[omgbossis21]

Im going to see what I can do about a gui plotter and miner, something basic if I have time.  We do need more buyers that's for sure but its time will come!  A gui wallet would be nice and shouldn't be to hard using a nxt wallet source probably. 

[burstcoin]

I'm really interested in finding what the relationship is between difficulty and the total size of the burstcoin mining network. As an analogy, the bitcoin mining network knows that they have an approximate hash rate of 200 petahash right now. It would be interesting and useful to know the total number of bytes dedicated to mining BURST. This would allow miners to more accurately predict their earnings, and it would also allow the entire community to know the economic cost of mounting a 51% attack.

I asked the dev about this, and they said:

A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).

A general difficulty -> TB amount could likely be found but I don't know it.

So, this confirms that the difficulty figure is arbitrary, and not directly related to the number of bytes in the network. However, since it self-adjusts for a 4-minute block time, I believe there should be a linear relationship between the average difficulty and the number of bytes in the burstcoin mining network.

Current estimates (based on my own findings and what others have been saying) indicate that 1 TB will mine about 2000 BURST per day. Based on this, the total number of bytes mining burst is approximately 1800 TB, which equals 1.8 x 10^15 bytes.

Currently, the difficulty is 2182485975211560, and the block height is 6246. This makes the average difficulty equal to 3.49 x 10^11.

Based on these figures, and the assumption that there is a linear relationship between average difficulty and total bytes mining, the formula for figuring out the total number of bytes mining is:

Code:

(cumulative_difficulty / block_height) * 5151 = number of bytes on the burstcoin mining network

Using this formula with current figures, we get a network size of 2182485975211560 / 6246 * 5151  = 1.8 x 10^15 bytes.

I'd love to work to improve on this formula! Any feedback is welcome.

you can see detailed block info at http://burst.cryptoport.io



on block 6250, Base Target = 16086365

if burst scaling factor is equal to Nxt Base target,
then we assume that this number is the scaling factor dev said,
and its look correct because overtime this number is reducing

based on dev said difficulty calculation is 2^64/scaling_factor
so on block 6250,

difficulty is 2^64/16086365 = 1.1467317 x 10^12
this number is total nonce required to solve a block
since 1 nonce is equal to 256KB = 0.25 MB
we can convert this nonce count into MB by

1.1467317 x 10^12 x 0.25 = 286,682,915,527 MB
= 279963784.7 GB
= 273402.1 TB

so it need 266 Peta Bytes to solve every block, that is your plot always resulting deadline of < 1 seconds
since blocktime is adjusted to 240 secs, minimal data required is
273402.1 TB / 240 = 1139 TB

assuming we have 1 TB, your chance to found a block is one every 1139 blocks
which is equal to 1139 x 240 = 273360 seconds
= 3.16 days

conclusion :
 you will get 1 block every 3 days on 1 TB plots

Nice explanation! Is it possible to show the amount of TB used real-time (refreshes every block) ?

yes its possible,but i need dev confirmation how to correctly calculated it

This looks probably correct.

yes its possible,but i need dev confirmation how to correctly calculated it

Haven't seen the Dev around for some time. Must be busy working on the v2 pool.
We should also ask the Dev to update the OP with the features of this tool.
Also i am curious where Wullfcastle is hanging around.

v2 is in progress, I also got working a gpu plotter, but it needs a lot more work before it is releasable.

Haven't heard from Wulfcastle in a while

[CryptoSurfer]

I'm really interested in finding what the relationship is between difficulty and the total size of the burstcoin mining network. As an analogy, the bitcoin mining network knows that they have an approximate hash rate of 200 petahash right now. It would be interesting and useful to know the total number of bytes dedicated to mining BURST. This would allow miners to more accurately predict their earnings, and it would also allow the entire community to know the economic cost of mounting a 51% attack.

I asked the dev about this, and they said:

A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).

A general difficulty -> TB amount could likely be found but I don't know it.

So, this confirms that the difficulty figure is arbitrary, and not directly related to the number of bytes in the network. However, since it self-adjusts for a 4-minute block time, I believe there should be a linear relationship between the average difficulty and the number of bytes in the burstcoin mining network.

Current estimates (based on my own findings and what others have been saying) indicate that 1 TB will mine about 2000 BURST per day. Based on this, the total number of bytes mining burst is approximately 1800 TB, which equals 1.8 x 10^15 bytes.

Currently, the difficulty is 2182485975211560, and the block height is 6246. This makes the average difficulty equal to 3.49 x 10^11.

Based on these figures, and the assumption that there is a linear relationship between average difficulty and total bytes mining, the formula for figuring out the total number of bytes mining is:

Code:

(cumulative_difficulty / block_height) * 5151 = number of bytes on the burstcoin mining network

Using this formula with current figures, we get a network size of 2182485975211560 / 6246 * 5151  = 1.8 x 10^15 bytes.

I'd love to work to improve on this formula! Any feedback is welcome.

you can see detailed block info at http://burst.cryptoport.io



on block 6250, Base Target = 16086365

if burst scaling factor is equal to Nxt Base target,
then we assume that this number is the scaling factor dev said,
and its look correct because overtime this number is reducing

based on dev said difficulty calculation is 2^64/scaling_factor
so on block 6250,

difficulty is 2^64/16086365 = 1.1467317 x 10^12
this number is total nonce required to solve a block
since 1 nonce is equal to 256KB = 0.25 MB
we can convert this nonce count into MB by

1.1467317 x 10^12 x 0.25 = 286,682,915,527 MB
= 279963784.7 GB
= 273402.1 TB

so it need 266 Peta Bytes to solve every block, that is your plot always resulting deadline of < 1 seconds
since blocktime is adjusted to 240 secs, minimal data required is
273402.1 TB / 240 = 1139 TB

assuming we have 1 TB, your chance to found a block is one every 1139 blocks
which is equal to 1139 x 240 = 273360 seconds
= 3.16 days

conclusion :
 you will get 1 block every 3 days on 1 TB plots

Nice explanation! Is it possible to show the amount of TB used real-time (refreshes every block) ?

yes its possible,but i need dev confirmation how to correctly calculated it

This looks probably correct.

yes its possible,but i need dev confirmation how to correctly calculated it

Haven't seen the Dev around for some time. Must be busy working on the v2 pool.
We should also ask the Dev to update the OP with the features of this tool.
Also i am curious where Wullfcastle is hanging around.

v2 is in progress, I also got working a gpu plotter, but it needs a lot more work before it is releasable.

Haven't heard from Wulfcastle in a while

Great splendid news.
Dev, thank you very much for your update. We can count on you as always!

[uray]

We really need that v2 pool ... if we want more ppl to mine this coin .... it is very hard to get 1 block

to be honest, we need more people buying this coins, instead of mining it  ! LOL LOL
difficulty is gone crazy !

Dont worry we will have a lot of people buying this coin after we hit a bigger exchange ... nobody need expensive electricity bills anymore ... we need aother alternative to mine coins and this is the best untill now .

well you will still need expensive storage...

but what good about this concept is that, we are striving to find how can mining is affordable to regular peoples, ASIC too expensive, GPU less expensive but running cost is huge, CPU everyone have it but botnet and infected computer can dominate the hashrate

storage : almost all regular people own it, its relatively cheap, running cost is even cheaper, and botnet can't create 1 TB of data on their infected PC, so... this is what closest so far for ideal mining concept

and please dont mention PoS, DPoS or anything related to stake, thats not real mining

[ctenc001]

Incase you missed it.. Check out my review and Dev interview of BURST at CryptoTycoons.com
Follow us on twitter at: twitter.com/cryptotycoons

Very nice, I am reading it now. One thing I noticed right away, it's not 'more plots you have the more hashrate you have' necessarily... It's more space, so either bigger plots, or lots of little plots. But I'm stoked someone wrote another article! I will let you know my full opinion when I am finished. I am also going to follow you. Thanks!

edit: you also forgot to post the link to this ANN page.


also, this sentence, 'o make matters worse, the innovative new algorithm will force the whales who typically do most of the social media pumping to pass by this coin since there expensive mining rigs will be all but useless.'

The word 'there' is incorrect, it should be 'their'.

I would be more than happy to proof-read your articles and edit them for you, if you would like. Let me know! I am a sort of 'grammar nazi' lol.

Thanks for checking it out! I appreciate the feedback=) I'll correct the errors you listed!

[familiaverde]

We really need that v2 pool ... if we want more ppl to mine this coin .... it is very hard to get 1 block

to be honest, we need more people buying this coins, instead of mining it  ! LOL LOL
difficulty is gone crazy !

Dont worry we will have a lot of people buying this coin after we hit a bigger exchange ... nobody need expensive electricity bills anymore ... we need aother alternative to mine coins and this is the best untill now .

well you will still need expensive storage...

but what good about this concept is that, we are striving to find how can mining is affordable to regular peoples, ASIC too expensive, GPU less expensive but running cost is huge, CPU everyone have it but botnet and infected computer can dominate the hashrate

storage : almost all regular people own it, its relatively cheap, running cost is even cheaper, and botnet can't create 1 TB of data on their infected PC, so... this is what closest so far for ideal mining concept

and please dont mention PoS, DPoS or anything related to stake, thats not real mining

This is my opinion too ... it will be bigger if we will use this space for someting ... now we only keep hdd full with plots ...

[AnonymousEconomist]

I like the idea that you can't use the space. It makes it more valuable. That means you need to buy HDD space specifically for mining BURST, thus raising the value.

Can we get a multipool bounty going please?

I pledge 5k BURST. This will up the buying pressure and bring attention.

[crowetic]

I like the idea that you can't use the space. It makes it more valuable. That means you need to buy HDD space specifically for mining BURST, thus raising the value.

Can we get a multipool bounty going please?

I pledge 5k BURST. This will up the buying pressure and bring attention.

At first I liked the idea of being able to use the space, but currently my thought process is more in line with yours. I also believe it's more valuable when you buy hardware specifically for it.

[AnonymousEconomist]

The unique thing about a multipool for BURST, would be that it would consistently up the profitability for mining on the HDD, thus increasing the difficulty, which of course, raises the price. A circle of price increases. First of it's kind, too.

I think I'll hold for years if a multi pool comes out now.

[Vorksholk]

I'll pitch in 25k burst for a multipool.

[jzhoulon]

I like the idea that you can't use the space. It makes it more valuable. That means you need to buy HDD space specifically for mining BURST, thus raising the value.

Can we get a multipool bounty going please?

I pledge 5k BURST. This will up the buying pressure and bring attention.

At first I liked the idea of being able to use the space, but currently my thought process is more in line with yours. I also believe it's more valuable when you buy hardware specifically for it.

no, if the mining needs specific hardware, this difficulty will be low for those who owns specific hardware and high for those who haven't , that is , this coin can be mined easily by those who owns hardware but not for those who haven't, then who have no hardware must by the coin if they want, but those own the hardware still can easily mine the coin, but hdd, every one has, increase one miner, difficulty increase, this will really increase the difficulty and cost, when every one can mine little, then when the burst's value increase, none have the ability to dump it , but for those which need hardware, the owner still can easily dump the coin

[MOB]

Sorry for yet another question, but with my 8x3TB drives that are not in JBOD or RAID0 but just singles, how do I get all of them to mine?  Do I run multiple mining instances?

[AnonymousEconomist]

I'll pitch in 25k burst for a multipool.

Oh nice that's what I'm talking about!

So we are up to 30k for the multipool