New PascalCoin Build 1.5.3
SOURCE CODE at GitHub:
https://github.com/PascalCoin/PascalCoin/releases/tag/1.5.3
COMPILED BINARIES at SourceForge:
https://sourceforge.net/projects/pascalcoin/files/
### Build 1.5.3.0 - 2017-03-06
- Fixed issue #23: RPC findoperation fails to find operation by opHash
- Miners best practices: Sending new job with new timestamp every 30 seconds
- Buffering last 10 sent jobs to miners
- Small delay prior to destroy a connection to prevent exception handling
- Minor logs changes
Topic: [ANN] [PASC] PascalCoin, true deletable blockchain - V3 Hardfork on block 210000 - page 153. (Read 990783 times)
March 06, 2017, 05:45:55 PM
March 06, 2017, 05:26:00 AM
Were do you guys think the bottom is for the price? I have a few BTC I was going to throw at this project just wondering if I should wait or strike now...
Any input that's at least half intelligent is appreciated
-DynamicPimp
Any input that's at least half intelligent is appreciated
-DynamicPimp
u can only guess about short terms price changes but the coin may rise during long period (1-2 years).
March 05, 2017, 09:57:37 PM
Were do you guys think the bottom is for the price? I have a few BTC I was going to throw at this project just wondering if I should wait or strike now...
Any input that's at least half intelligent is appreciated
-DynamicPimp
Any input that's at least half intelligent is appreciated
-DynamicPimp
March 05, 2017, 02:32:56 PM
Dear @ocminer
It's down for the first time
The wallet crashed after using up all of the 64GB ram on linux - i'm restarting it in a few moments.
However, I'd like to takes this opportunity and take down the pool as well, so I'll post a notice that it'll close in a few days after it's back up again.
Please move over to Coinotron or Nanopool
thx !
EDIT:
Ah looks like there's another bug
05-03-2017 09:17:11.134 TID:2391A700 [Info] Start restoring from disk operations (Max 4294967295) BlockCount: 69500 Orphan:
05-03-2017 09:17:12.801 TID:2391A700 [Error] Invalid stream size. Block 69534 need to be at relative 3072088 after 113831006 = 116903094 BlockSize:443 (Size 116903094)
05-03-2017 09:17:12.801 TID:2391A700 [Error] Invalid new block 69534: Proof of work is higher than target
05-03-2017 09:17:12.801 TID:2391A700 [Error] Error restoring block: 69534 Errors: Proof of work is higher than target
I'll try with a fresh version of the wallet
EDIT2:
And the trouble keeps going on.. something is up again:
05-03-2017 09:27:14.220 TID:4C66D700 [Error] Invalid new block 69547: Error executing operation 1/13: Invalid n_operation 163563 (expected 163576)
EDIT3:
And we still have the invalid op hash error when the chain is flooded with tx'es:
2017-03-05 10:21:56.703 TID:7F942F493700 [Debug] AddNewBlockChain Connection:00000000 NewBlock:Block:69555 Timestamp:1488705156 Reward:1000000 Fee:0 PoW:000000000000013F8DE83F48ED5F7B105AC70D75D4DB1344A84DA7287F9D1B46
2017-03-05 10:21:56.703 TID:7F942F493700 [Error] Invalid new block 69555: Invalid Operations Hash 6726DB6BFCB0ADA8CB16FDE5ECA129E648DDB91FF62429D4ED84E7D926020BF9<>E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855
2017-03-05 10:21:56.704 TID:7F942F493700 [Debug] Finalizing AddNewBlockChain Connection:00000000 NewBlock:Block:69555 Timestamp:1488705156 Reward:1000000 Fee:0 PoW:000000000000013F8DE83F48ED5F7B105AC70D75D4DB1344A84DA7287F9D1B46
2017-03-05 10:21:56.704 TID:7F942F493700 [Error] Sending Error JSON RPC id () : Error: Invalid Operations Hash 6726DB6BFCB0ADA8CB16FDE5ECA129E648DDB91FF62429D4ED84E7D926020BF9<>E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 payload:SUPRNOVAROXXXXXXXXXXXXKUEM4d2f0000 timestamp:1488705156 nonce:775248896
According to my logs 6726DB6BFCB0ADA8CB16FDE5ECA129E648DDB91FF62429D4ED84E7D926020BF9 was the ophash before one tx and E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 was the one after.. So the block should still be valid, just with less TX'es included in the block.
THX 4 the information.
Not correct.
Any timestamp is accepted.
This coins are exploited heavily already and big stakes are already in hands which are just waiting to dump.
The coin is not mature in its current state for any use, it's a pure speculators (and fpga miners) coin with custom pools and hacked / modded nodes / wallets
THX 4 the honest and remarkable words.
At least, my solo-miner in v1.5.2 seems 2 be working on the right block now.
My guess is, 2 better watch it from the side-line, when supernova really closes pool (not 2 feed the cheaters).
PanneKopp
It's down for the first time
The wallet crashed after using up all of the 64GB ram on linux - i'm restarting it in a few moments.
However, I'd like to takes this opportunity and take down the pool as well, so I'll post a notice that it'll close in a few days after it's back up again.
Please move over to Coinotron or Nanopool
thx !
EDIT:
Ah looks like there's another bug
05-03-2017 09:17:11.134 TID:2391A700 [Info]
05-03-2017 09:17:12.801 TID:2391A700 [Error]
05-03-2017 09:17:12.801 TID:2391A700 [Error]
05-03-2017 09:17:12.801 TID:2391A700 [Error]
I'll try with a fresh version of the wallet
EDIT2:
And the trouble keeps going on.. something is up again:
05-03-2017 09:27:14.220 TID:4C66D700 [Error]
EDIT3:
And we still have the invalid op hash error when the chain is flooded with tx'es:
2017-03-05 10:21:56.703 TID:7F942F493700 [Debug]
2017-03-05 10:21:56.703 TID:7F942F493700 [Error]
2017-03-05 10:21:56.704 TID:7F942F493700 [Debug]
2017-03-05 10:21:56.704 TID:7F942F493700 [Error]
According to my logs 6726DB6BFCB0ADA8CB16FDE5ECA129E648DDB91FF62429D4ED84E7D926020BF9 was the ophash before one tx and E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 was the one after.. So the block should still be valid, just with less TX'es included in the block.
THX 4 the information.
Not correct.
Any timestamp is accepted.
This coins are exploited heavily already and big stakes are already in hands which are just waiting to dump.
The coin is not mature in its current state for any use, it's a pure speculators (and fpga miners) coin with custom pools and hacked / modded nodes / wallets
THX 4 the honest and remarkable words.
At least, my solo-miner in v1.5.2 seems 2 be working on the right block now.
My guess is, 2 better watch it from the side-line, when supernova really closes pool (not 2 feed the cheaters).
PanneKopp 
March 05, 2017, 03:14:49 AM
suprnova down again jeez
again ?
It's down for the first time
The wallet crashed after using up all of the 64GB ram on linux - i'm restarting it in a few moments.
However, I'd like to takes this opportunity and take down the pool as well, so I'll post a notice that it'll close in a few days after it's back up again.
Please move over to Coinotron or Nanopool
thx !
EDIT:
Ah looks like there's another bug
05-03-2017 09:17:11.134 TID:2391A700 [Info]
05-03-2017 09:17:12.801 TID:2391A700 [Error]
05-03-2017 09:17:12.801 TID:2391A700 [Error]
05-03-2017 09:17:12.801 TID:2391A700 [Error]
I'll try with a fresh version of the wallet
EDIT2:
And the trouble keeps going on.. something is up again:
05-03-2017 09:27:14.220 TID:4C66D700 [Error]
EDIT3:
And we still have the invalid op hash error when the chain is flooded with tx'es:
2017-03-05 10:21:56.703 TID:7F942F493700 [Debug]
2017-03-05 10:21:56.703 TID:7F942F493700 [Error]
2017-03-05 10:21:56.704 TID:7F942F493700 [Debug]
2017-03-05 10:21:56.704 TID:7F942F493700 [Error]
According to my logs 6726DB6BFCB0ADA8CB16FDE5ECA129E648DDB91FF62429D4ED84E7D926020BF9 was the ophash before one tx and E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855 was the one after.. So the block should still be valid, just with less TX'es included in the block.
March 05, 2017, 12:50:57 AM
suprnova down again jeez
March 04, 2017, 12:05:29 PM
Added a jobs buffer for miners. This will allow to submit old job solutions (limited buffer). (Fix the “tx” issue)
Miner jobs will not be sent every time a transaction is received, thet will be buffered and sent every few seconds (Fix the “tx” issue)
Better network performance, allowing more operations and nodes thanks to buffering before relaying
Daemon: Allow select on ini file how many connections can handle
Fixed a locking when deleting connections##Downloads
https://cryptowallets.io/2017/03/03/pascalcoin-pascalcoin-build-1-5-2/
Miner jobs will not be sent every time a transaction is received, thet will be buffered and sent every few seconds (Fix the “tx” issue)
Better network performance, allowing more operations and nodes thanks to buffering before relaying
Daemon: Allow select on ini file how many connections can handle
Fixed a locking when deleting connections##Downloads
https://cryptowallets.io/2017/03/03/pascalcoin-pascalcoin-build-1-5-2/
March 03, 2017, 11:36:56 PM
The price has a little pump again, which makes me happy. I thought the price would go lower than 10k, but now it is pumping again. Congratulations for holders.
March 03, 2017, 11:25:23 PM
Anyone seeing high rejects on suprnova pool? average reject rate on my three rigs is 7% some as high as 20% when i first start them up
my efficiency is only 87% , these same rigs min DCR, and eth, ZEC with rejects in the low percentage points
my efficiency is only 87% , these same rigs min DCR, and eth, ZEC with rejects in the low percentage points
Are you dual mining with Claymore?
one of the rigs is dual mining, the other two are mining pascal alone 280x rigs
March 03, 2017, 10:57:17 PM
Anyone seeing high rejects on suprnova pool? average reject rate on my three rigs is 7% some as high as 20% when i first start them up
my efficiency is only 87% , these same rigs min DCR, and eth, ZEC with rejects in the low percentage points
my efficiency is only 87% , these same rigs min DCR, and eth, ZEC with rejects in the low percentage points
Are you dual mining with Claymore?
March 03, 2017, 10:40:22 PM
Anyone seeing high rejects on suprnova pool? average reject rate on my three rigs is 7% some as high as 20% when i first start them up
my efficiency is only 87% , these same rigs min DCR, and eth, ZEC with rejects in the low percentage points
my efficiency is only 87% , these same rigs min DCR, and eth, ZEC with rejects in the low percentage points
March 03, 2017, 08:53:07 PM
accounts for sale select and pm me your offer
Do you sell bct account id? March 03, 2017, 08:51:33 PM
What initial price of pascal during first launch?
March 03, 2017, 08:42:39 PM
HEAVY Pump is coming in Polo.. 
March 03, 2017, 08:24:20 PM
yess thats great , I hope soon go to moon again 150K or more
March 03, 2017, 05:47:07 PM
@PanneKopp thanks!
March 03, 2017, 04:59:17 PM
@gaba did you get an account already ?
Unfortunately nothing, not a single one. Happy news is that I yesterday presented Pascal to the group of crypto enthusiasts. Who knows maybe they are buying today
I strongly encourage all who believe in this project, it would be nice to donate. Do not be afraid. Developer needs your support.
Hi @gaba,
291329-38 should be on the way 2 you.
March 03, 2017, 03:19:56 PM
try with --gpu-platform 0.
March 03, 2017, 03:05:56 PM
!!!!!!!!!!!!!!!!!!!!!HHEEEEEEEELP!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Exception at 000000010004492C: EAccessViolation:
Access violation
Error pls help 6x MSI RX 480 GAMING X 4G!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Exception at 000000010004492C: EAccessViolation:
Access violation
Error pls help 6x MSI RX 480 GAMING X 4G!!!
i had this error on my 6x rx 470 rig. I used -p 1 instead of -p 0 and voila. Hope it helps !
It detects the number of platforms.Quote
D:\blockchain\pascal\miner>PascalCoinMiner.exe -p 1 -d 0 -n GPU -s
Invalid Platform 1. Valid values: 0..0
Exception at 000000010004492C: EAccessViolation:
Access violation.
Invalid Platform 1. Valid values: 0..0
Exception at 000000010004492C: EAccessViolation:
Access violation.
Thanks
March 03, 2017, 01:47:35 PM
Looks like PASC hit a bottom at poloniex at 0.00012 and is only going up from here. Thoughts?
If DASH and ETH weren't attracting all the volume right now, I'd have thought a massive pump could be possible. As it is, it's a bit dodgy.
Jump to: