[PASC] PascalCoin: Induplicatable NFT

[escapefrom3dom]

For those with sync issue, it's easy fix. Delete data folder, appparams, and blocks.log. Restart pc maybe, but then run wallet. Syncs no problem. I originally had the sync problem and then performed these steps. It works.

Thanks your inf0, I try this and my wallet is ok! But can i sent my coin to exchange at the moment?

just try with 1 pasc and u'll see.

nano withdrawals work fine.

[jmknapp80]

from Albert:

pascalcoin [9:36 PM]
The bad news is that I made a mistake and the safebox file I provided with the installer is malformed.
You have 2 solutions:

1 - Delete ALL your *.safebox files  (WARNING: Only the .safebox files!)
  Linux: $HOME/PascalCoin/Data
  Windows: C:\Users\xxx\AppData\Roaming\PascalCoin\Data
Restart the app.
This will "regenerate" the safebox reading all the blockchain... aprox 2 hours


2 - Wait for a new installer with this issue solved

[rooster2000bka]

Everyone can share me a acc for PASC coin, I only member of this coin, not a exchange or miner
thanks
My key: 3GhhbokJZXG3XxpLANiQAu69JEiRs1wcC1hsqu9c8fuJBeN4MbzYxbaDBBdpEwckrkqkobzZuYVqido iND9KL2KU2tzQkZuKFXwCt8

[turn over]

Looks like the hard fork failed 

Why should hard fork , who can explain it

[cryptotrader111]

Looks like the hard fork failed  

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

[MisterMerci]

Looks like the hard fork failed  

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

2. Turn off wallet, delete the *.safebox files from data directory and restart. Wait 2 hours whilst SafeBox is reconstructed by your wallet.

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

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

Indeed, all this went without any problem, it is rare in the cryptos world. Pascalcoin is very well coded and everything works correctly it is time to buy in large quantity now 

[BrunoS]

############## Buying / selling Pascal accounts works perfectly! ##############

[MisterMerci]

############## Buying / selling Pascal accounts works perfectly! ##############

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

[BrunoS]

############## Buying / selling Pascal accounts works perfectly! ##############

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

https://sourceforge.net/projects/pascalcoin/files/latest/download?utm_campaign=updater&utm_medium=email&utm_source=subscribers

[MisterMerci]

############## Buying / selling Pascal accounts works perfectly! ##############

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

https://sourceforge.net/projects/pascalcoin/files/latest/download?utm_campaign=updater&utm_medium=email&utm_source=subscribers

Thank you very much 

[MisterMerci]

I think it might be interesting to create a faucet for Pascalcoin  People would be interested in it even more. If I had the technical knowledge to take care of it I will do it but I do not know how to do, does anyone think it can take care of it?

[Nooby-miner]

Looks like the hard fork failed  

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

I deleted all the safebox files. The miner caught up to current date, but is showing "current block age 12 Hours" and deposit to my account i made this morning has not been added although the transaction is showing as confirmed. All in all i havent got a clue whats happening or what to do.

[BrunoS]

Have you installed the latest version 2.1.1

[Nooby-miner]

Have you installed the latest version 2.1.1

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.

[escapefrom3dom]

Have you installed the latest version 2.1.1

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.

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!

[BrunoS]

Have you installed the latest version 2.1.1

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.

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!

If you install version 2.1.1, you do not need to delete anything.
Here last version 2.1.1:
https://sourceforge.net/projects/pascalcoin/

[Nooby-miner]

Thanks You guys! Ive done this now, and all is working 100%

[MisterMerci]

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

[BrunoS]

I think the option:
"List account for private sale" does not work.
The account is not displayed in the wallet of the buyer.
I have tested on 2 different pc with 2 different wallets. Or I do not understand something. 

[jmknapp80]

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

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