Bitcoin Forum
June 27, 2017, 04:13:04 PM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 [74] 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 ... 334 »
  Print  
Author Topic: [ANN] [PASC] PascalCoin, true deletable blockchain [WHITEPAPER V2]  (Read 466991 times)
jiggytom
Hero Member
*****
Offline Offline

Activity: 728


View Profile
October 22, 2016, 10:43:07 PM
 #1461

wonder what the miner "ocminer" plans to do with boat loads of coins he has mined

Sell @ $0.20 +/- IMHO.

Total, or per coin? lol

... PLAY SHARE EARN...
.LBRY...
                            ▄▄███▄▄
                        ▄▄█████▀█████▄▄
                    ▄▄█████▀▀     ▀▀█████▄▄
                ▄▄█████▀▀             ▀▀█████▄▄
            ▄▄█████▀▀                     ▀▀█████▄▄
        ▄▄█████▀▀                             ▀▀█████▄▄
    ▄▄█████▀▀                                     ▀▀███
▄▄█████▀▀                                         ▄▄███
███▀▀                                         ▄▄█████▀▀
███     █▄▄                               ▄▄█████▀▀
███     █████▄▄                       ▄▄█████▀▀  ▄▄▄▄▄▄▄▄
███       ▀▀█████▄▄               ▄▄█████▀▀       ██████
█████▄▄       ▀▀█████▄▄       ▄▄█████▀▀       ▄▄███████
  ▀▀█████▄▄       ▀▀█████▄▄▄█████▀▀       ▄▄█████▀▀ ██
      ▀▀█████▄▄       ▀▀█████▀▀       ▄▄█████▀▀
          ▀▀█████▄▄       ▀       ▄▄█████▀▀
              ▀▀█████▄▄       ▄▄█████▀▀
                  ▀▀█████▄▄▄█████▀▀
                      ▀▀█████▀▀
                          ▀
BTC: 174MGp3R5prNbuen31Kx5G5XuyuAXu9jye
LBC: bFrTLRcP9GSSHq2v5muLex4Sep4jphbNSU
1498579984
Hero Member
*
Offline Offline

Posts: 1498579984

View Profile Personal Message (Offline)

Ignore
1498579984
Reply with quote  #2

1498579984
Report to moderator
1498579984
Hero Member
*
Offline Offline

Posts: 1498579984

View Profile Personal Message (Offline)

Ignore
1498579984
Reply with quote  #2

1498579984
Report to moderator
1498579984
Hero Member
*
Offline Offline

Posts: 1498579984

View Profile Personal Message (Offline)

Ignore
1498579984
Reply with quote  #2

1498579984
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1498579984
Hero Member
*
Offline Offline

Posts: 1498579984

View Profile Personal Message (Offline)

Ignore
1498579984
Reply with quote  #2

1498579984
Report to moderator
Vorksholk
Legendary
*
Offline Offline

Activity: 1554



View Profile WWW
October 22, 2016, 10:43:47 PM
 #1462

Ahh. Gotcha. TY. Testing a multi gpu rig vs a single see how many blocks they solve.

I ran a two-gpu rig overnight and it got the exact same number of blocks as a single-GPU rig (all GPUs are the same), and I looked more into this, so I know for sure multi-GPU rigs for the moment are only effectively mining with the power of one GPU. I'm testing a fix right now.

Ahh. That explains it. Even though in the .jar proxy it shows as shares being submitted by individual / different GPU's.

Right--the problem stems from each GPU hashing the same data. Effectively two GPUs will hash slightly faster than one with the current system if they are slow enough that they don't complete a kernel run every second, because the timestamp will then be different at some points during both miners' running. However, GPUs fast enough to complete one or more kernel grinds a second will mostly duplicate each others' work, because the headerout file contains the miner name (like VorkGPUs01 or VorkGPUs00), so both GPUs are hashing the same 164 bytes of input data, adding their own 4-byte nonces which are deterministically produced (so two miners would produce the same nonce iteration, assuming the same kernel launch parameters (block and grid size, which are currently hard-coded into the binaries and set at what seemed to be the most efficient parameters on 9xx and 10xx cards during my testing), as well as the same 4-byte timestamp.

Still waiting to find a block with my new solution, but everything appears to be working correctly. Just a dumb oversight on my part, just waiting to get a block from both GPUs on the test system to make sure everything's kosher Smiley

