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

[fanepatent]

can you elaborate on how the payments work on these pools?

On uray based pools, the pool takes the one best deadline you find each block and runs it through a formula to give you a score. When the pool finds a block, it splits it up based on the scores users have.

On my v2 pool, the pool has a set deadline target, and amount of shares to keep. The miner submits each share that results in a deadline under the target. The pool always maintains a fixed amount of shares, so when a new one is submitted, the oldest one is discarded. When a block is found, it splits the block up based on the number of shares each user has in that fixed size buffer.

Will you make the source code available for the v2 pool?

[burstcoin]

can you elaborate on how the payments work on these pools?

On uray based pools, the pool takes the one best deadline you find each block and runs it through a formula to give you a score. When the pool finds a block, it splits it up based on the scores users have.

On my v2 pool, the pool has a set deadline target, and amount of shares to keep. The miner submits each share that results in a deadline under the target. The pool always maintains a fixed amount of shares, so when a new one is submitted, the oldest one is discarded. When a block is found, it splits the block up based on the number of shares each user has in that fixed size buffer.

Will you make the source code available for the v2 pool?

I need to check it for bugs more thoroughly before I would consider releasing it.

[twig123]

I'm running 4TB on a quad-core with 4GB RAM (Win7).

Both the "burst-pool-miner" and the new "burst-miner" miners absolutely thrashes whatever drive I have the pagefile setup on (causing the system to be pretty much unusable).

I have already disabled prefetch/superfetch like several have suggested and the pagefile usage is a lot better, but still gets hit up really hard.

I've tested this same system running Ubuntu instead of Windows 7... and it works perfectly fine... same hardware, different OS.

On the other hand, I have another system with a 4TB, 4GB RAM, but running Windows Server 2012... and has 0 issues with resources like Win7.

What is going on with the Memory/Pagefile usage in Windows 7 when mining? and does anyone know of a solution?

[cyberspacemonkey]

On dcct's new miner I keep getting this:

Code:

Could not get mining info from Node. Will retry..             
917 MB read/3671 GB total/deadline 1426805s (1426631s left)           
New block 14088, basetarget 2407011                          
21 MB read/85 GB total/deadline 711256s (711246s left)                   
Walet reported no deadline.
917 MB read/3671 GB total/deadline 117016s (116939s left)           
New block 14089, basetarget 2360711                          
317 MB read/1271 GB total/deadline 73700s (73684s left)              
Walet reported no deadline.
917 MB read/3671 GB total/deadline 73700s (73307s left)           
New block 14090, basetarget 2395043                          
0 MB read/0 GB total/no deadline                 
Walet reported no deadline.

Is this normal? If not, how do I fix it? Please help!

Can someone familiar with dcct's new miner please answer this for me?  

Its not normal, pool or solo mining?

New block 14094, basetarget 2446962
1360 MB read/5440 GB total/deadline 178039s (177773s left)
New block 14095, basetarget 2505140
1360 MB read/5440 GB total/deadline 5074s (4930s left)
New block 14096, basetarget 2554054
1360 MB read/5440 GB total/deadline 520849s (520485s left)
New block 14097, basetarget 2671767
1360 MB read/5440 GB total/deadline 381845s (381787s left)
New block 14098, basetarget 2492339
1360 MB read/5440 GB total/deadline 1075203s (10748s left)
New block 14099, basetarget 2550128
1360 MB read/5440 GB total/deadline 3395s (3175s left)
New block 14100, basetarget 2586473
 

I'm mining at a pool but it's not uray's, it's another pool based on uray's.

Anyone using dcct's miner care to help me out?

[cyberspacemonkey]

Code:

Could not get mining info from Node. Will retry..

             
             

Code:

Walet reported no deadline.

Why do I keep getting this?

[pimytron]

Code:

Could not get mining info from Node. Will retry..

             
             

Code:

Walet reported no deadline.

Why do I keep getting this?

The same.

[fivebells]

I only tried a mining pool for a few hours before giving up on it.  When I was getting those messages, it was because the pool network was hosed.  I also saw extremely long deadlines when I tried to telnet to the mining pool ports directly.

The "no deadline" messages look perfectly normal to me for a 4TB drive.  I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times.  In your first "no deadline" message, the block was found before you had finished scanning your HD.  In the second, it had only just started scanning the drive.

[burstcoin]

The "no deadline" messages look perfectly normal to me for a 4TB drive.  I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times.  In your first "no deadline" message, the block was found before you had finished scanning your HD.  In the second, it had only just started scanning the drive.

You really should optimize those plots. With the reference implementation's 8191 stagger limit, I'm able to scan a 2TB drive in under 15 seconds. With new generators, or dcct's optimizer, I'd imagine I could get it down to ~3 seconds.

[fivebells]

Yeah, I'm optimizing one now.  Unfortunately I can only afford an SSIZE of 8, it's going to take about a week to optimize a 2.4TB plot, and I have about 30TB of plots.  The stagger on these plots is 7500, which was optimal for my GPU, but that's looking like a false economy now.

The limiting factor at the moment is writes.  I'm getting about 40MB/s for writing out the optimized plot.

[twig123]

The "no deadline" messages look perfectly normal to me for a 4TB drive.  I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times.  In your first "no deadline" message, the block was found before you had finished scanning your HD.  In the second, it had only just started scanning the drive.

You really should optimize those plots. With the reference implementation's 8191 stagger limit, I'm able to scan a 2TB drive in under 15 seconds. With new generators, or dcct's optimizer, I'd imagine I could get it down to ~3 seconds.

How does one optimize plots? is there a Windows tool?
(I was only able to max my stagger at 2000 with my GPU)

[burstcoin]

The "no deadline" messages look perfectly normal to me for a 4TB drive.  I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times.  In your first "no deadline" message, the block was found before you had finished scanning your HD.  In the second, it had only just started scanning the drive.

You really should optimize those plots. With the reference implementation's 8191 stagger limit, I'm able to scan a 2TB drive in under 15 seconds. With new generators, or dcct's optimizer, I'd imagine I could get it down to ~3 seconds.

How does one optimize plots? is there a Windows tool?
(I was only able to max my stagger at 2000 with my GPU)

https://bitcointalk.org/index.php?topic=731923.msg8879760#msg8879760
There's a windows build in the bin folder in that archive.

[twig123]

The "no deadline" messages look perfectly normal to me for a 4TB drive.  I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times.  In your first "no deadline" message, the block was found before you had finished scanning your HD.  In the second, it had only just started scanning the drive.

You really should optimize those plots. With the reference implementation's 8191 stagger limit, I'm able to scan a 2TB drive in under 15 seconds. With new generators, or dcct's optimizer, I'd imagine I could get it down to ~3 seconds.

How does one optimize plots? is there a Windows tool?
(I was only able to max my stagger at 2000 with my GPU)

https://bitcointalk.org/index.php?topic=731923.msg8879760#msg8879760
There's a windows build in the bin folder in that archive.

Does this modify the existing file or create a new file?
Ex: Do I need to have the same amount of free space as the plot I'm trying to optimize?

[mmmaybe]

The "no deadline" messages look perfectly normal to me for a 4TB drive.  I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times.  In your first "no deadline" message, the block was found before you had finished scanning your HD.  In the second, it had only just started scanning the drive.

You really should optimize those plots. With the reference implementation's 8191 stagger limit, I'm able to scan a 2TB drive in under 15 seconds. With new generators, or dcct's optimizer, I'd imagine I could get it down to ~3 seconds.

How does one optimize plots? is there a Windows tool?
(I was only able to max my stagger at 2000 with my GPU)

https://bitcointalk.org/index.php?topic=731923.msg8879760#msg8879760
There's a windows build in the bin folder in that archive.

Does this modify the existing file or create a new file?
Ex: Do I need to have the same amount of free space as the plot I'm trying to optimize?

You will need the same amount of free space as the plot you'r optimizing.

[MsCollec]

Burst will likely fall to 50 satoshi by Saturday and then 0 sat by the end of next week. Cut your loss now before its too late
Feed the whales and regret your decision in few months

[twig123]

The "no deadline" messages look perfectly normal to me for a 4TB drive.  I just pulled the latest log for one of mine, and out of 276 blocks, no deadline was reported before the next block started 74 times.  In your first "no deadline" message, the block was found before you had finished scanning your HD.  In the second, it had only just started scanning the drive.

You really should optimize those plots. With the reference implementation's 8191 stagger limit, I'm able to scan a 2TB drive in under 15 seconds. With new generators, or dcct's optimizer, I'd imagine I could get it down to ~3 seconds.

How does one optimize plots? is there a Windows tool?
(I was only able to max my stagger at 2000 with my GPU)

https://bitcointalk.org/index.php?topic=731923.msg8879760#msg8879760
There's a windows build in the bin folder in that archive.

Does this modify the existing file or create a new file?
Ex: Do I need to have the same amount of free space as the plot I'm trying to optimize?

You will need the same amount of free space as the plot you'r optimizing.

Gah! So, I'd have to delete have my plots to optimize a single plot... very lame.

[fivebells]

Burst will likely fall to 50 satoshi by Saturday and then 0 sat by the end of next week. Cut your loss now before its too late
Feed the whales and regret your decision in few months

Well, clearly no one here knows the right way to do a debut on bittrex, I'll give you that. :-)

PLEASE let the price fall to 50s!  PUH-LEAZE!!

[omgbossis21]

Drop to 0 not likely, its just bitcoin is down to $400 what do you want?   Its not looking good for bitcoin atm and with ebay announcing they will accept it they will likely have a big sale like newegg and then another huge dump.....

[Irontiga]

Drop to 0 not likely, its just bitcoin is down to $400 what do you want?   Its not looking good for bitcoin atm and with ebay announcing they will accept it they will likely have a big sale like newegg and then another huge dump.....

Wow, 130 sats, that's too low. If anyone wants to start something for a burst marketplace, pm me. Hmm...we need investors...I'll say something on nxtforum... Maybe....

[yellowduck2]

Drop to 0 not likely, its just bitcoin is down to $400 what do you want?   Its not looking good for bitcoin atm and with ebay announcing they will accept it they will likely have a big sale like newegg and then another huge dump.....

Wow, 130 sats, that's too low. If anyone wants to start something for a burst marketplace, pm me. Hmm...we need investors...I'll say something on nxtforum... Maybe....

maybe someone should start a campaign to advertise burst to NXT community. I am sure some of them are interested to invest in burst if they are invested in NXT.

[timk225]

10.43 TB mining and I haven't gotten a GODDAMN single coin in four days!!!  WTF!!!