[PASC] PascalCoin: Induplicatable NFT

[kahir]

next step for pascal is pool

[1713481121]

1713481121

[ICOcountdown.com]

next step for pascal is pool

It's like developing for Bitcoin all over again, very happy that the community is making strides and the pascal developer is pushing out continuous and serious updates. I believe this project has huge potential because of it's correlation with cryptography and typical legacy system infrastructure.

[PascalCoin]

next step for pascal is pool

It's like developing for Bitcoin all over again, very happy that the community is making strides and the pascal developer is pushing out continuous and serious updates. I believe this project has huge potential because of it's correlation with cryptography and typical legacy system infrastructure.

Mr. Satoshi Nakamoto did not had a furious comunity like yours in first 2 months of Bitcoin life ... 

I'm developing all over again, it's true, but I'll not develop apps for third partys use. For example: App for a pool.
I'll only develop RPC calls to be accessible for third partys (exchanges, pools or new kind of applications based on account system of PascalCoin)

If somebody wants to create a pool, will need to develop itself a pool server, like Vorksholk developed a GPU miner.

[proletariat]

next step for pascal is pool

It's like developing for Bitcoin all over again, very happy that the community is making strides and the pascal developer is pushing out continuous and serious updates. I believe this project has huge potential because of it's correlation with cryptography and typical legacy system infrastructure.

Mr. Satoshi Nakamoto did not had a furious comunity like yours in first 2 months of Bitcoin life ... 

I'm developing all over again, it's true, but I'll not develop apps for third partys use. For example: App for a pool.
I'll only develop RPC calls to be accessible for third partys (exchanges, pools or new kind of applications based on account system of PascalCoin)

If somebody wants to create a pool, will need to develop itself a pool server, like Vorksholk developed a GPU miner.

So this is where the real OCminer chimes in. So guys, start harassing him about it 

[Vorksholk]

OpenCL miner is here!

https://github.com/Vorksholk/PascalCoin-OpenCL/releases/download/v1.00/PascalCoin_OpenCL_ProxyMiner_v1.zip

Getting about 550 MH/s on an RX 480 with stock clocks.

For anyone thinking about CPU mining, an i7-5820k overclocked used to get about 8 MH/s.

Instructions very similar to PascalCoin CUDA Proxy miner. Here they are:

Code:

To use this miner:

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 (PascalProxyv2.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). For most people, the host should be 127.0.0.1, and the port should be 4009. Enter the same 8-character miner name you put in your PascalCoin wallet.

6. Open one or more (one for each GPU) copy of PascalCoinOpenCL_ProxyMiner.exe by cd-ing to this directory in a command prompt, and running PascalCoinOpenCL_ProxyMiner.exe.
The miner takes four arguments: device (d), platform (p), intensity (i), and cyclesize (c).

For example: PascalCoinOpenCL_ProxyMiner.exe d0 p0 i23 c50
would run the miner on platform 0, device 0, with an intensity of 23 and a cyclesize of 50.

Higher intensities are more demanding on the GPU. Additionally, too high of an intensity can cause the miner to actually decrease in effective hashrate.

The cyclesize has a minimal affect on hashrate generally.

Unless you have a special setup (like NVidia and AMD cards in the same system), your platform is probably 0. You can determine which platform and device to use from the output at the original miner's start.

You can also run the benchmark miner (in the Benchmark folder) to try out different devices and intensity/cyclesize arguments. If you are compiling from source and want to make the benchmark version instead of the normal mining version, comment out the lines responsible for writing to the datainXX.txt file, (optionally) change the header file you read from to a single name regardless of device name, change the line

printf("Found nonce: %08x    T: %08x    Hashrate: %.3f MH/s   Total: %d\n", nonce, timestamp, (((((double)totalNonces) * 4 * 16 * 16 * 16 * 16) / (4)) / (((double)getTimeMillis() - start) / 1000)), totalNonces);

to

printf("Found nonce: %08x    T: %08x    Hashrate: %.3f MH/s   Total: %d\n", nonce, timestamp, (((((double)totalNonces) * 4 * 16 * 8) / (4)) / (((double)getTimeMillis() - start) / 1000)), totalNonces);


 and modify the .cl code by changing the lines:

uint targetX = h0 & 0xFFFFFFFF;
uint targetY = h1 & 0xF0000000;
to
uint targetX = h0 & 0xFFFFFF70;
uint targetY = h1 & 0x00000000;

This essentially lets the code find nonces 512 times faster, and accounts for the 512-times-faster-sharerate by reducing how many hashes it expects each nonce solve to take by a factor of 512, while removing the overhead of writing files (since writing a few files a second may cause it to be slower).

If you notice your miner finding several of the same nonce, try lowering the intensity and/or cyclesize (because you're sending so much work to the GPU that it can't get a timestamp often enough, so it exhausts the 4-ish billion possible nonces (~4 GH), and starte repeating work).

[PascalCoin]

OpenCL miner is here!

Aplause!

Very good job Vorksholk!

[hankrules]

When does VorksholkCoin come out?

[thedreamer]

Vork,

