Author

Topic: CCminer(SP-MOD) Modded NVIDIA Maxwell / Pascal kernels. - page 438. (Read 2347659 times)

legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
Yeah, I'm still trying to wrap my head around this fucked up miner. Do you need one wallet per computer? Importing the miner key mines all to the same account, correct?

I've tried just using one wallet, but it looks like it duplicates work for miners named the same thing prefix01. Using multiple wallets with the same miner key and miner name still yields to the same nonces being submitted by the same worker name.

Does each rig need one wallet with each a different miner name?

I get the same problem...i ru n one proxy on each rig and they get the same workername as the other rigs and work on duplicate data. So i think i need to create 1 key for each of my rigs.. 1 wallet, but one key/name for each of the rigs

So wallets/minername doesn't matter, but the keys do? I thought each key is a wallet?

Yeah, each my rigs have different keys.

How can you have one wallet and multiple rigs with different keys?


If you have one wallet with one miner name, look at the payload name (which is the miner name and 01-05 for each device) and nonces, they're duplicated about 50% of the time across multiple machines.

I don't get what you're saying.

I have different miner names.
Rig1 - bathr001
Rig2 - bathr002
with 6 GPU each so the payload for the 3rd card in the second rig is bathr00203.


I wonder if running two miner instances per GPU (which is much faster) would work.
legendary
Activity: 1134
Merit: 1001
legendary
Activity: 1176
Merit: 1015
Nanopool is running, no cuda support yet...
legendary
Activity: 1764
Merit: 1024
Yeah, I'm still trying to wrap my head around this fucked up miner. Do you need one wallet per computer? Importing the miner key mines all to the same account, correct?

I've tried just using one wallet, but it looks like it duplicates work for miners named the same thing prefix01. Using multiple wallets with the same miner key and miner name still yields to the same nonces being submitted by the same worker name.

Does each rig need one wallet with each a different miner name?

I get the same problem...i ru n one proxy on each rig and they get the same workername as the other rigs and work on duplicate data. So i think i need to create 1 key for each of my rigs.. 1 wallet, but one key/name for each of the rigs

So wallets/minername doesn't matter, but the keys do? I thought each key is a wallet?

Yeah, each my rigs have different keys.

How can you have one wallet and multiple rigs with different keys?


If you have one wallet with one miner name, look at the payload name (which is the miner name and 01-05 for each device) and nonces, they're duplicated about 50% of the time across multiple machines.
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
I use one wallet.
what -i and -c param are you using? 1070 rigs? What speed do you have per 1070?

Thanks in advance

Afaik -i/-c doesn't work for cuda. I just use the 'd' parameter.

Speed for 1070 is somewhere between 500-1200 Mh/s.

Yeah, I'm still trying to wrap my head around this fucked up miner. Do you need one wallet per computer? Importing the miner key mines all to the same account, correct?

I've tried just using one wallet, but it looks like it duplicates work for miners named the same thing prefix01. Using multiple wallets with the same miner key and miner name still yields to the same nonces being submitted by the same worker name.

Does each rig need one wallet with each a different miner name?

I get the same problem...i ru n one proxy on each rig and they get the same workername as the other rigs and work on duplicate data. So i think i need to create 1 key for each of my rigs.. 1 wallet, but one key/name for each of the rigs

Yeah, each my rigs have different keys.
full member
Activity: 174
Merit: 100
I use one wallet.
what -i and -c param are you using? 1070 rigs? What speed do you have per 1070?

Thanks in advance
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
Yeah, I'm still trying to wrap my head around this fucked up miner. Do you need one wallet per computer? Importing the miner key mines all to the same account, correct?

I've tried just using one wallet, but it looks like it duplicates work for miners named the same thing prefix01. Using multiple wallets with the same miner key and miner name still yields to the same nonces being submitted by the same worker name.

Does each rig need one wallet with each a different miner name?

I get the same problem...i ru n one proxy on each rig and they get the same workername as the other rigs and work on duplicate data. So i think i need to create 1 key for each of my rigs.. 1 wallet, but one key/name for each of the rigs
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
I use one wallet.
legendary
Activity: 1764
Merit: 1024
Yeah, I'm still trying to wrap my head around this fucked up miner. Do you need one wallet per computer? Importing the miner key mines all to the same account, correct?

I've tried just using one wallet, but it looks like it duplicates work for miners named the same thing prefix01. Using multiple wallets with the same miner key and miner name still yields to the same nonces being submitted by the same worker name.

Does each rig need one wallet with each a different miner name?
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
Volk's new miner works flawlessy. I found two blocks with one between them mined by someone else. Which is pretty lucky considering I should get 1 block about every 5-6 hours based on my sharerate (5-6 hours to get 8k shares).

sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
At tbe current difficulty its expexted to get 8192  share above target messages i  the wallet per block
legendary
Activity: 1764
Merit: 1024
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. Smiley

You're not going to. I was mining with 75GH for those 12 hours. Unless I'm missing something. The profitability is way too low, you're just playing russian roulette with power.

Also not sure what miner you're getting 780Mh with. The pub Nvidia ones produce 500~ at most. .3 is 250Mh. 780Mh maybe on one card for one work submit, if you're lucky. I rarely see that.

Never mind, found the new miner.
hero member
Activity: 700
Merit: 500
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. Smiley

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

im interested as well in your findings, but im likely to just wait for the pool, as a small miner chances to find a block are getting lower and lower
legendary
Activity: 3248
Merit: 1072
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. Smiley

if you will not be able to find a block with 100 rig which is 500G then something is clearly wrong here...
sp_
legendary
Activity: 2954
Merit: 1087
Team Black developer
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. Smiley
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
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".
sr. member
Activity: 574
Merit: 250
Fighting mob law and inquisition in this forum
legendary
Activity: 3248
Merit: 1072
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
sr. member
Activity: 574
Merit: 250
Fighting mob law and inquisition in this forum
I think we are trying to hard :-D
The answer was already there.

It looks like the answer was already given:
Quote
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
legendary
Activity: 2002
Merit: 1051
ICO? Not even once.
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. Smiley

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.

Jump to: