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

[bobafett]

yes i also think so. got 3 miner, all win 8 and one has it every 5 days, the other 2 never had it until now.

[1714046038]

1714046038

[1714046038]

1714046038

[1714046038]

1714046038

[1714046038]

1714046038

[FakeAccount]

yes i also think so. got 3 miner, all win 8 and one has it every 5 days, the other 2 never had it until now.

if everything is the same, then maybe it's now trying to execute some code it hasn't tried/needed to run before.
some variable changed in size?  i'm just thinking out loud here.

[Razerglass]

ninja pool updated to v1.2.3
historic pie rendering fixed (data was okay, just stats page was wrong)

BONUS PAYMENT CODE coming very soon (yum yum)

nice work catbref

[skymax]

mmmhh... burst at 0.00000122   TIME TO BUYYY    

[callmejack]

yes i also think so. got 3 miner, all win 8 and one has it every 5 days, the other 2 never had it until now.

if everything is the same, then maybe it's now trying to execute some code it hasn't tried/needed to run before.
some variable changed in size?  i'm just thinking out loud here.

for me the error message sounds like a wrong index somewhere in the code.
maybe the cache filling thread doesn't get reset correctly on block change if the sata port or network times out and freezes the whole machine.
there may be included libraries which tend to crash the program if threads get simply terminated and not shutdown.
on average situations this works but if there are long response times somewhere (disk or network) the regular situation changes and a counter wont be reset (multithreading can be evil).

personally i have not reviewed the code to give a hint where to look for.
simply switch your rigs to linux using the dcct or java miner.
both combinations run totally unattended (except the wallet updates) without any of the windows related issues since month for me
even the  last wallet update did not crash a single running miner instance.

what is special with the blago miner?
how many tb can be parsed per core per minute on a current average i7 cpu?
is it only useful for windows based mining?

[mmmaybe]

mmmhh... burst at 0.00000122   TIME TO BUYYY    

Yup, 1,5mil to add to the good old pile Loving it. Just want more BTC hehe

[katlogic]

it seems that burst didn't be updated for more than 2.5month, and the dev seems disapear for a long time, i am wondering whether the dev is still developing this coin? i have asked the same question one month ago, it seems lots of people said the the new update will come soon, but i didn't see any updates from the top of the thread now?

also poc2 is developed and will be implementet parallel with poc. so you can mine with you gpu AND with your hdd. with poc2 you need no so much hdd space as with normal poc. that will bring the coin to much more people who has their gpu mining rigs allready at home.

atm we all wait for the world first acct that will be done, if qora is ready this month.

hmm...I'm not sure if GPU mining is such a good idea. It was always about low power usage when mining this coin. And now we should throw away one of the main advantages?
PoC was a revolutionary approach with all those GPU/ASIC coins..

POC2 will not really allow GPU mining much more than POC

Basically the idea is that if miners hack it, they can store only partial proofs on your hard drive and use their GPU to try to figure out in real time what those missing bits should be.  However, realistically it doesn't make sense given that it is still much more cost and energy efficient to spend that money on an extra hard drive rather than a GPU.


Anyway, people are getting impatient.. but trust me, big things are happening in the background.  That being said.. please dump more coins!  I'm trying to make an effort to attract more developers and people who might have some venture capital for us and I'm sure they'd prefer to buy in cheaper!!  Not that I'm having much luck yet.. but you know.  Plus I told myself I wasn't allowed to buy any more Burst.. but at these prices, I splurged.. really hoping I don't regret it in the long run, though I really just don't see any way that Burst doesn't beat BTC some day.

And after some very through analysis of POC vs POS and POW.. POC has a lot more potential than most people realize.

See https://bitcointalk.org/index.php?topic=731923.msg10292524#msg10292524

