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

[Vorksholk]

Due to the increase in difficulty, now renting out TBs of mining power for 0.045BTC per TB for the first month (generation fee), then 0.0225BTC per TB per month thereafter. Solo or pool mining.

Just got an order for 20TB, so any other orders will be waiting a few days.

20tb?

Crazy.

I was thinking burst was probably a fad but its looking more and more like real investors are coming in.

What did he/she pay for that?

0.90BTC for a month once the plots finish generating.

Crazy. I wonder if that will produce more than just buying them from market today.

This is getting interesting.

Very interesting indeed. Right now, 0.9BTC would get around 500,000 BURST at the exchanges, give or take 50k. At current difficulty, 20TB would certainly generate >500k BURST in a month, but there's no way the current difficulty is sticking for any period of time. Personally, I think mining will be a marginally better return, but that's napkin speculation.

[neite99]

Due to the increase in difficulty, now renting out TBs of mining power for 0.045BTC per TB for the first month (generation fee), then 0.0225BTC per TB per month thereafter. Solo or pool mining.

Just got an order for 20TB, so any other orders will be waiting a few days.

20tb?

Crazy.

I was thinking burst was probably a fad but its looking more and more like real investors are coming in.

What did he/she pay for that?

0.90BTC for a month once the plots finish generating.

Crazy. I wonder if that will produce more than just buying them from market today.

This is getting interesting.

Very interesting indeed. Right now, 0.9BTC would get around 500,000 BURST at the exchanges, give or take 50k. At current difficulty, 20TB would certainly generate >500k BURST in a month, but there's no way the current difficulty is sticking for any period of time. Personally, I think mining will be a marginally better return, but that's napkin speculation.

I think it depends on a lot of things. The sooner the better though. A 5% monthly reward drop doesn't sound like much but after a few months and an increased difficulty it will feel a whole lot more like a roadblock.

Hope you can get them their plots really fast. Whoever it is deserves a good chance.

[Vorksholk]

Due to the increase in difficulty, now renting out TBs of mining power for 0.045BTC per TB for the first month (generation fee), then 0.0225BTC per TB per month thereafter. Solo or pool mining.

Just got an order for 20TB, so any other orders will be waiting a few days.

20tb?

Crazy.

I was thinking burst was probably a fad but its looking more and more like real investors are coming in.

What did he/she pay for that?

0.90BTC for a month once the plots finish generating.

Crazy. I wonder if that will produce more than just buying them from market today.

This is getting interesting.

Very interesting indeed. Right now, 0.9BTC would get around 500,000 BURST at the exchanges, give or take 50k. At current difficulty, 20TB would certainly generate >500k BURST in a month, but there's no way the current difficulty is sticking for any period of time. Personally, I think mining will be a marginally better return, but that's napkin speculation.

I think it depends on a lot of things. The sooner the better though. A 5% monthly reward drop doesn't sound like much but after a few months and an increased difficulty it will feel a whole lot more like a roadblock.

Hope you can get them their plots really fast. Whoever it is deserves a good chance.

Oh for sure, 4-5 days to generate, and plots are mining while they are being generated. It'll be interesting to see what 5% reward deduction does to the market prices, too.

[Sglasio]

I like to announce:

The Plot-generator rewritten in C!

It has several advantages over the one written in Java:
- About twice as fast
- Support for larger stagger sizes, only limited by system memory
- More efficient memory handling. With just 3GB you can use Stagger size 8191, with 8GB 24000 is possible. Plots with larger stagger sizes are better, as they require less disk seeks to be read.

You need a 64bit Linux environment to run this. Maybe someone can port it to Windows?

How to run it:
Download, unpack (tar -xzf plotgenerator.tgz), compile (make)

Then use the same command line options as with the Java-generator:

Code:

./plot <key> <starting nonce> <nonces> <stagger size> <threads>

You can download it here:
https://bchain.info/plotgenerator.tgz

Anyone have any luck compiling this for Windows? It runs fine in Linux after compiling.

I used the this in terminal in Linux after I compiled it: "x86_64-w64-mingw32-gcc plot -o plot.exe"

Then I try to run it on Windows and can not run. I think I am suppose to use "x86_64-w64-mingw32-g++ plot -o plot.exe"

My skills are novice in compiling, so any help is greatly appreciated. Once I can get this running, I'll share a link to download it for Windows users.

where is a link ? _)

[SpeedDemon13]

I like to announce:

The Plot-generator rewritten in C!

It has several advantages over the one written in Java:
- About twice as fast
- Support for larger stagger sizes, only limited by system memory
- More efficient memory handling. With just 3GB you can use Stagger size 8191, with 8GB 24000 is possible. Plots with larger stagger sizes are better, as they require less disk seeks to be read.

You need a 64bit Linux environment to run this. Maybe someone can port it to Windows?

How to run it:
Download, unpack (tar -xzf plotgenerator.tgz), compile (make)

Then use the same command line options as with the Java-generator:

Code:

./plot <key> <starting nonce> <nonces> <stagger size> <threads>

You can download it here:
https://bchain.info/plotgenerator.tgz

Anyone have any luck compiling this for Windows? It runs fine in Linux after compiling.

I used the this in terminal in Linux after I compiled it: "x86_64-w64-mingw32-gcc plot -o plot.exe"

Then I try to run it on Windows and can not run. I think I am suppose to use "x86_64-w64-mingw32-g++ plot -o plot.exe"

My skills are novice in compiling, so any help is greatly appreciated. Once I can get this running, I'll share a link to download it for Windows users.

where is a link ? _)

I'm still trying to work on it, but remember my coding skills is novice at best. I can not make any promises if I even get it to run.

[tibolt]

any news about pool v2?

[burstcoin]

New update 1.0.3 update by block 6500
Download: https://mega.co.nz/#!G0YS1CKA!car3sW6XULkl0FyOngbyidoKnzEiBsNx5v7SJj4Byo4
sha256: 22cdc6cda9530cfbc75eaf68932fe82228b740910eefc085732aac784d433a09
or grab it from githib

Move your burst_db folder from the old client to the new one to avoid re-downloading the blockchain.

This adds the protocol update needed for v2 pools, and goes into effect on on block 6500. Usage is not yet integrated into the gui, so expect another update for that, but it won't be mandatory to stay in sync like this one is.

[jamoes]

New update 1.0.3 update by block 6500
Download: https://mega.co.nz/#!G0YS1CKA!car3sW6XULkl0FyOngbyidoKnzEiBsNx5v7SJj4Byo4
sha256: 22cdc6cda9530cfbc75eaf68932fe82228b740910eefc085732aac784d433a09
or grab it from githib

Move your burst_db folder from the old client to the new one to avoid re-downloading the blockchain.

This adds the protocol update needed for v2 pools, and goes into effect on on block 6500. Usage is not yet integrated into the gui, so expect another update for that, but it won't be mandatory to stay in sync like this one is.

Great news! I'm really excited about this coin.

Can you clarify how the difficulty figure relates to the total size of all miner's plots? Is it equal to the total number of bytes across all miner's plots, or is there another formula? Thanks!

[burstcoin]

New update 1.0.3 update by block 6500
Download: https://mega.co.nz/#!G0YS1CKA!car3sW6XULkl0FyOngbyidoKnzEiBsNx5v7SJj4Byo4
sha256: 22cdc6cda9530cfbc75eaf68932fe82228b740910eefc085732aac784d433a09
or grab it from githib

Move your burst_db folder from the old client to the new one to avoid re-downloading the blockchain.

This adds the protocol update needed for v2 pools, and goes into effect on on block 6500. Usage is not yet integrated into the gui, so expect another update for that, but it won't be mandatory to stay in sync like this one is.

Great news! I'm really excited about this coin.

Can you clarify how the difficulty figure relates to the total size of all miner's plots? Is it equal to the total number of bytes across all miner's plots, or is there another formula? Thanks!

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.

[omgbossis21]

just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

[theblazehen]

just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?

[dcct]

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.

Just as a suggestion: Now we have to calculate the results as quick as possible as some deadlines are just a few seconds.

Why don't we just add some seconds to the deadline, just to give everyone enough time to finish processing?

And some blocks take too long. We can just add some math to reduce them!