Fold Proteins, earn cryptos! CureCoin.
https://bitcointalk.org/index.php?topic=603757.0
thedreamer
Hero Member
*****
Offline Offline

Activity: 868

Go Big or Go Home.....


View Profile
October 22, 2016, 10:45:49 PM
 #1463

Right--the problem stems from each GPU hashing the same data. Effectively two GPUs will hash slightly faster than one with the current system if they are slow enough that they don't complete a kernel run every second, because the timestamp will then be different at some points during both miners' running. However, GPUs fast enough to complete one or more kernel grinds a second will mostly duplicate each others' work, because the headerout file contains the miner name (like VorkGPUs01 or VorkGPUs00), so both GPUs are hashing the same 164 bytes of input data, adding their own 4-byte nonces which are deterministically produced (so two miners would produce the same nonce iteration, assuming the same kernel launch parameters (block and grid size, which are currently hard-coded into the binaries and set at what seemed to be the most efficient parameters on 9xx and 10xx cards during my testing), as well as the same 4-byte timestamp.

Still waiting to find a block with my new solution, but everything appears to be working correctly. Just a dumb oversight on my part, just waiting to get a block from both GPUs on the test system to make sure everything's kosher Smiley

Looks like you got a few blocks the past hour.

**Only send to this Wallet in BTC**
BTC Wallet : 1ANkrJri2sKVEyY7q4wjSPtWcrtMF3mqk7
Vorksholk
Legendary
*
Offline Offline

Activity: 1554



View Profile WWW
October 22, 2016, 10:48:34 PM
 #1464

Right--the problem stems from each GPU hashing the same data. Effectively two GPUs will hash slightly faster than one with the current system if they are slow enough that they don't complete a kernel run every second, because the timestamp will then be different at some points during both miners' running. However, GPUs fast enough to complete one or more kernel grinds a second will mostly duplicate each others' work, because the headerout file contains the miner name (like VorkGPUs01 or VorkGPUs00), so both GPUs are hashing the same 164 bytes of input data, adding their own 4-byte nonces which are deterministically produced (so two miners would produce the same nonce iteration, assuming the same kernel launch parameters (block and grid size, which are currently hard-coded into the binaries and set at what seemed to be the most efficient parameters on 9xx and 10xx cards during my testing), as well as the same 4-byte timestamp.

Still waiting to find a block with my new solution, but everything appears to be working correctly. Just a dumb oversight on my part, just waiting to get a block from both GPUs on the test system to make sure everything's kosher Smiley

Looks like you got a few blocks the past hour.

Yup, but I have multiple systems mining under the same name. My test rig got 1 block with GPU #1, and if I get 1 block with GPU #0 I can be pretty sure everything is perfect.

The update will require new CUDA mining binaries too, btw.

Fold Proteins, earn cryptos! CureCoin.
https://bitcointalk.org/index.php?topic=603757.0
Vorksholk
Legendary
*
Offline Offline

Activity: 1554



View Profile WWW
October 22, 2016, 10:57:14 PM
 #1465

Found a block on both miners and all of my debugging shows nothing but good results, so here's the proxy version 2 with cuda miners updated to support proxy v2:

https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.03/CUDA_Pascal_v1.03.zip

AMD miner coming in the next few hours.

Fold Proteins, earn cryptos! CureCoin.
https://bitcointalk.org/index.php?topic=603757.0
ICOcountdown.com
Sr. Member
****
Offline Offline

Activity: 462


View Profile WWW
October 22, 2016, 10:59:28 PM
 #1466

wonder what the miner "ocminer" plans to do with boat loads of coins he has mined

Sell @ $0.20 +/- IMHO.

Total, or per coin? lol

It isn't actually OCminer it is someone else using his name.

thedreamer
Hero Member
*****
Offline Offline

Activity: 868

Go Big or Go Home.....


View Profile
October 22, 2016, 11:13:54 PM
 #1467

Found a block on both miners and all of my debugging shows nothing but good results, so here's the proxy version 2 with cuda miners updated to support proxy v2:

https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.03/CUDA_Pascal_v1.03.zip

AMD miner coming in the next few hours.

How can you tell if GPU 0 or GPU 1 found a block?

And I can not wait for the AMD GPU miner.

**Only send to this Wallet in BTC**
BTC Wallet : 1ANkrJri2sKVEyY7q4wjSPtWcrtMF3mqk7
Vorksholk
Legendary
*
Offline Offline