Using single sha256 for nonce as a reference, the ballpark for conventional hardware of this TMTO is 25/75 pow/poc (bruteforce 8 bits of each 32bit nonce during a readout - assuming a disk can read 10Mnonce/s a second (*4 byte = 40Mbyte/s), that translates to 2560M nonce/s for top of the line GPU. The shorter the nonces are, the easier the PoW part is.

With dedicated hardware, 50/50 or more in favour of PoW.

As for your energy argument - if you have 1PB cluster eating 1kW and with a tiny (compared to HDDs) investment for PoW "booster" you have effectively 2PB cluster eating 2kW ... guess what most miners will opt for. Big appeal of current PoC is that most of capital investment is the equipment, not energy. POC2 as it is will drastically shift it towards conventional PoW.

On the upside - this can effectively get rid of NaS.

Fixing POW2 involves making the nonces large enough (at least 64 bit) so PoW becomes impractical for all intents and purposes.

[dcct]

See https://bitcointalk.org/index.php?topic=731923.msg10292524#msg10292524

Using single sha256 for nonce as a reference, the ballpark for conventional hardware of this TMTO is 25/75 pow/poc (bruteforce 8 bits of each 32bit nonce during a readout - assuming a disk can read 10Mnonce/s a second (*4 byte = 40Mbyte/s), that translates to 2560M nonce/s for top of the line GPU. The shorter the nonces are, the easier the PoW part is.

With dedicated hardware, 50/50 or more in favour of PoW.

As for your energy argument - if you have 1PB cluster eating 1kW and with a tiny (compared to HDDs) investment for PoW "booster" you have effectively 2PB cluster eating 2kW ... guess what most miners will opt for. Big appeal of current PoC is that most of capital investment is the equipment, not energy. POC2 as it is will drastically shift it towards conventional PoW.

On the upside - this can effectively get rid of NaS.

Fixing POW2 involves making the nonces large enough (at least 64 bit) so PoW becomes impractical for all intents and purposes.

Currently each scoop is 64 bytes - or 512 bits - long. Lets assume you brute force 16 bits of each, thats 65536 hashes per nonce the gpu needs to do - leaving 496 bits to store. You´d be able to store 3% more nonces, at the cost of massive CPU/GPU load.
The long scoop length is an effective protection against this "hack", I hope its not going to be changed drastically with poc2.

In my opinion the number of scoops should be increased (to 16 * 4096 maybe), the scoop size reduced to 32 bytes - that would total in 2MB of disk space per nonce and 16MB/TB to be read each block, at a VERY LOW cpu load. Energy efficiency is the main selling point of BURST, don´t give up on that.

5. High blocktime variance
Due to the high amount of diskspace used per nonce, the total amount of nonces checked per block is very low compared to PoW coins. This leads to higher variance in block times.

In my opinion this is not the reason for higher block time variance. Coins with "slow" pow-algorithms like scrypt-jane don´t have this problem either.

In fact, basetarget may be adjusting too fast.

[timk225]

You're all idiots for wasting your time and money on this shitcoin that will never amount to anything.

[dystopian]

You're all idiots for wasting your time and money on this shitcoin that will never amount to anything.

You're a serious troll dude 

[coinits]

You're all idiots for wasting your time and money on this shitcoin that will never amount to anything.

You're a serious troll dude 

He dips his pathetic self into a lot of threads and is always full of hate. The guy is a self-professed thief. He does computer repairs and troubleshooting and is always looking for bitcoin wallets to steal.

[lmaonade80]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

[sellbuy]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 has problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

[lmaonade80]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 have problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Hey, so if I set the IO load to idle, then it would help? I'm trying it now. I'm confused by your wording which stated no go on Win7, but try this? Thanks

[haitch]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 has problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Memory doesn't really help - the miner itself uses very little memory, it's windows trying to be "helpful" and cache the data from the drives that sucks up the ram, enable the "cleanmem" setting and all memory will be retruned after the mining process. Add more memory and windows will just suck up more, until you force it to be released.

The problem issue you can run into, especially when mining multiple drives, is that you max out the CPU. Blagos miner will use one core/thread per drive/directory you specify. If you're mining with more drives than you have threads, your CPU will be maxed out. To get around this you can adjust the CPU affinity to leave some of the cores untouched by the miner - generally I allow the miner to use all but one thread. You can either do it manually by going into task manager -> processes, right clicking miner.exe, select Set Affinity, and unselect CPU 0. If you're launching it from a batch file, you can set the affinity in the batch file.

To do it via the batch file, do:  start "Burst Miner" /wait /affinity <affinity_mask> miner

The affinity mask is a hex representation of a binary value of your cpus. eg, if you have four threads, the binary mask is XXXX, where X is 0 or 1 - 0 means don't use that CPU, 1 means use it. So on a 4 thread CPU, to disable CPU0 for miner, the binary vale would be 1110, which is 0xE. So the command would be:

start "Burst Miner" /wait /affinity 0xD miner

For a 8 thread CPU, it'd be 1111 1110, => 0xFE, so start "Burst Miner" /wait /affinity 0x0FE miner

To leave two threads available:

start "Burst Miner" /wait /affinity 0xFD miner

Windows calc.exe has a programmers mode that can do the binary -> hex conversions for the hexidecimally challenged ;-)

H.

[lmaonade80]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 has problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Memory doesn't really help - the miner itself uses very little memory, it's windows trying to be "helpful" and cache the data from the drives that sucks up the ram, enable the "cleanmem" setting and all memory will be retruned after the mining process. Add more memory and windows will just suck up more, until you force it to be released.

The problem issue you can run into, especially when mining multiple drives, is that you max out the CPU. Blagos miner will use one core/thread per drive/directory you specify. If you're mining with more drives than you have threads, your CPU will be maxed out. To get around this you can adjust the CPU affinity to leave some of the cores untouched by the miner - generally I allow the miner to use all but one thread. You can either do it manually by going into task manager -> processes, right clicking miner.exe, select Set Affinity, and unselect CPU 0. If you're launching it from a batch file, you can set the affinity in the batch file.

To do it via the batch file, do:  start "Burst Miner" /wait /affinity <affinity_mask> miner

The affinity mask is a hex representation of a binary value of your cpus. eg, if you have four threads, the binary mask is XXXX, where X is 0 or 1 - 0 means don't use that CPU, 1 means use it. So on a 4 thread CPU, to disable CPU0 for miner, the binary vale would be 1110, which is 0xE. So the command would be:

start "Burst Miner" /wait /affinity 0xD miner

For a 8 thread CPU, it'd be 1111 1110, => 0xFE, so start "Burst Miner" /wait /affinity 0x0FE miner

To leave two threads available:

start "Burst Miner" /wait /affinity 0xFD miner

Windows calc.exe has a programmers mode that can do the binary -> hex conversions for the hexidecimally challenged ;-)

H.

Thanks! That was helpful in regards to my CPU. My question in regards to RAM usage is still the problem. Resource manager watches my RAM fill up until I can no longer operate my computer. Unless I've misread your post, all your help was in use to my CPU, which does not run into any issues.

Could you elaborate on this "cleanmem" setting, and if I read your post correctly, it is only helpful BEFORE and AFTER mining process and not DURING, so my only real correction is using a new Windows OS, or is there clearing of the ram during the mining process I can write in?

[sellbuy]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 have problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Hey, so if I set the IO load to idle, then it would help? I'm trying it now. I'm confused by your wording which stated no go on Win7, but try this? Thanks

On Win7 you will always get lags, because on every read it try to cache the file, while caching (system IO always maxed) you will get lags. So first of all you need to change OS to Win8 or Win10.

Changing IO Priority On Win7 only help with system response by 20-50% depending on stagger/file size. Used or available amount of RAM anyway will not be affected.

Changing CPU(Process) Priority of Burst Miner never helped me, because problem was always with System process playing with Cache/RAM.
But disabling 1 core is a good idea.

Could you elaborate on this "cleanmem" setting, and if I read your post correctly, it is only helpful BEFORE and AFTER mining process and not DURING, so my only real correction is using a new Windows OS, or is there clearing of the ram during the mining process I can write in?

cleaning RAM will not help you much, every clean run(every 4 minutes) = lag.

[haitch]