Code:

Say: Actual deadline = (calculated_deadline ^ 0.8) + 120

10s => 126s
100s => 160s
240s => 200s
300s => 215s
1000s => 371s
3600s => 820s

This way we average at around 240s again, have some extra time for slow HDD/CPU's and avoid extra long block solving times.

If you like it I can do the math to get exactly back to 240s average.

[Depredation]

I can't seem to pool mine, is that intentional for now?
I have updated to 1.0.3 but it says can't get mining info from wallet.

[omgbossis21]

Yeah on the pool, glad its not just me!

[burstcoin]

just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?

Pool is down at the moment. I took it down to update the wallet, and it's not loading the current state correctly. If I can't figure it out in a few more minutes I'm just going to load it back up as-is and we'll have one screwed up payout on its next block and it should be fine after that.

EDIT: brought the pool back up, not worth the downtime. for some reason it didn't pick up on what its last block was, and loaded all shares submitted instead of just the current ones, so payout will be wrong once, then should be normal.

[mamamae]

can be done with AWS on amazon
free for some gb and some hd space ?

[SpeedDemon13]

just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?

Pool is down at the moment. I took it down to update the wallet, and it's not loading the current state correctly. If I can't figure it out in a few more minutes I'm just going to load it back up as-is and we'll have one screwed up payout on its next block and it should be fine after that.

EDIT: brought the pool back up, not worth the downtime. for some reason it didn't pick up on what its last block was, and loaded all shares submitted instead of just the current ones, so payout will be wrong once, then should be normal.

You should take it down if you need to prepare it. Think the community wouldn't mind.

[dcct]

can be done with AWS on amazon
free for some gb and some hd space ?

It can, but AWS is expensive.

[shlsumy]

I like to announce:

The Plot-generator rewritten in C!

It has several advantages over the one written in Java:
- About twice as fast
- Support for larger stagger sizes, only limited by system memory
- More efficient memory handling. With just 3GB you can use Stagger size 8191, with 8GB 24000 is possible. Plots with larger stagger sizes are better, as they require less disk seeks to be read.

You need a 64bit Linux environment to run this. Maybe someone can port it to Windows?

How to run it:
Download, unpack (tar -xzf plotgenerator.tgz), compile (make)

Then use the same command line options as with the Java-generator:

Code:

./plot <key> <starting nonce> <nonces> <stagger size> <threads>

You can download it here:
https://bchain.info/plotgenerator.tgz

Anyone have any luck compiling this for Windows? It runs fine in Linux after compiling.

I used the this in terminal in Linux after I compiled it: "x86_64-w64-mingw32-gcc plot -o plot.exe"

Then I try to run it on Windows and can not run. I think I am suppose to use "x86_64-w64-mingw32-g++ plot -o plot.exe"

My skills are novice in compiling, so any help is greatly appreciated. Once I can get this running, I'll share a link to download it for Windows users.

where is a link ? _)

I'm still trying to work on it, but remember my coding skills is novice at best. I can not make any promises if I even get it to run.

using 2047 MB memory

i have 32 GB RAM
how i can make more memory for plotting?

[burstcoin]

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.

Just as a suggestion: Now we have to calculate the results as quick as possible as some deadlines are just a few seconds.

Why don't we just add some seconds to the deadline, just to give everyone enough time to finish processing?

And some blocks take too long. We can just add some math to reduce them!

Code:

Say: Actual deadline = (calculated_deadline ^ 0.8) + 120

10s => 126s
100s => 160s
240s => 200s
300s => 215s
1000s => 371s
3600s => 820s

This way we average at around 240s again, have some extra time for slow HDD/CPU's and avoid extra long block solving times.

If you like it I can do the math to get exactly back to 240s average.

I thought of this also, however I never got around to examining it in depth for potential repercussions. It might be possible that a function like that could open it up to sub 51% attacks. One potential attack vector that comes to mind is if an attacker mined their own chain with timestamps intentionally boosting the difficulty, then they would be avoiding the +120 seconds more, and would have the *0.8 reduction apply to more of their total deadline each time. This might allow them to build up the cumulative difficulty faster than they should be able to with that amount of TB.