CCminer(SP-MOD) Modded GPU kernels.

[sp_]

Looks like zec is about to take nosedive so another nvidia-coin would be very welcome.

Lbry, nice efficiency on nvidia and profit @ the level of zcash nowadays. Hope to see some news for the lbry miner, sp_ anything ?  

I get some more time in the next month. Just a small speedup in #5. Around +7% on the gtx 1070.

[m1n1ngP4d4w4n]

Looks like zec is about to take nosedive so another nvidia-coin would be very welcome.

Lbry, nice efficiency on nvidia and profit @ the level of zcash nowadays. Hope to see some news for the lbry miner, sp_ anything ?  

I get some more time in the next month. Just a small speedup in #5. Around +7% on the gtx 1070.

Is lbry spmod #5 available for purchase (0.05 BTC) ? still with that 2.5% fee ?

[sp_]

Is lbry spmod #5 available for purchase (0.05 BTC) ? still with that 2.5% fee ?

Not yet. Perhaps some time next week

[m1n1ngP4d4w4n]

Is lbry spmod #5 available for purchase (0.05 BTC) ? still with that 2.5% fee ?

Not yet. Perhaps some time next week

Alright, shoot me up a PM as soon as you release, i'll be interested, cheers  

Would you consider lowering to 2% fee btw ?

[bathrobehero]

As KlausT mentioned, CUDA JSON-RPC issues are caused by Pascalproxyv2, it doesn't send "target" param to the miner.

Now we need that shitty proxy source... or a completely new miner 

Or if somebody has time he can read proxy console output and replace headeroutXX.txt with correct value for "target", currently it's 000000000 for every round...

[felixbrucker]

As KlausT mentioned, CUDA JSON-RPC issues are caused by Pascalproxyv2, it doesn't send "target" param to the miner.

Now we need that shitty proxy source... or a completely new miner  

Or if somebody has time he can read proxy console output and replace headeroutXX.txt with correct value for "target", currently it's 000000000 for every round...

anyone can see the src, thats not the problem, just decompile the jar it takes about 10 sec to google how

edit: here it is

http://pastebin.com/SrPkQRrQ
http://pastebin.com/0HPWetzi

[reb0rn21]

Network hasrate in the wallet is totaly fuckedup, same with the diff retarget is insane..... profitability is a lot less then reported by calculator

even AMD miners with 60Ghs have problem finding block today