I have 17 TB in my miner right now; just moved various HDD's to one rig due to a different mining algo I'm using would freeze it up when mining in conjunction. With 17 TB (blago's miner), my 16 gb of ram is not enough to let the miner run smoothly while also allowing me to work on the computer unaffected.. My question is... Is there a preferred ratio of HDD space (in terabytes) to ram ratio I should be shooting for? I'm going to pick up some more ram tomorrow, and I wanna know how much I need to get.

you need windows 8 or windows 10 for normal RAM using, windows 7 has problems with caching big files.
8gb of RAM is ok for mining on Windows 8.

try to set IO Priority & Cache Priority of burst miner to "idle" (System tool "Process Hacker" can do that, but manually)

anyway, high IO Load(big queque) may cause some lags even with 1 HDD mining.
for comfortable using PC you will need optimized miner

Memory doesn't really help - the miner itself uses very little memory, it's windows trying to be "helpful" and cache the data from the drives that sucks up the ram, enable the "cleanmem" setting and all memory will be retruned after the mining process. Add more memory and windows will just suck up more, until you force it to be released.

The problem issue you can run into, especially when mining multiple drives, is that you max out the CPU. Blagos miner will use one core/thread per drive/directory you specify. If you're mining with more drives than you have threads, your CPU will be maxed out. To get around this you can adjust the CPU affinity to leave some of the cores untouched by the miner - generally I allow the miner to use all but one thread. You can either do it manually by going into task manager -> processes, right clicking miner.exe, select Set Affinity, and unselect CPU 0. If you're launching it from a batch file, you can set the affinity in the batch file.

To do it via the batch file, do:  start "Burst Miner" /wait /affinity <affinity_mask> miner

The affinity mask is a hex representation of a binary value of your cpus. eg, if you have four threads, the binary mask is XXXX, where X is 0 or 1 - 0 means don't use that CPU, 1 means use it. So on a 4 thread CPU, to disable CPU0 for miner, the binary vale would be 1110, which is 0xE. So the command would be:

start "Burst Miner" /wait /affinity 0xD miner

For a 8 thread CPU, it'd be 1111 1110, => 0xFE, so start "Burst Miner" /wait /affinity 0x0FE miner

To leave two threads available:

start "Burst Miner" /wait /affinity 0xFD miner

Windows calc.exe has a programmers mode that can do the binary -> hex conversions for the hexidecimally challenged ;-)

H.

Thanks! That was helpful in regards to my CPU. My question in regards to RAM usage is still the problem. Resource manager watches my RAM fill up until I can no longer operate my computer. Unless I've misread your post, all your help was in use to my CPU, which does not run into any issues.

Could you elaborate on this "cleanmem" setting, and if I read your post correctly, it is only helpful BEFORE and AFTER mining process and not DURING, so my only real correction is using a new Windows OS, or is there clearing of the ram during the mining process I can write in?

The file caching shouldn't impact your usage, over time it can cause performance issues, but with the memory cleaning it's mostly resolved. during the mining process windows will use pretty much all available memory for caching, but it will not swap out other apps to make space for caching. On my daily PC, which is mining, memory usage during mining goes from around 4GB to just short of the 18GB installed, and I can't tell when mining is happening.

The memory clean does clean out everything that's cached, so that can impact your performance, but not to the level of your CPU getting maxed. To use the cleanmem setting, make sure you have Blagos latest miner, and have in your miner.conf

  "UseCleanMem" : true,

Miner is available from: https://github.com/Blagodarenko/miner-burst/releases/download/v1.150401/miner-burst-1.150401.zip

H.

[Grim]

question:

<...>
* for merged(optimized) plots miner read by 64*CacheSize bytes. For unmerged plots - by 64*stagger bytes.
<...>

can you explain how this is determined? is it as simple as reading the file name to see of nonces=stagger size?

Yes, miner compare filename's nonces and stagger.
https://github.com/Blagodarenko/miner-burst/blob/master/miner.cpp#L1690

This is done so that at one time would have read all the information available in part of plot.
for example, i have:
1) xxxx_yyyy_40000_4000
2) xxxx_yyyy_40960_4096
so, if i sets CacheSize = 4000, then 1) = 10 seeks, 2) = 11 seeks. And read by 64 bytes.
Now, miner reads all 64*stagger bytes, 1) = 10 seeks, 2) = 10 seeks.

Hi blago,

what do you recommend to set the cachesize to?

xxxx_yyyy_2048000_2048000
xxxx_yyyy_1024000_1024000
xxxx_yyyy_332800_332800
xxxx_yyyy_1433600_51200

[mczarnek]

You're all idiots for wasting your time and money on this shitcoin that will never amount to anything.

Says the guy who decided to start his own Burst clone a couple months ago... and runs a computer store and admits that any time he gets a computer to repair he'll look through the users drive trying to find BTC passwords.

haha.. hope he isn't invested in it!  Wouldn't want this guy to get rich someday..

it seems that burst didn't be updated for more than 2.5month, and the dev seems disapear for a long time, i am wondering whether the dev is still developing this coin? i have asked the same question one month ago, it seems lots of people said the the new update will come soon, but i didn't see any updates from the top of the thread now?

