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... |
|
|
|
I optimized the opencl miner a little bit. (2% - 5% expected) This is tested on an r9 280x If anyone interested, just replace the pascalsha.cl file in the miner directory https://ufile.io/0f267btc: 19RgeAw8PAU7WoP6zrWGiYuD78KmUhDmRx eth: 0x585ae8cf889282751b3c38c38a9c833d96d0dc59 happy mining Go fuck yourself with your fucking malware Unless he changed the link, how is a single .cl file is a malware? |
|
|
|
I use free WiFi at McDonalds and similar places. I'm in England, and I don't seem to have any delays or problems. I can even run a full node on a notebook computer.
It comes in waves, the slowdowns. Most of the time it's fine but sometimes for a few hours it gets bad. |
|
|
|
|
Yeah, I have the latest wallet (1.4.2), with 8 character workers and I tried several different builds that I compiled, the result is the same.
The only way to know for sure that it's not an issue is if we can get someone with an AMD card/miner chechking if they have that message or not. And from random pics I've seen it doesn't look like AMD miners have that error.
But from the guide I linked it does sound like the miner doesn't work ("Explanation: You received a JSON-RPC error. Error is explained in plain text. In above example, you've sent a "miner-submit" message with a not valid payload. Note that payload must be equal or greater than param "payload_start" provided on a "miner-notify" message.")
But then again I'm not a dev so I can only guess. I should have found a couple of blocks by now, but I might just be unlucky.
|
|
|
|
Blocks found is 0 though. If you use the proxy miner you need to set your miner name to 8 chars in wallet (options). After that start the proxy, then the miner and when it asks about miner prefix just put the 8 chars from the wallet.
They proxy will append 00, 01, etc on each GPU so you will always have 10 chars miner name.
My assumption is that you use bathr008 in miner and forgot to set same name in wallet.
Yeah, I know, I have the name added in the wallet. Can anyone with AMD card/miner check if they have the same message? |
|
|
|
I don't think the nvidia miner works. I get this from the PascalCointWallet.log every time there's a share found: TID:00001074 [Debug] <TBufferedNetTcpIpClientThread> Sent 158 bytes TID:00001074 [Debug] <TBufferedNetTcpIpClientThread> Received 116 bytes. Buffer length: 116 bytes TID:000019C4 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Invalid payload (bathr00804). Need start with: New Node 1/25/2017 7:31:35 - Pascal Coin Wallet & Explorer Build:1.4.1 Based on the "how to develop a GPU miner" guide it shouldn't happen: https://github.com/PascalCoin/PascalCoin/blob/master/HOWTO_DEVELOP_GPU_MINER_FOR_PASCALCOIN.txt#L44Have you tried .3 and .4? Something is working for Nvidia, either people are trolling or they're finding blocks with some random combinations of miners, clients, and luck. I use KlausT's fork but every version that I've tried so far does the same (including 1.03). |
|
|
|
I don't think the nvidia miner works. I get this from the PascalCointWallet.log every time there's a share found: TID:00001074 [Debug] <TBufferedNetTcpIpClientThread> Sent 158 bytes TID:00001074 [Debug] <TBufferedNetTcpIpClientThread> Received 116 bytes. Buffer length: 116 bytes TID:000019C4 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Invalid payload (bathr00804). Need start with: New Node 1/25/2017 7:31:35 - Pascal Coin Wallet & Explorer Build:1.4.1 Based on the "how to develop a GPU miner" guide it shouldn't happen: https://github.com/PascalCoin/PascalCoin/blob/master/HOWTO_DEVELOP_GPU_MINER_FOR_PASCALCOIN.txt#L44 |
|
|
|
|
TID:00001074 [Debug] <TBufferedNetTcpIpClientThread> Sent 158 bytes
TID:00001074 [Debug] <TBufferedNetTcpIpClientThread> Received 116 bytes. Buffer length: 116 bytes
TID:000019C4 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Invalid payload (bathr00804). Need start with: New Node 1/25/2017 7:31:35 - Pascal Coin Wallet & Explorer Build:1.4.1
I get this every time I find a share with cudaminer. Is it normal? Any AMD miner can check please if they get this in their PascalCointWallet.log?
Also, which private key option should I use, "Use a random existing key" or "Always mine with this key"? I mine to the same wallet from multiple computers.
|
|
|
|
You need 5 Gh/s to find a block as per the current net hashrate (1,500,000 Mh/s).
But according to whatmine the current net hash is 9 000 000 MH/s I base it on the block explorer: http://explorer.pascalcoin.org |
|
|
|
It is useless. To find a single block a day you need 130G = more than 300 R9 280x/RX470 cards!
With klaus_t's miner you get 800Mhash with the compute 52 build on the 1070. So if your calculation is right, you need 162,5 cards to get 1 block. per day. ($143) $0.88 per day per card. You need 5 Gh/s to find a block as per the current net hashrate (1,500,000 Mh/s). As per this difficulty calculation you need 6 Gh/s to find a block a day. Anyway, I should have found 6 blocks by now but I haven't found any. |
|
|
|
|
No blocks here in 2 days with cuda. Should have found 3 by now.
|
|
|
|
PASCAL MINING PROFITABILITY CALCULATOR
Check the target. Currently its 30416083
Take the first 2 bits "30" and change from HEX into DEC and you get 48
Take
2^48= 281,474,976,710,656 hashes
Now look at the 3rd bit, its 4. Take 4 / 16 = 0.25
Take 0.25 * 281,474,976,710,656 = 70,368,744,177,664
Add that to the original 2^48
281,474,976,710,656 + 70,368,744,177,664 = 351,843,720,888,320 hashes on average to find 1 block.
If your farm is 1 GH/s
351,843,720,888,320 / 1,000,000,000 = 351,843.72088832 seconds to find a block
Or 5864 Minutes to find a block
Or 97 Hours to find a block
Or 4.07 Days to find a block.
-----------------------------------------------------------
How reliable is this? Also, in case of the 3rd bit is 'A' does that mean 10? |
|
|
|
Edit: Using now different compiled verson of the CUDA Pascal miner and getting on GTx1080 around 1000MH/s on my Zotacs and 865MH/s on Asus Strix and 765MH on Zotac GTX1070 Mini.
Could you point me into the direction of that miner please? im not sure if its the same version, but i tested klausT's version (from github) and my 1070s hash with ~700mh/s I assume you're talking about cryptonight. We're talking about Pascalcoin. Sp_, this single file is the miner (it compiles and runs alone): https://github.com/Vorksholk/PascalCoin-CUDA/blob/master/kernel.cuso this should be optimized. This - https://github.com/KlausT/PascalCoin-CUDA/releasesOh, how did I missed that... Thanks! i was talking about PascalCoin, not Cryptonight Yeah, I realizeed now, my bad. |
|
|
|
Edit: Using now different compiled verson of the CUDA Pascal miner and getting on GTx1080 around 1000MH/s on my Zotacs and 865MH/s on Asus Strix and 765MH on Zotac GTX1070 Mini.
Could you point me into the direction of that miner please? im not sure if its the same version, but i tested klausT's version (from github) and my 1070s hash with ~700mh/s I assume you're talking about cryptonight. We're talking about Pascalcoin. Sp_, this single file is the miner (it compiles and runs alone): https://github.com/Vorksholk/PascalCoin-CUDA/blob/master/kernel.cuso this should be optimized. This - https://github.com/KlausT/PascalCoin-CUDA/releasesOh, how did I missed that... Thanks! |
|
|
|
Edit: Using now different compiled verson of the CUDA Pascal miner and getting on GTx1080 around 1000MH/s on my Zotacs and 865MH/s on Asus Strix and 765MH on Zotac GTX1070 Mini.
Could you point me into the direction of that miner please? im not sure if its the same version, but i tested klausT's version (from github) and my 1070s hash with ~700mh/s I assume you're talking about cryptonight. We're talking about Pascalcoin. Sp_, this single file is the miner (it compiles and runs alone): https://github.com/Vorksholk/PascalCoin-CUDA/blob/master/kernel.cuso this should be optimized. |
|
|
|
Edit: Using now different compiled verson of the CUDA Pascal miner and getting on GTx1080 around 1000MH/s on my Zotacs and 865MH/s on Asus Strix and 765MH on Zotac GTX1070 Mini.
Could you point me into the direction of that miner please? |
|
|
|
How much coins per day with 500 mhs ?
It's literally on the previous page. |
|
|
|
How do you get the cuda miner to work? I get only crashes.
I had to fix here and there and now it works, I even improved it a bit, but solo mining with such difficulty is no fun and even the hashrate reporting is crap for any serious optimisation work. Some parts should be rewritten. Would it be possible for the wallet/proxy to send much smaller chunks of work to the GPUs? I'd assume that would help with hashrate calculations if the cards could find shares frequently instead of one in every blue moon. That's the point of vardiff but doesn't apply to solo mining because you have to solve the whole block, not just a share. Lower diff just allows you to solve smaller shares with proportionally less work to even it out. I understand but for this coin you find nonces with the proxy which doesn't mean found blocks. The hashrate indication is based on the frequency on finding those nonces. GPU 4 submitted a share [payload: nonce: 396146189 timestamp: 1485418823] GPU 4 submitted a share [payload: nonce: -453467848 timestamp: 1485418827] GPU 1 submitted a share [payload: nonce: -1025482191 timestamp: 1485418887] GPU 0 submitted a share [payload: nonce: -144107511 timestamp: 1485418891] GPU 1 submitted a share [payload: nonce: -59821775 timestamp: 1485419002] GPU 4 submitted a share [payload: nonce: 1012223289 timestamp: 1485419047] |
|
|
|
How do you get the cuda miner to work? I get only crashes.
I had to fix here and there and now it works, I even improved it a bit, but solo mining with such difficulty is no fun and even the hashrate reporting is crap for any serious optimisation work. Some parts should be rewritten. Would it be possible for the wallet/proxy to send much smaller chunks of work to the GPUs? I'd assume that would help with hashrate calculations if the cards could find shares frequently instead of one in every blue moon. |
|
|
|
|
Show Posts
