[PASC] PascalCoin: Induplicatable NFT

[Gema]

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/

[Marvell1]

suprnova down again jeez

[ocminer]

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] <TPCBank> Start restoring from disk operations (Max 4294967295) BlockCount: 69500 Orphan:
05-03-2017 09:17:12.801 TID:2391A700 [Error] <TFileStorage> 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] <TPCOperationsComp> Invalid new block 69534: Proof of work is higher than target
05-03-2017 09:17:12.801 TID:2391A700 [Error] <TPCOperationsComp> 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] <TPCOperationsComp> 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] <TNode> AddNewBlockChain Connection:00000000 NewBlock:Block:69555 Timestamp:1488705156 Reward:1000000 Fee:0 PoW:000000000000013F8DE83F48ED5F7B105AC70D75D4DB1344A84DA7287F9D1B46
2017-03-05 10:21:56.703 TID:7F942F493700 [Error] <TPCOperationsComp> Invalid new block 69555: Invalid Operations Hash 6726DB6BFCB0ADA8CB16FDE5ECA129E648DDB91FF62429D4ED84E7D926020BF9<>E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855
2017-03-05 10:21:56.704 TID:7F942F493700 [Debug] <TNode> 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] <TJSONRPCTcpIpClient> 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.

[PanneKopp]

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] <TPCBank> Start restoring from disk operations (Max 4294967295) BlockCount: 69500 Orphan:
05-03-2017 09:17:12.801 TID:2391A700 [Error] <TFileStorage> 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] <TPCOperationsComp> Invalid new block 69534: Proof of work is higher than target
05-03-2017 09:17:12.801 TID:2391A700 [Error] <TPCOperationsComp> 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] <TPCOperationsComp> 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] <TNode> AddNewBlockChain Connection:00000000 NewBlock:Block:69555 Timestamp:1488705156 Reward:1000000 Fee:0 PoW:000000000000013F8DE83F48ED5F7B105AC70D75D4DB1344A84DA7287F9D1B46
2017-03-05 10:21:56.703 TID:7F942F493700 [Error] <TPCOperationsComp> Invalid new block 69555: Invalid Operations Hash 6726DB6BFCB0ADA8CB16FDE5ECA129E648DDB91FF62429D4ED84E7D926020BF9<>E3B0C44298FC1C149AFBF4C8996FB92427AE41E4649B934CA495991B7852B855
2017-03-05 10:21:56.704 TID:7F942F493700 [Debug] <TNode> 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] <TJSONRPCTcpIpClient> 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

[DynamicPimp]

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

[escapefrom3dom]

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

u can only guess about short terms price changes but the coin may rise during long period (1-2 years).

[PascalCoin]

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

[nightraven]

What is this nonsense about time???

I get this kind of messages all the time:

7-3-17 00:50:30 Internal message: Detected a different time in an other node... check that your PC time and timezone is correct or you will be Blacklisted! Your time: 00:50:30 - 104.172.24.79:51486 time: 22:50:13 Difference: -7217 seconds. (If this message appears on each connection, then you have a bad configured time, if not, do nothing)

My computer isn't out of sync. It runs on central european time as it should. That is UTC + 1 hour.

[escapefrom3dom]

New PascalCoin Build 1.5.3

thanks.

way to go.

[PascalCoin]

How much does an address cost ?

Will i receive a public number and a private key ?

And how can i be sure my private key has not been copied by the former owner ?

something technical here i dont understand


thank you

A Pascal account (address on other altcoins) is generated by the miner. If you don't mine, then you need to obtain an account from other channels (somebody gives one to you for free... or buying)

To obtain an account, you must publish your PUBLIC key (not that your private key is only for you) and the other wallet must do a "change owner" operation, setting your public key to an account.
After this, you will be the new owner of this account, and only you will have the private key.

[jmknapp80]

Hi poolmn. Any update on the pool status? Hopefully you're making some progress 

We've disabled the pool currently as we see problems with the wallet hogging memory, cpu and also orphan blocks as well as work restarts. We'll investigate and eventually re-enable

[apolousm]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

[forzendiablo]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

You need to catch a single block to get account. Pools have account and get money there that they re-send to others.

[redmonski]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

They send me 1 account for every 25 PASC I mined with them.

[apolousm]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

You need to catch a single block to get account. Pools have account and get money there that they re-send to others.

Thanks for your response bro, but I think didn't make myself clear enought. If you mine at Nanopool you have to wait until reaching 4000 points of rating (rating???) to get an account. I got mine as soon as I reached the required rating, but I did not get any other account when I reached 8000. Right now my rating is 18470 points, and If i'm right I should have 4 accounts at this moment (I have four times the required rating) so, my question: what do the pools do with all the accounts generated from our work? do we receive any money for the sold accounts? does Nanopool sell the mined accounts? If I receive an account, will I receive another one?

[apolousm]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

They send me 1 account for every 25 PASC I mined with them.

Do you change your public key everytime you get a new account?

[redmonski]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

They send me 1 account for every 25 PASC I mined with them.

Do you change your public key everytime you get a new account?

No need to change public key. The pool uses your public key to send you the account.

Are you concerned of the security of the account? Once the account has been transferred to you, the sender can no longer control the account.

[apolousm]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

They send me 1 account for every 25 PASC I mined with them.

Do you change your public key everytime you get a new account?

No need to change public key. The pool uses your public key to send you the account.

Are you concerned of the security of the account? Once the account has been transferred to you, the sender can no longer control the account.

No, I just want to know why if I have mined more than 50 pascals on Nanopool I have just received one account.

[redmonski]

There's one thing I don't understand. Pools are distributing accounts, but how many pascals do I have to mine to get an account? (let say Nanopool for instance), and, after I get one account will I receive more for the mining process?

Thanks a lot

They send me 1 account for every 25 PASC I mined with them.

Do you change your public key everytime you get a new account?

No need to change public key. The pool uses your public key to send you the account.

Are you concerned of the security of the account? Once the account has been transferred to you, the sender can no longer control the account.

No, I just want to know why if I have mined more than 50 pascals on Nanopool I have just received one account.

You should open a support ticket with nano.

[nightraven]

I get banned for wrong time when I compile and run PascalCoin. No problems when I run the precompiled version downloaded from Sourceforge.

I think ther is a bug in UTime.pas. There is a function:

Function DateTime2UnivDateTime(d:TDateTime):TDateTime;
{$IFDEF FPC}
begin
  Result := UniversalTimeToLocal(d);
//  Result := LocalTimeToUniversal(d);
end;
{$ELSE}
var

The name says it should return Universal time from local time, but it calls a Lazarus/Fpc function that converts universal time to local time. It seems wrong.
The call that is commented out seems to be the right one. But it looks like somebody perhaps has made a quick fix.

There is also another function:

Function UnivDateTime2LocalDateTime(d:TDateTime):TDateTime;
{$IFDEF FPC}
begin
//  Result := UniversalTimeToLocal(d);
  Result := LocalTimeToUniversal(d);
end;
{$ELSE}

It should return local time from universal time but calls a system function that does the opposite

I compile with Lazarus 1.6.4 and Fpc 3.0.2. My computers OS is Linux Mint ver. 18.1

Cheers