Activity: 1554



View Profile WWW
October 22, 2016, 11:25:10 PM
 #1468

Found a block on both miners and all of my debugging shows nothing but good results, so here's the proxy version 2 with cuda miners updated to support proxy v2:

https://github.com/Vorksholk/PascalCoin-CUDA/releases/download/v1.03/CUDA_Pascal_v1.03.zip

AMD miner coming in the next few hours.

How can you tell if GPU 0 or GPU 1 found a block?

And I can not wait for the AMD GPU miner.

If you're using a name exclusively for a single rig, then you can just look at what the number is after the name. If you're mining with multiple pascal wallets on multiple machines all using the same miner name, then you need to pay attention to which nonce shows up in the any pascalcoin wallet when that block is announced in the logs, and see which of your machines with the gpu listed in the miner name (VorkGPUs00 for example is the name all of my GPUs I have at device #0 in my rigs are mining with, VorkGPUs01 is for all GPUs at device #1) mined that nonce by looking at the output in the proxy (or converting to hex and finding it in the miner output itself).

Fold Proteins, earn cryptos! CureCoin.
https://bitcointalk.org/index.php?topic=603757.0
thedreamer
Hero Member
*****
Offline Offline

Activity: 868

Go Big or Go Home.....


View Profile
October 22, 2016, 11:30:39 PM
 #1469

Ahh yeah. Forgot about the numerical convention after the 8=char walletname.

**Only send to this Wallet in BTC**
BTC Wallet : 1ANkrJri2sKVEyY7q4wjSPtWcrtMF3mqk7
kahir
Legendary
*
Offline Offline

Activity: 1050



View Profile
October 22, 2016, 11:43:59 PM
 #1470

next step for pascal is pool Cheesy
ICOcountdown.com
Sr. Member
****
Offline Offline

Activity: 462


View Profile WWW
October 23, 2016, 12:04:32 AM
 #1471

next step for pascal is pool Cheesy

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
Sr. Member
****
Offline Offline

Activity: 269



View Profile
October 23, 2016, 12:13:55 AM
 #1472

next step for pascal is pool Cheesy

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 ...  Grin

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.


PascalCoin is the first crypto currency without need of historical operations to control double spend and with ORDINAL account numbers. YES! LIKE A BANK!
proletariat
Legendary
*
Offline Offline

Activity: 994



View Profile
October 23, 2016, 12:15:36 AM
 #1473

next step for pascal is pool Cheesy

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 ...  Grin

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  Grin
Vorksholk
Legendary
*
Offline Offline

Activity: 1554



View Profile WWW
October 23, 2016, 02:24:31 AM
 #1474

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).

Fold Proteins, earn cryptos! CureCoin.
https://bitcointalk.org/index.php?topic=603757.0
PascalCoin
Sr. Member
****
Offline Offline

Activity: 269



View Profile
October 23, 2016, 02:45:27 AM
 #1475

OpenCL miner is here!

Aplause!

Very good job Vorksholk!

PascalCoin is the first crypto currency without need of historical operations to control double spend and with ORDINAL account numbers. YES! LIKE A BANK!
hankrules
Hero Member
*****
Offline Offline

Activity: 598


View Profile
October 23, 2016, 03:08:05 AM
 #1476

When does VorksholkCoin come out?
thedreamer
Hero Member
*****
Offline Offline

Activity: 868

Go Big or Go Home.....


View Profile
October 23, 2016, 03:31:39 AM
 #1477

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.

**Only send to this Wallet in BTC**
BTC Wallet : 1ANkrJri2sKVEyY7q4wjSPtWcrtMF3mqk7
lobstermd
Newbie
*
Offline Offline

Activity: 21


View Profile
October 23, 2016, 03:33:56 AM
 #1478

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
Legendary
*
Offline Offline

Activity: 1274


View Profile
October 23, 2016, 04:57:10 AM
 #1479

application error, can't even open the miner

windows 7 64 bit here.
adaseb
Legendary
*
Offline Offline

Activity: 1274



View Profile
October 23, 2016, 05:09:04 AM
 #1480

Works GREAT!


Getting 500MH/s on R9 280X

FORTUNEJACK.COM[
                             
WIN A SHARE OF 5BTC EVERY WEEK ON LEADERBOARD
FREE 1,000 mBTC daily for LuckyJack winners
[
           
]
Pages: « 1 ... 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 [74] 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 ... 334 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!