your miner name is "pascalcoin" that's 10 characters... you should rename miner using 8 characters like "pascalco", in your wallet too rename the miner name to 8 characters and always mine with this key (8 characters too) when you create a key use the "secp256k1"

I did everything you wrote but a miner and does not start

In your PascalCoin wallet,when you open Project -> Operations, what is the miner name in the box?

your miner name is "pascalcoin" that's 10 characters... you should rename miner using 8 characters like "pascalco", in your wallet too rename the miner name to 8 characters and always mine with this key (8 characters too) when you create a key use the "secp256k1"

I did everything you wrote but a miner and does not start

In your PascalCoin wallet,when you open Project -> Operations, what is the miner name in the box?

pascalco

What directory is your PascalProxyv2.jar file in, and do you run it by double-clicking on it?

your miner name is "pascalcoin" that's 10 characters... you should rename miner using 8 characters like "pascalco", in your wallet too rename the miner name to 8 characters and always mine with this key (8 characters too) when you create a key use the "secp256k1"

I did everything you wrote but a miner and does not start

In your PascalCoin wallet,when you open Project -> Operations, what is the miner name in the box?

pascalco

What directory is your PascalProxyv2.jar file in, and do you run it by double-clicking on it?

Pretty sure what happened was an attack on Pascal, but maybe not who knows. They threw huge hash on. Running the hash up to 100,000 MHs and made the difficulty really high then left. I've seen this before with other coins as people seem to do it in attempts to try and stop coins they don't like. Likely some zcash kiddie that's mad Pascal has been out for about 3 months already and doing more than zcash or other coins. Plus Pascal already has working GPU miners thanks to Vorksholk. I'll just be glad when the difficulty falls so we can all get blocks again.

Pretty sure what happened was an attack on Pascal, but maybe not who knows. They threw huge hash on. Running the hash up to 100,000 MHs and made the difficulty really high then left. I've seen this before with other coins as people seem to do it in attempts to try and stop coins they don't like. Likely some zcash kiddie that's mad Pascal has been out for about 3 months already and doing more than zcash or other coins. Plus Pascal already has working GPU miners thanks to Vorksholk. I'll just be glad when the difficulty falls so we can all get blocks again.

Its not an attack its the way difficulty works. It ramps up slowly and then takes a while to level off if the miners leave. Alot of miners like me left when it hit 100GH/s since there is no exchange and no value yet for this coin.

Network hashrate is down so I decided to fire off the AMD miner today and watch it closer.

Why is it duplicating some of these nonces on the same GPU and submitting them twice?

The readme file with Vorksholk's miner suggests: "If you notice your miner finding several of the same nonce, try lowering the intensity and/or cyclesize (because you're sending so much work to the GPU that it can't get a timestamp often enough, so it exhausts the 4-ish billion possible nonces (~4 GH), and starte repeating work)."

Network hashrate is down so I decided to fire off the AMD miner today and watch it closer.

Why is it duplicating some of these nonces on the same GPU and submitting them twice?

The readme file with Vorksholk's miner suggests: "If you notice your miner finding several of the same nonce, try lowering the intensity and/or cyclesize (because you're sending so much work to the GPU that it can't get a timestamp often enough, so it exhausts the 4-ish billion possible nonces (~4 GH), and starte repeating work)."

i missed that part ... reduced (from default) my intensity to 22 and cycles to 45 ... seems "same nonce's" are gone .

Network hashrate is down so I decided to fire off the AMD miner today and watch it closer.

Why is it duplicating some of these nonces on the same GPU and submitting them twice?

The readme file with Vorksholk's miner suggests: "If you notice your miner finding several of the same nonce, try lowering the intensity and/or cyclesize (because you're sending so much work to the GPU that it can't get a timestamp often enough, so it exhausts the 4-ish billion possible nonces (~4 GH), and starte repeating work)."

i missed that part ... reduced (from default) my intensity to 22 and cycles to 45 ... seems "same nonce's" are gone .

Thanks for this, I guess we need to start putting best intensity and cycles to GPU types to get best results.

I was using 23 and 50 as referenced in the example, will try 22 and 45