and about NV miner i mined 12h with 20Ghs 36h ago, maybe was bad luck, maybe cuda miner/proxy is screwed we don`t know at all

bitcause had 100 NV GPU on it and got no block, and AMD hw are finding blocks just fine

[ioglnx]

As KlausT mentioned, CUDA JSON-RPC issues are caused by Pascalproxyv2, it doesn't send "target" param to the miner.

Now we need that shitty proxy source... or a completely new miner  

Or if somebody has time he can read proxy console output and replace headeroutXX.txt with correct value for "target", currently it's 000000000 for every round...

anyone can see the src, thats not the problem, just decompile the jar it takes about 10 sec to google how

edit: here it is

http://pastebin.com/SrPkQRrQ
http://pastebin.com/0HPWetzi

So then what? We is the problem then

[bensam1231]

I've mined with a pretty substantial amount of hashing power for about 12 hours and didn't find a block. I tried .4 for about 8 of those, .3 for about 4 of those, I also tried one wallet per rig with the same 8 character mining name and the same mining key (newest wallet), no block.

A lot of things could be happening here. Since there is no way to verify whether or not your mining setup is working till you're finding a block I'm basically possibly pissing hash away. A lot of people are basing profitability based off of cryptocompare, but I definitely don't think that's right. I'm pretty sure the amount you make is a lot lower then that. I should be hitting a block every half a hour. Given there are 12 blocks per hour and I've already been through 12 hours of those, it's safe to say something is fucked up.

Just a FYI, don't waste your time on this. Unless someone comes up with a guide down to the letter, this is a silly waste of time and energy. AMD seems to work, but that may be due to a large amount of AMD users... not necessarily because the miners/wallet are broken for Nvidia.

[bathrobehero]

I've mined with a pretty substantial amount of hashing power for about 12 hours and didn't find a block. I tried .4 for about 8 of those, .3 for about 4 of those, I also tried one wallet per rig with the same 8 character mining name and the same mining key (newest wallet), no block.

A lot of things could be happening here. Since there is no way to verify whether or not your mining setup is working till you're finding a block I'm basically possibly pissing hash away. A lot of people are basing profitability based off of cryptocompare, but I definitely don't think that's right. I'm pretty sure the amount you make is a lot lower then that. I should be hitting a block every half a hour. Given there are 20 blocks per hour and I've already been through 12 of those, it's safe to say something is fucked up.

Just a FYI, don't waste your time on this. Unless someone comes up with a guide down to the letter, this is a silly waste of time and energy. AMD seems to work, but that may be due to a large amount of AMD users... not necessarily because the miners/wallet are broken for Nvidia.

At this point I'm pretty certain if you get "Sending Error JSON RPC id () : Invalid payload" in your pascalcoin log then mining is not working.

The issue has to come from the java proxy.

[ioglnx]

This is the last block I have found 56952..and here is the debug log :-D

Code:

2017-01-27 10:03:41.861 TID:0000343C [Update] <TPCOperationsComp> New block height:56951 nOnce:-278407448 timestamp:1485507822 Operations:0 Fee:0 SafeBoxBalance:56952000000=56952000000 PoW:00000000000010D516BBF1611BD12AA5F8E3B008CAB7F4A526D6324607F385C8 Operations previous Safe Box hash:470DD20D5FFEF1139D4A29672AA8A20E3BD2959DC2FA68796E9FDD0F98D656A6 Future old Safe Box hash for next block:5E4A4406918F7B3777801B5B7488FB9BF76ECA80066FDB1A32CEE67480541113
2017-01-27 10:03:41.861 TID:000031A8 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 63
2017-01-27 10:03:41.861 TID:00003C34 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 64
2017-01-27 10:03:41.861 TID:00002908 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 65
2017-01-27 10:03:41.861 TID:0000323C [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 66
2017-01-27 10:03:41.861 TID:000027B8 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 67
2017-01-27 10:03:41.861 TID:000019F0 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 68
2017-01-27 10:03:41.861 TID:00003B34 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 69
2017-01-27 10:03:41.861 TID:00002480 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 70
2017-01-27 10:03:41.861 TID:00003778 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 71
2017-01-27 10:03:41.861 TID:0000343C [Debug] <TNode> Finalizing AddNewBlockChain Connection:024507B0 NewBlock:Block:56952 Timestamp:1485507822 Reward:1000000 Fee:0 PoW:06D8C0E07292C4EFB59F34F6DA44EB0A4C8725A00D3EFFA3C986809642380915
2017-01-27 10:03:41.861 TID:00002D90 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 72
2017-01-27 10:03:41.861 TID:000039A0 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 73
2017-01-27 10:03:41.861 TID:00003D78 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 74
2017-01-27 10:03:41.861 TID:00003670 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 75
2017-01-27 10:03:41.861 TID:0000285C [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 76
2017-01-27 10:03:41.861 TID:00003ABC [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 77
2017-01-27 10:03:41.861 TID:00001C04 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 78
2017-01-27 10:03:41.861 TID:00003C7C [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 79
2017-01-27 10:03:41.861 TID:00003A54 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 80
2017-01-27 10:03:41.861 TID:0000265C [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 81
2017-01-27 10:03:41.861 TID:00003AF4 [Debug] <TThreadNodeNotifyNewBlock> Starting Thread in pos 82
2017-01-27 10:03:41.883 TID:00003B34 [Debug] <TThreadNodeNotifyNewBlock> Sending new block found to 194.58.188.89:59997
2017-01-27 10:03:41.883 TID:00003B34 [Debug] <TNetServerClient> Sending: Autosend operation:NEW BLOCK id:951 errorcode:0 Size:273b (Data:251b) to 194.58.188.89:59997
2017-01-27 10:03:41.892 MAIN:00002834 [Debug] <TJSONRPCTcpIpClient> Sending JSON-RPC: {"method":"miner-notify","params":[{"block":56952,"version":1,"part1":"78DE0000CA022000586656AFFC7BCBCE6B5D9D8F90B2B8E5864822CE9781BD1C70AC9FA1517AE9B520006F5558E4E18F39E9F51865394CC5494428EA7D79AE754DCA4C31EBE12103D6F640420F00000000000100010001D9D430","payload_start":"696F676C6E786E76","part3":"5E4A4406918F7B3777801B5B7488FB9BF76ECA80066FDB1A32CEE67480541113E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000","target":819255553,"target_pow":"00000000000095937F0000000000000000000000000000000000000000000000","timestamp":1485507822}],"id":null}
2017-01-27 10:03:41.893 MAIN:00002834 [Debug] <TJSONRPCTcpIpClient> Sending JSON-RPC: {"method":"miner-notify","params":[{"block":56952,"version":1,"part1":"78DE0000CA022000586656AFFC7BCBCE6B5D9D8F90B2B8E5864822CE9781BD1C70AC9FA1517AE9B520006F5558E4E18F39E9F51865394CC5494428EA7D79AE754DCA4C31EBE12103D6F640420F00000000000100010001D9D430","payload_start":"696F676C6E786E76","part3":"5E4A4406918F7B3777801B5B7488FB9BF76ECA80066FDB1A32CEE67480541113E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000","target":819255553,"target_pow":"00000000000095937F0000000000000000000000000000000000000000000000","timestamp":1485507822}],"id":null}

2017-01-27 10:04:17.695 TID:000018DC [Debug] <TNode> AddNewBlockChain Connection:00000000 NewBlock:Block:56952 Timestamp:1485507858 Reward:1000000 Fee:100 PoW:000000000F1F76C3F35D8549E1E622CF2C9F76FDD39733138BFAC33285DE2B68
2017-01-27 10:04:17.696 TID:000018DC [Error] <TPCOperationsComp> Invalid new block 56952: Proof of work is higher than target
2017-01-27 10:04:17.697 TID:000018DC [Debug] <TPCOperationsComp> Sanitizing (pos:1/1): Transaction from 52465-93 to 143351-30 amount:99,9900 fee:0,0100 (n_op:1) payload size:64
2017-01-27 10:04:17.697 TID:000018DC [Debug] <TPCOperationsComp> Sanitize operations (before 1 - after 1)
2017-01-27 10:04:17.697 TID:000018DC [Debug] <TNode> Finalizing AddNewBlockChain Connection:00000000 NewBlock:Block:56952 Timestamp:1485507858 Reward:1000000 Fee:100 PoW:000000000F1F76C3F35D8549E1E622CF2C9F76FDD39733138BFAC33285DE2B68
2017-01-27 10:04:17.697 TID:000018DC [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Proof of work is higher than target payload:ioglnxnv02 timestamp:1485507858 nonce:3984220427
2017-01-27 10:04:17.715 TID:00002BAC [Debug] <TBufferedNetTcpIpClientThread> Sent 138 bytes
2017-01-27 10:04:18.361 TID:00003A30 [Debug] <TBufferedNetTcpIpClientThread> Received 115 bytes. Buffer length: 115 bytes
2017-01-27 10:04:18.362 TID:000039EC [Debug] <TNode> AddNewBlockChain Connection:00000000 NewBlock:Block:56952 Timestamp:1485507858 Reward:1000000 Fee:100 PoW:000000000F1F76C3F35D8549E1E622CF2C9F76FDD39733138BFAC33285DE2B68
2017-01-27 10:04:18.363 TID:000039EC [Error] <TPCOperationsComp> Invalid new block 56952: Proof of work is higher than target
2017-01-27 10:04:18.363 TID:000039EC [Debug] <TPCOperationsComp> Sanitizing (pos:1/1): Transaction from 52465-93 to 143351-30 amount:99,9900 fee:0,0100 (n_op:1) payload size:64
2017-01-27 10:04:18.364 TID:000039EC [Debug] <TPCOperationsComp> Sanitize operations (before 1 - after 1)
2017-01-27 10:04:18.364 TID:000039EC [Debug] <TNode> Finalizing AddNewBlockChain Connection:00000000 NewBlock:Block:56952 Timestamp:1485507858 Reward:1000000 Fee:100 PoW:000000000F1F76C3F35D8549E1E622CF2C9F76FDD39733138BFAC33285DE2B68
2017-01-27 10:04:18.364 TID:000039EC [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Proof of work is higher than target payload:ioglnxnv02 timestamp:1485507858 nonce:3984220427
2017-01-27 10:04:18.382 TID:00003A30 [Debug] <TBufferedNetTcpIpClientThread> Sent 138 bytes
2017-01-27 10:04:42.047 TID:00001510 [Debug] <TBufferedNetTcpIpClientThread> Received 259 bytes. Buffer length: 259 bytes
2017-01-27 10:04:42.049 TID:00003BEC [Debug] <TNetClient> Received Autosend operation:ADD OPERATIONS id:0 Buffer size:237
2017-01-27 10:04:42.049 TID:00003BEC [Debug] <TNode> AddOperations Connection:084070F0 Operations:1
2017-01-27 10:04:42.049 TID:00003BEC [Debug] <TNode> AddOperation 1/1: Transaction from 52475-35 to 143351-30 amount:99,9900 fee:0,0100 (n_op:1) payload size:64
2017-01-27 10:04:42.050 TID:00002804 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 63
2017-01-27 10:04:42.050 TID:000005C8 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 64
2017-01-27 10:04:42.050 TID:00002434 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 65
2017-01-27 10:04:42.050 TID:00002B7C [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 66
2017-01-27 10:04:42.050 TID:00003728 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 67
2017-01-27 10:04:42.050 TID:0000195C [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 68
2017-01-27 10:04:42.050 TID:00002B18 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 69
2017-01-27 10:04:42.050 TID:00000850 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 70
2017-01-27 10:04:42.050 TID:00003B48 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 71
2017-01-27 10:04:42.050 TID:00001D78 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 72
2017-01-27 10:04:42.050 TID:00003B08 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 73
2017-01-27 10:04:42.050 TID:00002A84 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 74
2017-01-27 10:04:42.050 TID:000003A8 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 75
2017-01-27 10:04:42.050 TID:00003980 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 76
2017-01-27 10:04:42.050 TID:00003F64 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 77
2017-01-27 10:04:42.050 TID:00003FA4 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 78
2017-01-27 10:04:42.050 TID:00001D24 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 79
2017-01-27 10:04:42.050 TID:00003BEC [Debug] <TNode> Finalizing AddOperations Connection:084070F0 Operations:1
2017-01-27 10:04:42.050 TID:00002B40 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 80
2017-01-27 10:04:42.050 TID:00001D24 [Debug] <TThreadNodeNotifyOperations> Sending 1 Operations to 5.172.237.241:2597
2017-01-27 10:04:42.050 TID:000004D4 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 81
2017-01-27 10:04:42.050 TID:00001D24 [Debug] <TNetServerClient> Sending: Autosend operation:ADD OPERATIONS id:989 errorcode:0 Size:259b (Data:237b) to 5.172.237.241:2597
2017-01-27 10:04:42.050 TID:00002760 [Debug] <TThreadNodeNotifyOperations> Starting Thread in pos 82
2017-01-27 10:04:42.057 TID:000039CC [Debug] <TBufferedNetTcpIpClientThread> Sent 259 bytes
2017-01-27 10:04:42.156 MAIN:00002834 [Debug] <TPCThread> Cannot Protect a critical section by TPCThreadList after 100 milis
2017-01-27 10:04:42.156 MAIN:00002834 [Debug] <TJSONRPCTcpIpClient> Sending JSON-RPC: {"method":"miner-notify","params":[{"block":56952,"version":1,"part1":"78DE0000CA022000586656AFFC7BCBCE6B5D9D8F90B2B8E5864822CE9781BD1C70AC9FA1517AE9B520006F5558E4E18F39E9F51865394CC5494428EA7D79AE754DCA4C31EBE12103D6F640420F00000000000100010001D9D430","payload_start":"696F676C6E786E76","part3":"5E4A4406918F7B3777801B5B7488FB9BF76ECA80066FDB1A32CEE674805411136DFC7C73A6776DBF4CEA694D3C261CBA023400A71C6A5776F5BC1B5AC2333676C8000000","target":819255553,"target_pow":"00000000000095937F0000000000000000000000000000000000000000000000","timestamp":1485507882}],"id":null}
2017-01-27 10:04:42.157 MAIN:00002834 [Debug] <TJSONRPCTcpIpClient> Sending JSON-RPC: {"method":"miner-notify","params":[{"block":56952,"version":1,"part1":"78DE0000CA022000586656AFFC7BCBCE6B5D9D8F90B2B8E5864822CE9781BD1C70AC9FA1517AE9B520006F5558E4E18F39E9F51865394CC5494428EA7D79AE754DCA4C31EBE12103D6F640420F00000000000100010001D9D430","payload_start":"696F676C6E786E76","part3":"5E4A4406918F7B3777801B5B7488FB9BF76ECA80066FDB1A32CEE674805411136DFC7C73A6776DBF4CEA694D3C261CBA023400A71C6A5776F5BC1B5AC2333676C8000000","target":819255553,"target_pow":"00000000000095937F0000000000000000000000000000000000000000000000","timestamp":1485507882}],"id":null}

What tells us this mh? Still don't get a schema or idea out of it.

[bensam1231]

I've mined with a pretty substantial amount of hashing power for about 12 hours and didn't find a block. I tried .4 for about 8 of those, .3 for about 4 of those, I also tried one wallet per rig with the same 8 character mining name and the same mining key (newest wallet), no block.

A lot of things could be happening here. Since there is no way to verify whether or not your mining setup is working till you're finding a block I'm basically possibly pissing hash away. A lot of people are basing profitability based off of cryptocompare, but I definitely don't think that's right. I'm pretty sure the amount you make is a lot lower then that. I should be hitting a block every half a hour. Given there are 12 blocks per hour and I've already been through 12 hours of those, it's safe to say something is fucked up.

Just a FYI, don't waste your time on this. Unless someone comes up with a guide down to the letter, this is a silly waste of time and energy. AMD seems to work, but that may be due to a large amount of AMD users... not necessarily because the miners/wallet are broken for Nvidia.

At this point I'm pretty certain if you get "Sending Error JSON RPC id () : Invalid payload" in your pascalcoin log then mining is not working.

The issue has to come from the java proxy.

That's incorrect. Not blaming you, but there is definitely a lot of misinformation flying around right now.

Alright, here's the CUDA miner with the working proxy: https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.02/CUDA_Pascal_v1.02.zip

VirusTotal: 0/55 https://virustotal.com/en/file/a7c451c3a19c4052cdf10d974da057f51bdb957734bb47c29115044741540648/analysis/1477111465/

These instructions are slightly different than the previous GPU miner! Take note!
1. You must already have PascalCoin installed. If you don't have it, download it from sourceforge here: https://sourceforge.net/projects/pascalcoin/. Once it is installed, run the PascalCoinWallet.exe provided in the download.
2. You must be using a 256-bit secp256k1 key. This is the default behavior of the PascalCoin wallet.
3. Your miner name must be exactly 8 characters long. The miner expects that the input is exactly 176 total bytes (which is achieved by using a secp256k1 key and a 10-character name)  NOTE: NOT 10 like before! 8 characters, because the last two will be used to identify each GPU!
4. You must have RPC enabled in your client (any port of your choosing, default is 4009)
5. You must run the proxy miner (PascalProxyv1.jar) in the same directory as the PascalCoinCUDA_ProxyMiner_smXX.exe file you run (everything is where it needs to be if you just extract the provided zip).

To run the proxy, just double-click on it on Windows, or in Linux do

Code:

java -jar /path/to/PascalProxyv1.jar

How does this work? The proxy connects to the PascalCoin wallet, grabs the current mining data, and then creates a headerout.txt file for the miner(s) to use. In return, the miner(s) write their shares to files called datainXX.txt, where XX is the GPU number (starting at 00, and going through 99). The miners use the device argument (0 if none is provided) to determine which device to use, and that's the file they write out to. The proxy waits for changes in those datainXX files, and then ferries the results back to the PascalCoin wallet.

You will notice that the PascalCoin wallet log constantly says "Sending Error JSON RPC id () : Error: Proof of work is higher than target" whenever you find a share. This is because the proxy's behavior is to submit any target 24000000 share, and since the target is 29xxxxxx, only about 1 in 2^5 = 32 shares will be an actual block. At a target of 2Axxxxxx, that'd be 2^6 or 64 shares. At a target of 2Bxxxxxx, that'll be 2^7 or 128 shares. etc.

Whenever I can get around to it, the OpenCL miner will work with this proxy.

Bottom line: you no longer need to rely on my modified PascalCoin wallet. You can use the official one from the developer, and run the proxy. The proxy won't work with old versions of the miner, but it will work with the version included in the zip linked above.

I spent a lot of time looking over everything in that thread, I'm leaning more towards payment calculators and estimations being insanely fucked up. People aren't calculating how likely they are to find a block correctly. All the AMD ethbabies from Ethereum and Equihash are riding it right now. I don't think net hashrate on the block explorer is correct... Nor is Cryptocompare or What reporting it correctly either. I think that's inherently a bug with dealing with this coin as it was never completely tested and vetted under load, something is buckling.

It does make me wonder if investors like finding the most fucked up coin they can just to make miners squirm for a good couple days before things get remotely ironed out.

[felixbrucker]

As KlausT mentioned, CUDA JSON-RPC issues are caused by Pascalproxyv2, it doesn't send "target" param to the miner.

Now we need that shitty proxy source... or a completely new miner  

Or if somebody has time he can read proxy console output and replace headeroutXX.txt with correct value for "target", currently it's 000000000 for every round...

anyone can see the src, thats not the problem, just decompile the jar it takes about 10 sec to google how

edit: here it is

http://pastebin.com/SrPkQRrQ
http://pastebin.com/0HPWetzi

So then what? We is the problem then

apparently no one knows how to fix it or has done it yet publicly, im not aware of any *fixed* proxy jar file
i myself also dont know about how all this works, i can code basic stuff in java, but thats about it

hopefully this all changes when ocminers pool is finished

[bathrobehero]

I've mined with a pretty substantial amount of hashing power for about 12 hours and didn't find a block. I tried .4 for about 8 of those, .3 for about 4 of those, I also tried one wallet per rig with the same 8 character mining name and the same mining key (newest wallet), no block.

A lot of things could be happening here. Since there is no way to verify whether or not your mining setup is working till you're finding a block I'm basically possibly pissing hash away. A lot of people are basing profitability based off of cryptocompare, but I definitely don't think that's right. I'm pretty sure the amount you make is a lot lower then that. I should be hitting a block every half a hour. Given there are 12 blocks per hour and I've already been through 12 hours of those, it's safe to say something is fucked up.

Just a FYI, don't waste your time on this. Unless someone comes up with a guide down to the letter, this is a silly waste of time and energy. AMD seems to work, but that may be due to a large amount of AMD users... not necessarily because the miners/wallet are broken for Nvidia.

At this point I'm pretty certain if you get "Sending Error JSON RPC id () : Invalid payload" in your pascalcoin log then mining is not working.

The issue has to come from the java proxy.

That's incorrect. Not blaming you, but there is definitely a lot of misinformation flying around right now.

Alright, here's the CUDA miner with the working proxy: https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.02/CUDA_Pascal_v1.02.zip

VirusTotal: 0/55 https://virustotal.com/en/file/a7c451c3a19c4052cdf10d974da057f51bdb957734bb47c29115044741540648/analysis/1477111465/

These instructions are slightly different than the previous GPU miner! Take note!
1. You must already have PascalCoin installed. If you don't have it, download it from sourceforge here: https://sourceforge.net/projects/pascalcoin/. Once it is installed, run the PascalCoinWallet.exe provided in the download.
2. You must be using a 256-bit secp256k1 key. This is the default behavior of the PascalCoin wallet.
3. Your miner name must be exactly 8 characters long. The miner expects that the input is exactly 176 total bytes (which is achieved by using a secp256k1 key and a 10-character name)  NOTE: NOT 10 like before! 8 characters, because the last two will be used to identify each GPU!
4. You must have RPC enabled in your client (any port of your choosing, default is 4009)
5. You must run the proxy miner (PascalProxyv1.jar) in the same directory as the PascalCoinCUDA_ProxyMiner_smXX.exe file you run (everything is where it needs to be if you just extract the provided zip).

To run the proxy, just double-click on it on Windows, or in Linux do

Code:

java -jar /path/to/PascalProxyv1.jar

How does this work? The proxy connects to the PascalCoin wallet, grabs the current mining data, and then creates a headerout.txt file for the miner(s) to use. In return, the miner(s) write their shares to files called datainXX.txt, where XX is the GPU number (starting at 00, and going through 99). The miners use the device argument (0 if none is provided) to determine which device to use, and that's the file they write out to. The proxy waits for changes in those datainXX files, and then ferries the results back to the PascalCoin wallet.

You will notice that the PascalCoin wallet log constantly says "Sending Error JSON RPC id () : Error: Proof of work is higher than target" whenever you find a share. This is because the proxy's behavior is to submit any target 24000000 share, and since the target is 29xxxxxx, only about 1 in 2^5 = 32 shares will be an actual block. At a target of 2Axxxxxx, that'd be 2^6 or 64 shares. At a target of 2Bxxxxxx, that'll be 2^7 or 128 shares. etc.

Whenever I can get around to it, the OpenCL miner will work with this proxy.

Bottom line: you no longer need to rely on my modified PascalCoin wallet. You can use the official one from the developer, and run the proxy. The proxy won't work with old versions of the miner, but it will work with the version included in the zip linked above.

I spent a lot of time looking over everything in that thread, I'm leaning more towards payment calculators and estimations being insanely fucked up. People aren't calculating how likely they are to find a block correctly. All the AMD ethbabies from Ethereum and Equihash are riding it right now. I don't think net hashrate on the block explorer is correct... Nor is Cryptocompare or What reporting it correctly either. I think that's inherently a bug with dealing with this coin as it was never completely tested and vetted under load, something is buckling.

It does make me wonder if investors like finding the most fucked up coin they can just to make miners squirm for a good couple days before things get remotely ironed out.

I see.


Well, after enabling logging in the wallet earlier today, I have a 4.2 MB log file without any "Error: Proof of work is higher than target" lines.

Instead, I have ~120 invalid payloads.

I tried every cuda miner I got my hands on, (even compiled it myself) every setting, miner name, miner name length, etc and it's the same.

I could might as well be missing something simple. I'm not even sure everyone with cuda miners have these invalid payload messages, but based on the guide it's clear that it's an error that shouldn't be there.

[ioglnx]

I think we are trying to hard :-D
The answer was already there.

It looks like the answer was already given:

You will notice that the PascalCoin wallet log constantly says "Sending Error JSON RPC id () : Error: Proof of work is higher than target" whenever you find a share. This is because the proxy's behavior is to submit any target 24000000 share, and since the target is 29xxxxxx, only about 1 in 2^5 = 32 shares will be an actual block. At a target of 2Axxxxxx, that'd be 2^6 or 64 shares. At a target of 2Bxxxxxx, that'll be 2^7 or 128 shares. etc

[Amph]

so it was just bad luck, the miner is working as intended, it make sense because few members found block with the nvidia miners espeically in the early stage

[ioglnx]

Here we go guys:

https://bitcointalk.org/index.php?topic=1583719.msg17644653#msg17644653

[bathrobehero]

I take everything back. I solved my issue.

I haven't changed the default, very long node name:



Now that I changed it, I'm mining fine with the expected "Proof of work is higher than target".

[sp_]

I adding rigs as we speak.I get around 780mhash on the 1070 and 460mhash on the 1060 3gb.

24 rigs added so far

I I find blocks I will add another 100 rigs.

[Amph]

I adding rigs as we speak.I get around 780mhash on the 1070 and 460mhash on the 1060 3gb.

24 rigs added so far

I I find blocks I will add another 100 rigs.

if you will not be able to find a block with 100 rig which is 500G then something is clearly wrong here...