also poc2 is developed and will be implementet parallel with poc. so you can mine with you gpu AND with your hdd. with poc2 you need no so much hdd space as with normal poc. that will bring the coin to much more people who has their gpu mining rigs allready at home.

atm we all wait for the world first acct that will be done, if qora is ready this month.

hmm...I'm not sure if GPU mining is such a good idea. It was always about low power usage when mining this coin. And now we should throw away one of the main advantages?
PoC was a revolutionary approach with all those GPU/ASIC coins..

POC2 will not really allow GPU mining much more than POC

Basically the idea is that if miners hack it, they can store only partial proofs on your hard drive and use their GPU to try to figure out in real time what those missing bits should be.  However, realistically it doesn't make sense given that it is still much more cost and energy efficient to spend that money on an extra hard drive rather than a GPU.


Anyway, people are getting impatient.. but trust me, big things are happening in the background.  That being said.. please dump more coins!  I'm trying to make an effort to attract more developers and people who might have some venture capital for us and I'm sure they'd prefer to buy in cheaper!!  Not that I'm having much luck yet.. but you know.  Plus I told myself I wasn't allowed to buy any more Burst.. but at these prices, I splurged.. really hoping I don't regret it in the long run, though I really just don't see any way that Burst doesn't beat BTC some day.

And after some very through analysis of POC vs POS and POW.. POC has a lot more potential than most people realize.

See https://bitcointalk.org/index.php?topic=731923.msg10292524#msg10292524

Using single sha256 for nonce as a reference, the ballpark for conventional hardware of this TMTO is 25/75 pow/poc (bruteforce 8 bits of each 32bit nonce during a readout - assuming a disk can read 10Mnonce/s a second (*4 byte = 40Mbyte/s), that translates to 2560M nonce/s for top of the line GPU. The shorter the nonces are, the easier the PoW part is.

With dedicated hardware, 50/50 or more in favour of PoW.

As for your energy argument - if you have 1PB cluster eating 1kW and with a tiny (compared to HDDs) investment for PoW "booster" you have effectively 2PB cluster eating 2kW ... guess what most miners will opt for. Big appeal of current PoC is that most of capital investment is the equipment, not energy. POC2 as it is will drastically shift it towards conventional PoW.

On the upside - this can effectively get rid of NaS.

Fixing POW2 involves making the nonces large enough (at least 64 bit) so PoW becomes impractical for all intents and purposes.

What do you think about this fix for NaS?

Basically every block instead of getting a block reward you get votes, so simple example, I get one vote per block I mine.  I can later use those votes to vote for a block on the correct chain say 1000 blocks later.  This vote can be redeemed between blocks 1010 and 1210.

You get 1/3 of your block reward immediately, 1/3 if you include at least one other vote into your block, and 1/3 when your vote it used.  Note this method does have an issue and I'd prefer to say have it so that you get 10 votes, each only redeemable during different periods but that's the basic idea.

The only thing is, I can't tell whether or not that opens the door to a Byzantine General's issue, meaning we have a 33% attack on the system.. don't understand the Byzantine General's thing well enough.  Just started looking into that today.  I don't see why that would be an issue but if anyone understands Byzantine General's, please explain how you could attack that.  I'm thinking it is not an issue because the Byzantine General's attack is only an issue if someone carrying the message can change it, which due to the signature from someone who can be trusted due to their high POC, this can be trusted?


Regarding POC2 vs POC:

The motivation for POC2 was to make it faster to verify blocks, this should both improve the speed of blockchain parsing as well as limit the likelihood of a DDOS attack where someone can throw out random numbers claiming they are valid POCs and require all the miners to work through all 4096 hashes to get there.

Here are my thoughts on how you could combine POC and POC2:
https://burstforum.com/index.php?threads/poc2-and-asic-resistance.796/

idk.. maybe it's not worth it.  Question is, how long does it take to verify a hash and does making it 500 to 1000 times faster to verify a block significantly decrease DDOS attack risk?  What about how long would it take to verify a couple years worth of block headers?  Burstdev did come up with an interesting way to essentially checkpoint our chain so that customers could only download one blockheader per week.. maybe that fixes the problem and this is no longer needed

So, to me the most important number is, how long does it take to do 4096 Shabal256's vs 1 Shabal256.  Anyone have a precise number?