[PASC] PascalCoin: Induplicatable NFT

[e-coinomist]

What's special with Pascal coin? Just added to poloniex, got huge volume and moon!?

This is just how it goes usually. In a way that's our own fault we could have a more ballanced altoin tradesites landscape out there, like fifty-fifty between Bittrex and Poloniex.
Would I buy in now?

PascalCoin started mining on 2016-08-11
...

Specifications:
...
- Hashing method is double Sha256
...

This ^^^ would mean giving a try to redeploy these old ASIC USB-Sticks again? Would love to see some numbers on exspectable revenue. It's still cold outside and the dissolved heat would not be wasted inside my home.

[barrysty1e]

in an attempt to work out how the cpu/gpu mining of pascalcoin works, i had a quick read of 'https://github.com/PascalCoin/PascalCoin/blob/master/HOWTO_DEVELOP_GPU_MINER_FOR_PASCALCOIN.txt' (which is pretty straightforward and easy to understand). i then captured some of the traffic between daemon and miner/proxy:

Code:

{
    "method": "miner-notify",
    "params": [{
        "block": 57100,
        "version": 1,
        "part1": "0CDF0000CA0220000644BA0E9C20DC3C81383A0CD17365C25CCC7C38B03E58D04FFBE50B2575FEFE2000FC861CD3E29EA6AB27DA0B4C1962B495E5F2BBB848792EC30953427085FD27DA40420F000000000001000100F5229830",
        "payload_start": "62617A7374796C65",
        "part3": "BAEFA4E7DAA3D43CE283FB77369A260EA736898E2206C1EF043627E308178142E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",
        "target": 815276789,
        "target_pow": "000000000000B3EE850000000000000000000000000000000000000000000000",
        "timestamp": 1485547008
    }],
    "id": null
}

however, the doc states that '"part3" : equal to part1', but as above this is not the case?

[daboehla]

in an attempt to work out how the cpu/gpu mining of pascalcoin works, i had a quick read of 'https://github.com/PascalCoin/PascalCoin/blob/master/HOWTO_DEVELOP_GPU_MINER_FOR_PASCALCOIN.txt' (which is pretty straightforward and easy to understand). i then captured some of the traffic between daemon and miner/proxy:

Code:

{
    "method": "miner-notify",
    "params": [{
        "block": 57100,
        "version": 1,
        "part1": "0CDF0000CA0220000644BA0E9C20DC3C81383A0CD17365C25CCC7C38B03E58D04FFBE50B2575FEFE2000FC861CD3E29EA6AB27DA0B4C1962B495E5F2BBB848792EC30953427085FD27DA40420F000000000001000100F5229830",
        "payload_start": "62617A7374796C65",
        "part3": "BAEFA4E7DAA3D43CE283FB77369A260EA736898E2206C1EF043627E308178142E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",
        "target": 815276789,
        "target_pow": "000000000000B3EE850000000000000000000000000000000000000000000000",
        "timestamp": 1485547008
    }],
    "id": null
}

however, the doc states that '"part3" : equal to part1', but as above this is not the case?

You have to do the same as with part1.
So it means for part3:
This is a Hexa string, you must convert it to RAW and store to a buffer called "buffer_part3"

[roy2266]

No block in 48 hours with 3 Khash!

[gegstore]

to mine 1 block with 1000 mh, how mani days???

[Vorksholk]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

[barrysty1e]

in an attempt to work out how the cpu/gpu mining of pascalcoin works, i had a quick read of 'https://github.com/PascalCoin/PascalCoin/blob/master/HOWTO_DEVELOP_GPU_MINER_FOR_PASCALCOIN.txt' (which is pretty straightforward and easy to understand). i then captured some of the traffic between daemon and miner/proxy:

Code:

{
    "method": "miner-notify",
    "params": [{
        "block": 57100,
        "version": 1,
        "part1": "0CDF0000CA0220000644BA0E9C20DC3C81383A0CD17365C25CCC7C38B03E58D04FFBE50B2575FEFE2000FC861CD3E29EA6AB27DA0B4C1962B495E5F2BBB848792EC30953427085FD27DA40420F000000000001000100F5229830",
        "payload_start": "62617A7374796C65",
        "part3": "BAEFA4E7DAA3D43CE283FB77369A260EA736898E2206C1EF043627E308178142E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",
        "target": 815276789,
        "target_pow": "000000000000B3EE850000000000000000000000000000000000000000000000",
        "timestamp": 1485547008
    }],
    "id": null
}

however, the doc states that '"part3" : equal to part1', but as above this is not the case?

You have to do the same as with part1.
So it means for part3:
This is a Hexa string, you must convert it to RAW and store to a buffer called "buffer_part3"

ah; this needs to be reworded:
'part3: perform the same steps with this hash, as per part1.'

[MinermanNC]

i am getting node status:alone in the world

I am on one of my rigs... Its keeps blacklisting my IP when it reaches 4 days old (alone in the world  ).... I have tried everything, still no luck with that rig. On another rig,,,, same W7, it runs fine and am mining with 2 x 7970's

Both rigs go out with the same public IP ??

yes

Obviously you confuse the network.  It's a safety measure.

-  Use only one wallet.  Point all your miners to it.  It works from other subnets too.

-  Forward tcp/4004 in your router, and let the packets arrive to the wallet.  I have 3 servers and 96 clients connected, and never had any such problem.  The traffic is low, no problem like bitcoin with big traffic.

Hey thanks for that insight. Right now I have a wallet on each separate rig (well 2 rigs for testing) I will try what you suggest.  

[ioglnx]

I just mined 2 Blocks with KlausT Miner yesterday and today one.

[Amph]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

you say that this error is not really an error, but just how it work, but why you are saying that "no promise that the new miner can actually mine blocks"? if it work it should eventually find one

[Vorksholk]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

you say that this error is not really an error, but just how it work, but why you are saying that "no promise that the new miner can actually mine blocks"? if it work it should eventually find one

I'm saying that the error isn't necessarily an indicator of any problem (in fact, it's 100% expected), but that doesn't mean something else couldn't be wrong with the miner.

[Amph]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

you say that this error is not really an error, but just how it work, but why you are saying that "no promise that the new miner can actually mine blocks"? if it work it should eventually find one

I'm saying that the error isn't necessarily an indicator of any problem (in fact, it's 100% expected), but that doesn't mean something else couldn't be wrong with the miner.

mmh ok...btw can you fix the multiple instance thing with the nvidia miner, amd can run all the gpu with one instances but nvidia still not...

[Vorksholk]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

you say that this error is not really an error, but just how it work, but why you are saying that "no promise that the new miner can actually mine blocks"? if it work it should eventually find one

I'm saying that the error isn't necessarily an indicator of any problem (in fact, it's 100% expected), but that doesn't mean something else couldn't be wrong with the miner.

mmh ok...btw can you fix the multiple instance thing with the nvidia miner, amd can run all the gpu with one instances but nvidia still not...

Unfortunately I'm way too busy with other projects at the moment Multiple instances really aren't that much of a pain though.

[D8V1D]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

You make a miner but say "No promise that the new miner can actually mine blocks".

WTF is this, how do you not know, if the miner that you made actually works?

[smaxz]

27/01/2017 19:02:48.943 TID:00000D28 [Error] <TPCOperationsComp> Invalid new block 57080: block (57080) is not new position (57081)
27/01/2017 19:02:53.394 TID:00000D28 [Info] <GetNewBlockChainFromClient> My blockchain is ok! Need to download new blocks starting at 57081

27/01/2017 19:28:35.209 TID:00000A98 [Error] <TPCOperationsComp> Invalid new block 57086: Error executing operation 1/1: Invalid n_operation 585 (expected 586)
27/01/2017 19:28:39.029 TID:00000A98 [Info] <GetNewBlockChainFromClient> My blockchain is ok! Need to download new blocks starting at 57087

Should i care about this message in the log?

Thanks for your Help

up

this looks like buggy wallet code or temporary disconnect from peers.

[reb0rn21]

@Vorksholk
there is now new json error:
<TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Invalid Operations Hash CEA1F197170160FAB4AF984F4DC6D5DEA7FF1F04B926F85B253C19B7FAF63F10<>E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 payload:reb0rn0101 timestamp:1485548997 nonce:3525306155

[BTCdoaA]

What's special with Pascal coin? Just added to poloniex, got huge volume and moon!?

This alone is very special for me and other traders\miners who like to trade@mine .....

[escapefrom3dom]

hi, i'm mining with 480 and PascalCoin_OpenCL_ProxyMiner_v1

is that ok i'm getting 2 windows and in miner window i see just (look at picture)
Real: 4LKHJSFLFGKBSLDKG0988........
Real: SVDFGVNFDSGBNFD58944........

without any hashrate, which is 630 MH/sec in PascalCoinMiner_0.2?

[Vorksholk]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

You make a miner but say "No promise that the new miner can actually mine blocks".

WTF is this, how do you not know, if the miner that you made actually works?

It's possible that one of the optimizations (namely the funnelshift, can't imagine an unroll causing a problem) could introduce a bug by not behaving the way I expect. The way to truly know a miner works is to mine a block with it (although you can be pretty certain that it works by manually checking hashes).

[D8V1D]

Hey everyone, updated the CUDA GPU miner with some of KlausT's improvements: https://github.com/Vorksholk/PascalCoin-CUDA/releases/tag/v1.04

No promise that the new miner can actually mine blocks, but if anyone gets a block with this, please let the rest of us know. About 360% performance improvements, I'm getting around 900 MH/s on an overclocked 1080.

I've also seen some people worried about the PascalCoin wallet saying "Error: Proof of work is higher than target payload." This isn't a problem--the way my miner works (and presumably some others that are floating around now, although I haven't looked at the code for them) is by submitting shares that meet a target of 24000000. Note that we are currently on track for a target of 31000000 soon, which is 8192 times higher, so you should expect to see, on average, 8192 of those errors per actual block mined. The miner is submitting shares to the wallet, effectively. These shares don't count for anything unless they meet the target.

You make a miner but say "No promise that the new miner can actually mine blocks".

WTF is this, how do you not know, if the miner that you made actually works?

It's possible that one of the optimizations (namely the funnelshift, can't imagine an unroll causing a problem) could introduce a bug by not behaving the way I expect. The way to truly know a miner works is to mine a block with it (although you can be pretty certain that it works by manually checking hashes).

So If it doesn't mine a block, we'll never know if it actually working.

People will be mining for days, saying they can't find a block, not knowing if the miner actually works.

What a waste of time and electricity.