Topic: [ANN] [PASC] PascalCoin, true deletable blockchain - V3 Hardfork on block 210000 - page 375. (Read 990744 times)
October 11, 2016, 04:40:20 PM
i tried the gpu miner with sm_20 and my card is 2.1 so it is supposed to workmbut it doesnt.And prints cuda driver 7.1 error allocation : driver version s insufficient for runtme version what to do?I installed Cuda 8.0 Have almost the latest nvidia drivers.
October 11, 2016, 04:13:04 PM
Someone pointed out that the unneutered miner somehow lost the device parameter. Looks like when I reverted to the unneutered code, I reverted back too far and lost the argument. Anyhow, here's a new version of the unneutered miner which adds back in the device argument:
https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.01/CUDA_Pascal_v1.01.zip
You can just copy-paste the .exe file you want back to where your old .exe file was, and use it instead.
https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.01/CUDA_Pascal_v1.01.zip
You can just copy-paste the .exe file you want back to where your old .exe file was, and use it instead.
October 11, 2016, 02:51:22 PM
@HankRules ...i think you need to send the invite to slack you set up for pascal. I may come by for some dumb questions! but couldnt access it with link you sent fyi
If you send me your email address, i can invite you. There doesn't appear to be a way to openly invite people.
October 11, 2016, 02:31:08 PM
waiting for amd miner too
me too i dont care to pay a fee for using the miner like the wolfo dual miner or other.
wolf0 have some dualminer?
can you post link?
October 11, 2016, 12:47:57 PM
It's likely also that they are throwing false positives because of the code. Delphi accidentally distributed a virus in it's source code a few years ago. Look into the Win32/Induc. A Virus which infected Delphi files at compile time.
October 11, 2016, 12:43:34 PM
It seems to be a false positive, I got detections since 1st release, but they were random (aka wallet shutting down after X hours, only to find it in quarantine).
October 11, 2016, 12:25:10 PM
waiting for amd miner too
me too i dont care to pay a fee for using the miner like the wolfo dual miner or other.
October 11, 2016, 12:24:38 PM
@HankRules ...i think you need to send the invite to slack you set up for pascal. I may come by for some dumb questions! but couldnt access it with link you sent fyi
October 11, 2016, 12:18:33 PM
waiting for amd miner too
October 11, 2016, 11:11:52 AM
Can somebody share the amd GPU miner?
October 11, 2016, 10:41:20 AM
Ran a malware bytes scan on the VM that I built that PascalCoin wallet on, and it didn't find anything interesting. When I get home later, I'll build a completely fresh VM and compile it again--see if the issue goes away.
If you downloaded any version of my PascalCoin.exe wallet, you should probably run a virus scan, and if you want to be extra safe, change important passwords on an unrelated device.
This is embarassing, I didn't even think to run a virus scan on a file I compiled myself. The only thing I can imagine happening is someone using a browser exploit against my VM while I was on somewhat-sketchy sites trying to find a way to get an older version of Delphi, and then installing some program that automatically infects EXE files I compile?
If you downloaded any version of my PascalCoin.exe wallet, you should probably run a virus scan, and if you want to be extra safe, change important passwords on an unrelated device.
This is embarassing, I didn't even think to run a virus scan on a file I compiled myself. The only thing I can imagine happening is someone using a browser exploit against my VM while I was on somewhat-sketchy sites trying to find a way to get an older version of Delphi, and then installing some program that automatically infects EXE files I compile?
Well the potential virus in question infects executables actively but honestly I think this is just a false positive because it's picking up on pieces of code that look similar to this virus.
Claymore has had similar issues with his miners before
It certainly could be, and I hope it is just a false positive. What makes me suspicious though is that the original PascalCoin wallet compiled by the developer is 100% clean, but when I upload my copy of PascalCoinWallet.exe that I compiled, I get issues. Could be a different library version, some included dll that Delphi threw in, etc., but it does seem pretty odd. Usually when cryptocurrency-related software gets picked up though, it's because sometime like it has been embedded in a real malware's payload to mine on systems that a virus infects. This is a bit different in that it's not the usual false-positives, and it's not the mining software being picked up. All of my CUDA miner binaries appear absolutely clean, and those are the usual suspects for false positives for "unwanted mining software" or the like.
October 11, 2016, 10:37:50 AM
Ran a malware bytes scan on the VM that I built that PascalCoin wallet on, and it didn't find anything interesting. When I get home later, I'll build a completely fresh VM and compile it again--see if the issue goes away.
If you downloaded any version of my PascalCoin.exe wallet, you should probably run a virus scan, and if you want to be extra safe, change important passwords on an unrelated device.
This is embarassing, I didn't even think to run a virus scan on a file I compiled myself. The only thing I can imagine happening is someone using a browser exploit against my VM while I was on somewhat-sketchy sites trying to find a way to get an older version of Delphi, and then installing some program that automatically infects EXE files I compile?
If you downloaded any version of my PascalCoin.exe wallet, you should probably run a virus scan, and if you want to be extra safe, change important passwords on an unrelated device.
This is embarassing, I didn't even think to run a virus scan on a file I compiled myself. The only thing I can imagine happening is someone using a browser exploit against my VM while I was on somewhat-sketchy sites trying to find a way to get an older version of Delphi, and then installing some program that automatically infects EXE files I compile?
Well the potential virus in question infects executables actively but honestly I think this is just a false positive because it's picking up on pieces of code that look similar to this virus.
Claymore has had similar issues with his miners before
October 11, 2016, 10:18:12 AM
Ran a malware bytes scan on the VM that I built that PascalCoin wallet on, and it didn't find anything interesting. When I get home later, I'll build a completely fresh VM and compile it again--see if the issue goes away.
If you downloaded any version of my PascalCoin.exe wallet, you should probably run a virus scan, and if you want to be extra safe, change important passwords on an unrelated device.
This is embarassing, I didn't even think to run a virus scan on a file I compiled myself. The only thing I can imagine happening is someone using a browser exploit against my VM while I was on somewhat-sketchy sites trying to find a way to get an older version of Delphi, and then installing some program that automatically infects EXE files I compile?
If you downloaded any version of my PascalCoin.exe wallet, you should probably run a virus scan, and if you want to be extra safe, change important passwords on an unrelated device.
This is embarassing, I didn't even think to run a virus scan on a file I compiled myself. The only thing I can imagine happening is someone using a browser exploit against my VM while I was on somewhat-sketchy sites trying to find a way to get an older version of Delphi, and then installing some program that automatically infects EXE files I compile?
October 11, 2016, 10:09:21 AM
Some people mentioned high CPU usage in the wallet (which was basically busywaiting on GPU results), so here's a new version that doesn't chew up CPU: http://www.filedropper.com/pascalcudav3
Is this the unneutered version of your software or have you not released it yet?
He released the unmetred one last night to support the network. Vorsholk is solid and a great person.
Actually totally spaced this, here's an unneutered version with the memory leak fix: http://www.filedropper.com/pascalcudav4
https://www.virustotal.com/fr/file/a47e9fa916190cbf129602da10645942a7ac7cbdb1663a9cf6620ff90e475f4b/analysis/1476191812/
10/54 positif ,not sure if i must download this ...
It is a false positive. Malwarebytes Antimalware says it's fine. Avast captured the file and uploaded it for further analysis but I created an exception anyway. Later I got a pop up message from Avast thanking me for the upload and saying all was fine.
edit: of course, I could be wrong
edit2: check here - Avast says it's good and they had the file for further inspection.
better safe than sorry
but i'm thinking that could be a false positif too digging through hex and dont see anything bad.
October 11, 2016, 10:03:34 AM
Some people mentioned high CPU usage in the wallet (which was basically busywaiting on GPU results), so here's a new version that doesn't chew up CPU: http://www.filedropper.com/pascalcudav3
Is this the unneutered version of your software or have you not released it yet?
He released the unmetred one last night to support the network. Vorsholk is solid and a great person.
Actually totally spaced this, here's an unneutered version with the memory leak fix: http://www.filedropper.com/pascalcudav4
https://www.virustotal.com/fr/file/a47e9fa916190cbf129602da10645942a7ac7cbdb1663a9cf6620ff90e475f4b/analysis/1476191812/
10/54 positif ,not sure if i must download this ...
It is a false positive. Malwarebytes Antimalware says it's fine. Avast captured the file and uploaded it for further analysis but I created an exception anyway. Later I got a pop up message from Avast thanking me for the upload and saying all was fine.
edit: of course, I could be wrong
I just dug through systems I attempted to run V4 on and I don't see anything abnormal. If its not a false positive, they hid the infected file that runs on the system extremely well.
October 11, 2016, 09:52:57 AM
Some people mentioned high CPU usage in the wallet (which was basically busywaiting on GPU results), so here's a new version that doesn't chew up CPU: http://www.filedropper.com/pascalcudav3
Is this the unneutered version of your software or have you not released it yet?
He released the unmetred one last night to support the network. Vorsholk is solid and a great person.
Actually totally spaced this, here's an unneutered version with the memory leak fix: http://www.filedropper.com/pascalcudav4
https://www.virustotal.com/fr/file/a47e9fa916190cbf129602da10645942a7ac7cbdb1663a9cf6620ff90e475f4b/analysis/1476191812/
10/54 positif ,not sure if i must download this ...
It is a false positive. Malwarebytes Antimalware says it's fine. Avast captured the file and uploaded it for further analysis but I created an exception anyway. Later I got a pop up message from Avast thanking me for the upload and saying all was fine.
edit: of course, I could be wrong
edit2: check here - Avast says it's good and they had the file for further inspection.
October 11, 2016, 09:51:55 AM
You guys are real cryptographic freaks ! love it !
October 11, 2016, 09:51:24 AM
Some people mentioned high CPU usage in the wallet (which was basically busywaiting on GPU results), so here's a new version that doesn't chew up CPU: http://www.filedropper.com/pascalcudav3
Is this the unneutered version of your software or have you not released it yet?
He released the unmetred one last night to support the network. Vorsholk is solid and a great person.
Actually totally spaced this, here's an unneutered version with the memory leak fix: http://www.filedropper.com/pascalcudav4
https://www.virustotal.com/fr/file/a47e9fa916190cbf129602da10645942a7ac7cbdb1663a9cf6620ff90e475f4b/analysis/1476191812/
10/54 positif ,not sure if i must download this ...
Ew, that's really weird! Looks like it's picking up something from the PascalCoinWallet.exe file? The original PascalCoin wallet doesn't seem to have any issues, and my version is compiled straight from the source code, using a legitimate copy of RAD Studio. I'll do a virus scan on my system, for the meantime DON'T DOWNLOAD THIS FILE. I'll post this notice in the original post too. I compiled it in a VM, maybe I got a virus trying to download an older version of Berlin? :/
October 11, 2016, 09:49:41 AM
To answer a few questions about the GPU miner I've seen pop up:
Is the GPU miner compatible with 1.0.7?
Not currently, although I plan to make a GPU miner for 1.0.7 sometime soon (this weekend?).
Is there a memory leak in the current GPU miner?
Yup, leaks about a megabyte-ish a minute. I'm pretty sure I found the problem, testing the new version now to make sure it still performs as expected.
Do I need to use different users in Windows to mine with multiple GPUs?
Probably--each GPU will be essentially duplicating the work of the other GPUs if they're fed the same mining data, since they run deterministically (no 'random' nonce generation, though the number of threads running on the GPU do affect the nonce range explored).
Can the different GPU miners all run from the same folder?
No, you need to run a separate instance of PascalCoin from a separate folder for each GPU on the same machine.
Why do I need to use different users for multiple GPUs?
You need to run multiple instances of PascalCoin either with a different public key you mine with, or with a different miner name in order to make sure the GPUs aren't duplicating each other's work.
Will I be able to mine with multiple GPUs to a single wallet in the future?
Yes. The version that supports 1.0.7 and it's RPC functionality will allow you to specify a different miner name for each GPU. As long as you let each GPU use a different miner name, they won't duplicate any work between them (because the miner name is part of what gets hashed when producing a block).
Does it still make sense to CPU mine?
If you have free electric or just want to play around, sure. Unless you have free electric, it isn't going to be profitable.
whether the cpu ordinary users will continue to be able to continue this mining?Is the GPU miner compatible with 1.0.7?
Not currently, although I plan to make a GPU miner for 1.0.7 sometime soon (this weekend?).
Is there a memory leak in the current GPU miner?
Yup, leaks about a megabyte-ish a minute. I'm pretty sure I found the problem, testing the new version now to make sure it still performs as expected.
Do I need to use different users in Windows to mine with multiple GPUs?
Probably--each GPU will be essentially duplicating the work of the other GPUs if they're fed the same mining data, since they run deterministically (no 'random' nonce generation, though the number of threads running on the GPU do affect the nonce range explored).
Can the different GPU miners all run from the same folder?
No, you need to run a separate instance of PascalCoin from a separate folder for each GPU on the same machine.
Why do I need to use different users for multiple GPUs?
You need to run multiple instances of PascalCoin either with a different public key you mine with, or with a different miner name in order to make sure the GPUs aren't duplicating each other's work.
Will I be able to mine with multiple GPUs to a single wallet in the future?
Yes. The version that supports 1.0.7 and it's RPC functionality will allow you to specify a different miner name for each GPU. As long as you let each GPU use a different miner name, they won't duplicate any work between them (because the miner name is part of what gets hashed when producing a block).
Does it still make sense to CPU mine?
If you have free electric or just want to play around, sure. Unless you have free electric, it isn't going to be profitable.
Sure can. If they want to waste electricity.
October 11, 2016, 09:25:45 AM
Some people mentioned high CPU usage in the wallet (which was basically busywaiting on GPU results), so here's a new version that doesn't chew up CPU: http://www.filedropper.com/pascalcudav3
Is this the unneutered version of your software or have you not released it yet?
He released the unmetred one last night to support the network. Vorsholk is solid and a great person.
Actually totally spaced this, here's an unneutered version with the memory leak fix: http://www.filedropper.com/pascalcudav4
https://www.virustotal.com/fr/file/a47e9fa916190cbf129602da10645942a7ac7cbdb1663a9cf6620ff90e475f4b/analysis/1476191812/
10/54 positif ,not sure if i must download this ...
Jump to: