@cryptonick said in POC1 to POC2 Plot Converter 2.3 Gives REALLY BAD deadline errors after conversion:

burstmining.club

Which block did you win ? I don't see the pool winning in the last 30 rounds - and looking at the pool stats:
2,423 Registered Miners, 261 Active Miners

Last Block: 14 Active Miners, 16 Good DLs submitted, 67 Bad DLs submitted.

Edit:

This was not intended to disparage the pool - just the stats look really odd.

Of 2,400 Miners, ~10% of them are active. Of those ~10% of miners who are "active", ~5% submitted DL's. So of the 0.5% of registered miners who submitted DLs, 80% of the DLs were invalid.

Those numbers are off the wall just weird.

@cryptonick I'd be very surprised if the only valid nonces/DL's you found came from the 1 converted (of 13) drives. Are you sure your miner & pool are properly configured for PoC2? I've converted over 100 drives and am not having any problems, and the remaining PoC1 drives are slower than the PoC2 drives.

@cryptonick From your screen shot, drive H is the only one that has completed conversion. All the other drives are being treated as PoC1 plots, so if conversion was started on them, it didn't complete - so the plots are corrupted, and causing the DL error.

@zapbuzz It's not handling the 502000 change - bootstrap it again, the bootstrap download should be post 502K.

@rds TurboSwizzler is a convertor, not a plotter.

@Agabus274 I don't know if Turboswizzler can pause/resume conversions. You may need to delete the target plotfile and start again.

If you're using the modified Blago miner, test out different values for the cache/cache2 values - they can make a huge performance difference.

I tested with different values from 8K upto 512K. Then tested performance to 50% of plot read and 100% read. This is around 1PB of mixed PoC1 PoC2 plots - around 50/50. Some example readings:

256K/64K - 50% @ 2,950MB/s, Total: 120 Seconds
512K/64K - 50% @ 3,120MB/s, Total: 117 Seconds
512K/8K - 50% @ 3,600MB/s, Total: 189 Seconds (!)
512K/128K - 50% @ 2,800MB/s, Total: 99 Seconds.

As the ratio of PoC1 to PoC2 changes, I'd expect the optimal settings to change. As a general rule of thumb it seems to be: Use a larger C1/smaller C2 for a lot of Poc2 files, Large C2/Smaller C1 for a lot of PoC1 files.

@tate-a For current Blago miners, use Johnnys modified version: https://github.com/JohnnyFFM/miner-burst/releases

@quasar said in Hi, I need one Burstcoin to start mining!:

BURST-3PLU-9UWR-UMMZ-DUDPN

Sent you both a coin. Use it to join a pool, NOT to set your name.

@quasar said in [ERROR 1004] "Your Burst account's reward recipient does not match pool's account":

BURST-3PLU-9UWR-UMMZ-DUDPN

I'd say come back to mining on my pool ;-) But have sent you some Burst to choose a pool.

@mr-x Don't know why it's now requiring a password - definitely wasn't previously. All links on the site now seem password protected.

Pools supporting PoC2 include all the burst-team.us pools, the CryptoGuru pool, burstmine.ro, solominer.ddns.net

Others please contribute to the list.