[PASC] PascalCoin: Induplicatable NFT

[mxhwr]

i think many people concern is with how exchanges are to receive the coins. new coin , new challenges, new projects only can get better. once this is possible we will see massive interest. its whats so exciting about this coin, things never been tried before.

[thedreamer]

How can I mine PASCAL on my laptop? Will it be profitable?

No. Read the past few pages back.

[Vorksholk]

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.

[go6ooo1212]

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.

Nice summary , especially the last one. Would you come in the slack channel...

[ICOcountdown.com]

Hello everyone I have made a telegram group so everyone can communicate.

Download the software for phone or desktop here: https://telegram.org/

Join here: http://telegram.me/pascalcoin

[xhomerx10]

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?

[ICOcountdown.com]

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.

[Vorksholk]

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

[xhomerx10]

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

 I saw you had said you would release it but I wasn't seeing any different speeds with v3.
Thanks very much!

[Vorksholk]

Also, source code for anyone who wants it: https://github.com/Vorksholk/PascalCoin-CUDA/blob/master/kernel.cu

And if people just want to download the new miner binaries without grabbing the whole PascalCoin package from filedropper: https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.00/CUDA_Pascal_v1.00.zip

[Eyedol-X]

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

Awesome, totally trying to figure out how to make this work here since I have 2x GTX 770's in one of my systems. I think I had v3 working but didn't wait long enough for a block, just downloaded v4 and rebooted.

I had to update my mining key and create a new one that fits your requirements. I then set the wallet to always mine with that key. I hope this is sufficient.

[Vorksholk]

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

Awesome, totally trying to figure out how to make this work here since I have 2x GTX 770's in one of my systems. I think I had v3 working but didn't wait long enough for a block, just downloaded v4 and rebooted.

I had to update my mining key and create a new one that fits your requirements. I then set the wallet to always mine with that key. I hope this is sufficient.

Did you make sure your miner name is exactly 10 characters, and is the miner running directly from the same folder as the custom PascalCoin wallet? If so, you're probably good to go!

[Arrakeen]

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

Awesome, totally trying to figure out how to make this work here since I have 2x GTX 770's in one of my systems. I think I had v3 working but didn't wait long enough for a block, just downloaded v4 and rebooted.

I had to update my mining key and create a new one that fits your requirements. I then set the wallet to always mine with that key. I hope this is sufficient.

Did you make sure your miner name is exactly 10 characters, and is the miner running directly from the same folder as the custom PascalCoin wallet? If so, you're probably good to go!

What could be causing such a rapid memory leak?  Just curious, as I know nothing about the code behind mining programs.  Thanks in advance, and great work + good luck !

[Eyedol-X]

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

Awesome, totally trying to figure out how to make this work here since I have 2x GTX 770's in one of my systems. I think I had v3 working but didn't wait long enough for a block, just downloaded v4 and rebooted.

I had to update my mining key and create a new one that fits your requirements. I then set the wallet to always mine with that key. I hope this is sufficient.

Did you make sure your miner name is exactly 10 characters, and is the miner running directly from the same folder as the custom PascalCoin wallet? If so, you're probably good to go!

Yes and Yes, I set my miner name in options to be GTX1234567 and I built a key using a similar style name.

Appreciate everything you are doing here for the community.

[vibajajo64]

Did you make sure your miner name is exactly 10 characters, and is the miner running directly from the same folder as the custom PascalCoin wallet? If so, you're probably good to go!

So do you open the original PascalCoin wallet or the custom PascalCoin wallet?

[Eyedol-X]

So v3 showed me Hash Rates and Total's

v4 seems to be sitting there and occasionally shows Real: 67XXXXXXXXXX across the screen.

Am I just not waiting long enough or did I miss something?

Benchmark in v4 is noticeably faster.

[Eyedol-X]

So v3 showed me Hash Rates and Total's

v4 seems to be sitting there and occasionally shows Real: 67XXXXXXXXXX across the screen.

Am I just not waiting long enough or did I miss something?

Benchmark in v4 is noticeably faster.

Found a nonce but showed 0 hash rate and total 0

GPU Usage shows 98% so it's definitely doing something

[DaniellPlasmmer]

I see a great interest here in mining this criptocurrency. I'm thinking why.

[Eyedol-X]

So v3 showed me Hash Rates and Total's

v4 seems to be sitting there and occasionally shows Real: 67XXXXXXXXXX across the screen.

Am I just not waiting long enough or did I miss something?

Benchmark in v4 is noticeably faster.

Found a nonce but showed 0 hash rate and total 0

GPU Usage shows 98% so it's definitely doing something

Well I switched back to v3 and it instantly started working again... not sure whats up with v4

I'm using SM30

[Eyedol-X]

So v3 showed me Hash Rates and Total's

v4 seems to be sitting there and occasionally shows Real: 67XXXXXXXXXX across the screen.

Am I just not waiting long enough or did I miss something?

Benchmark in v4 is noticeably faster.

Found a nonce but showed 0 hash rate and total 0

GPU Usage shows 98% so it's definitely doing something

Well I switched back to v3 and it instantly started working again... not sure whats up with v4

I'm using SM30

Some additional testing of V4:

I can confirm argument for additional GPU's doesn't work on V4, works fine on V3