Quote from: bible_pay on January 22, 2020, 05:06:00 PM

Quote from: bible_pay on January 22, 2020, 03:49:37 PM

Quote from: WhyMe on January 22, 2020, 03:38:54 PM

Quote from: bible_pay on January 22, 2020, 02:58:51 PM

Quote from: WhyMe on January 22, 2020, 01:14:05 AM

Solo mining with a Ryzen, 8 threads doing each 24kHs, 192kHs combined, now considered as gpu mining !? Are you serious ?
2020-01-22 01:00:49 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: 57786e9e872bfaeff5d2d5a020d68c71eea849fbe9c242b7a2d86612938eef06, high-hash, proof of work failed (code 16)

My server with 16 threads doing each 10kHs, 160kHs combined is running fine and finding blocks.

This release for ( trying to ) block gpu is just a bunch of crap ...

"bunch of crap":
-> No, I'm afraid you don't know what you are talking about. Could you provide one piece of evidence of a way to get around it with a gpu? Or, you can surely win the 2 mil bounty if you care to? Please explain.

All I'm asking for is for you to explain your position in detail. I've been answering your posts but this seems to be a one way endeavor (you just complain more with a baseless complaint).

For sure I'm complaining ! With the last release I can't anymore use my Ryzen 2600x !
You're trying to lock gpus, it's fine I'm correct with that.
But your modification is too restrictive, "high" cpu hashrate is locked too !
And there's a BIG difference between a Ryzen doing something like 190kHs and a GTX 1070 doing 7MHs no ?

Quote from: dave_bbp on January 22, 2020, 03:25:12 PM

Quote from: bible_pay on January 22, 2020, 02:58:51 PM

Quote from: WhyMe on January 22, 2020, 01:14:05 AM

Solo mining with a Ryzen, 8 threads doing each 24kHs, 192kHs combined, now considered as gpu mining !? Are you serious ?
2020-01-22 01:00:49 ERROR: AcceptBlockHeader: Consensus::CheckBlockHeader: 57786e9e872bfaeff5d2d5a020d68c71eea849fbe9c242b7a2d86612938eef06, high-hash, proof of work failed (code 16)

My server with 16 threads doing each 10kHs, 160kHs combined is running fine and finding blocks.

This release for ( trying to ) block gpu is just a bunch of crap ...

"bunch of crap":
-> No, I'm afraid you don't know what you are talking about. Could you provide one piece of evidence of a way to get around it with a gpu? Or, you can surely win the 2 mil bounty if you care to? Please explain.

All I'm asking for is for you to explain your position in detail. I've been answering your posts but this seems to be a one way endeavor (you just complain more with a baseless complaint).

@Rob: his problem is NOT a hypothetical ability to mine with GPU, but a now existing INability to mine with a high power CPU.

@whyme: why don't you redirect your ryzen against WCG and do some PODC instead of simple "heat mining"? Wink

Just finding 1 solo block per day pays more than WCG. And it's winter here, so just doing heat is fine.

Just to clarify my position, I'm not against you complaining

... I was under the impression your position was that our GPU restricition was fake. I just want to clarify that our GPU restriction has been tested from 2017-2018 and it works fine (the logic is sound).

So your talking more about the heat mining environment itself not working, OK, I will look at that now.

Sorry to ruffle your feathers. Checking.

We are here to provide a quality environment for the miners- we will not tolerate broken software; if something is broken I was not aware of it.

I'll run each of the miners on my windows machine first.

So far I have only tested nomp mining on my ryzen windows box and I found a couple problems.

The pool difficulty was not set correctly for pobh 2.0, and there was an issue where we complain too often about invalid shares.

These things have just been adjusted. Its not 'perfect' yet but it appears to be working now (that is pool mining against nomp.biblepay.org).

If you have problems, try increasing the thread count with "-t40" for example in the command line string.
Then wait a while and look at the nomp leaderboard.

When time permits Ill try to hone in on lowering the reject rate to be more like 90% like we had in 1.0.

In the mean time Ill check out solo mining against the wallet using the external miner.

The internal miner seems to be fine (solo mining with setgenerate true 40 for example, gives me 225KHPS, and the nonce was tested in unit testing mode yesterday, so I know the internal miner is working).

Ill test the external miner in solo mode.

Ok now Im testing my external miner on my ryzen windows box (bbpminer64.exe -o http://127.0.0.1:12000 -uusername -ppass -t40) and its working. In task manager I see 99% cpu utilization.

Two days ago, I tested the external miner against testnet using pobh 2.0. To address your concern about finding a share, and then seeing the other threads reject the same share, thats because in solo mode, if you find a block, the other threads have not joined the main thread yet and the other submissions are stale. We do explicitly restart the work request (see the code) and let them join - so that is not a bug, its just a lagging display which gets cleared from the page in about 10 more seconds.

I don't see a problem. I confirmed that this miner can solo mine against testnet and find blocks, and its running at full speed.
You might just need to add the parameter "-t40" to the end of your string.

Otherwise please tell us what problem you are having with heat mining.