I'm playing with your miner, after a few minutes of mining, it crashes and I get this in the debug window :
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   PascalCoinOpenCL_ProxyMiner.exe
  Application Version:   0.0.0.0
  Application Timestamp:   580c14f1
  Fault Module Name:   StackHash_385c
  Fault Module Version:   6.3.9600.18233
  Fault Module Timestamp:   56bb4e1d
  Exception Code:   c0000374
  Exception Offset:   PCH_ED_FROM_ntdll+0x0003C7EC
  OS Version:   6.3.9600.2.0.0.256.48
  Locale ID:   1033
  Additional Information 1:   385c
  Additional Information 2:   385cca563338e9b5fd41b5d5b84858e6
  Additional Information 3:   2413
  Additional Information 4:   241304d9adad72f983c42a32fcdd4b40

I'm using Windows 8.1 Pro, 64bit with RX480 8GB cards.

[lobstermd]

OpenCL miner is here!

https://github.com/Vorksholk/PascalCoin-OpenCL/releases/download/v1.00/PascalCoin_OpenCL_ProxyMiner_v1.zip

Getting about 550 MH/s on an RX 480 with stock clocks.

For anyone thinking about CPU mining, an i7-5820k overclocked used to get about 8 MH/s.

Instructions very similar to PascalCoin CUDA Proxy miner. Here they are:

Code:

To use this miner:

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 (PascalProxyv2.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). For most people, the host should be 127.0.0.1, and the port should be 4009. Enter the same 8-character miner name you put in your PascalCoin wallet.

6. Open one or more (one for each GPU) copy of PascalCoinOpenCL_ProxyMiner.exe by cd-ing to this directory in a command prompt, and running PascalCoinOpenCL_ProxyMiner.exe.
The miner takes four arguments: device (d), platform (p), intensity (i), and cyclesize (c).

For example: PascalCoinOpenCL_ProxyMiner.exe d0 p0 i23 c50
would run the miner on platform 0, device 0, with an intensity of 23 and a cyclesize of 50.

Higher intensities are more demanding on the GPU. Additionally, too high of an intensity can cause the miner to actually decrease in effective hashrate.

The cyclesize has a minimal affect on hashrate generally.

Unless you have a special setup (like NVidia and AMD cards in the same system), your platform is probably 0. You can determine which platform and device to use from the output at the original miner's start.

You can also run the benchmark miner (in the Benchmark folder) to try out different devices and intensity/cyclesize arguments. If you are compiling from source and want to make the benchmark version instead of the normal mining version, comment out the lines responsible for writing to the datainXX.txt file, (optionally) change the header file you read from to a single name regardless of device name, change the line

printf("Found nonce: %08x    T: %08x    Hashrate: %.3f MH/s   Total: %d\n", nonce, timestamp, (((((double)totalNonces) * 4 * 16 * 16 * 16 * 16) / (4)) / (((double)getTimeMillis() - start) / 1000)), totalNonces);

to

printf("Found nonce: %08x    T: %08x    Hashrate: %.3f MH/s   Total: %d\n", nonce, timestamp, (((((double)totalNonces) * 4 * 16 * 8) / (4)) / (((double)getTimeMillis() - start) / 1000)), totalNonces);


 and modify the .cl code by changing the lines:

uint targetX = h0 & 0xFFFFFFFF;
uint targetY = h1 & 0xF0000000;
to
uint targetX = h0 & 0xFFFFFF70;
uint targetY = h1 & 0x00000000;

This essentially lets the code find nonces 512 times faster, and accounts for the 512-times-faster-sharerate by reducing how many hashes it expects each nonce solve to take by a factor of 512, while removing the overhead of writing files (since writing a few files a second may cause it to be slower).

If you notice your miner finding several of the same nonce, try lowering the intensity and/or cyclesize (because you're sending so much work to the GPU that it can't get a timestamp often enough, so it exhausts the 4-ish billion possible nonces (~4 GH), and starte repeating work).

Its crashing for me ever 2-4 minutes.  When I run the proxy what should i put in for prefex?

Windows 10 with a 390x

[arielbit]

application error, can't even open the miner

windows 7 64 bit here.

[adaseb]

Works GREAT!


Getting 500MH/s on R9 280X

[hankrules]

Works GREAT!


Getting 500MH/s on R9 280X

what c and i values are you using for that card?

[thedreamer]

Seems to work on single gpus. But crashes when starting 2nd instance of the miner for multiple gpus.

[arielbit]

Works GREAT!


Getting 500MH/s on R9 280X

what amd driver version you are using?

[lobstermd]

Works GREAT!


Getting 500MH/s on R9 280X

what amd driver version you are using?

That's what I'm wondering, I'm running the newest drivers and they seem to cause the program to crash. The benchmark runs for a few minutes and also crashes. Strange.

[Eyedol-X]

Working here on Win 7 X64 with a couple 390s -- one seems to be hashing faster than the other but that may just be luck.

Already found a block!

[szachta]

When pascal hit to the exchange?

[adaseb]

RADEON 7970 are MURDERING this coin at 800MH/S

[Aetsen]

I can get it to mine with 1 GPU, but the other 3 don't run. Trying to set up another user account now and syncing the wallet to test if it will work for targeting the 2nd GPU. Opening multiple miners with different device targets didn't work on an account together. The first card runs at 100%, but the others are at 0% doing nothing. Also noticed when I find a nonce it finds and submits the same nonce 6 or 7 times in a row.

[Eyedol-X]

RADEON 7970 are MURDERING this coin at 800MH/S

what intensity?