Topic: [ANN] [PASC] PascalCoin, true deletable blockchain - V3 Hardfork on block 210000 - page 90. (Read 990744 times)

I have a transation of 1 pascal since 2 days ago with 0 of 8 confirmations. Can someone help?

I downloaded ubuntu wallet and the new blockchainstream but my wallet says v 2.1.0 am I good or where is 2.1.1 ubuntu binaries

I downloaded ubuntu wallet and the new blockchainstream but my wallet says v 2.1.0 am I good or where is 2.1.1 ubuntu binaries

Slack is like a chat room with different channels based on topic. The devs, mainly Herman are there often. If you want pasc news firsthand, join here:

http://www.pascalcoin.org/slack-self-invite

Hello, I do not understand the operating principle of Slack, I have never used it before, could someone explain how to access the PascalCoin slack? Thank you

2.1.1 works fine after a clean install (i.e. uninstall old wallet and delete data folder in C:\Users\UserName\AppData\Roaming\PascalCoin\Data).

but don't delete WalletKeys.dat!

no, in an above post theres a bug on 2.1.1.0, so i was going to wait untill thats fixed, i really dont need to make this more complicated or time consuming, i have a very young O.D.D. child to constantly attend from dawn till midnight. and can only grab a few mins here or there before i have to run back to my dutys.

Have you installed the latest version 2.1.1

HARD FORK INFORMATION

Hard-fork was successful and went smoothly for critical users such as miners and exchanges. There were no bugs or crashes, however, many nodes experienced an issue described below. For those affected nodes, the solution is very simple:

1. Download latest build 2.1.1 and re-install

OR if you do not care about historical operations, you can just

2. Delete your /Data sub-dir and restart wallet, you will be synced in few minutes due to new checkpointing functionality. Make sure you do not delete WalletKeys.dat files.


HOW ISSUE OCCURED

1. PascalCoin 2.0.0 and 2.1.0 were shipped with a pre-packaged SafeBox to improve sync performance. This pre-packaged SafeBox included block 107187a

Moments after the package was created, Murphy's Law strikes as follows:

2. Nanopool orphans it’s 107187a with an operationally identical block 107187b except with a different Payload (they do this occasionally since Nanopool appears to be 3 independent pools operating under one umbrella).

3. Since the operations between 107187a and 107187b are the same they affected the account balances and keys exactly the same way. As a result, the V1 SafeBox hash was identical for both 107187a and 107187b.

4. When block 115001 reached, the V2 hashing algorithm activated and detected the difference between 107187a and 107187b. This occurs because V2 now includes the block header in the account segment sub-structures of the SafeBox, which affects the SafeBox hash. Since the Payloads were different, the nodes that contained 107187a hashed the SafeBox differently than those who had 107187b.

5. Only nodes that installed using the pre-packaged installer were affected. All other nodes that synchronised from block 0, or who rebuilt their own SafeBox were unaffected.


CONCLUSION

A - Completely harmless. No funds were lost, stolen or changed whatsoever. We know this for a fact because if there was a difference in account balance or key ownership, step (3) would have detected this difference early on as the V1 SafeBox hash would have been different.

B - Poloniex and other miners were not affected at all and are sending/receiving funds normally.

C - Thanks to V2 Checkpointing, we will no longer ship SafeBox’s inside the installer. This issue will never happen again.


Apologies for inconvenience, but this issue was harmless and we consider the V2 Hard-Fork a success nonetheless.

Regards,
Herman, PascalCoin Development Team

Which version of wallet is this? Do you have a link to download?