[ANN] BitShares PTS Mandatory Upgrade & Snapshot Announcement

[pc]

This was an urgently needed fix for the transaction malleability bug.

[testz]

Version 2.0.1 has been published - please upgrade ASAP.

Can you post some release notes/changes in https://github.com/PTS-DPOS/PTS/releases/tag/v2.0.1

[pc]

Version 2.0.1 has been published - please upgrade ASAP.

[cube]

The signed message command gave me assert exception. The import wallet command worked. Thanks!

That error actually contains the message that you need to sign, then you need to enter everything on one line once you have the message. But good to see you got it working anyways.

A good point raised.  We will update the guide to explain this point.

[svk]

The signed message command gave me assert exception. The import wallet command worked. Thanks!

That error actually contains the message that you need to sign, then you need to enter everything on one line once you have the message. But good to see you got it working anyways.

[mhps]

 The signed message command gave me assert exception. The import wallet command worked. Thanks!

[cube]

Guess I have overlooked somewhere obvious but how do I claim the "new" PTS in the new wallet with my "old" protoshares in the old wallet?
It seems that the commandline option -datadir and -conf don't work for the new wallet, how do I get a list command line options ?

Same way you did with BitsharesX. You can use the import bitcoin wallet command, or you can avoid exposing private keys by using the new "import_wallet_by_signed_message" command that allows you to import your old balance by signing a message using the old client.

Yes, that is right.  The details are here - http://pts.cubeconnex.com/index.php?topic=66.0

[svk]

Guess I have overlooked somewhere obvious but how do I claim the "new" PTS in the new wallet with my "old" protoshares in the old wallet?
It seems that the commandline option -datadir and -conf don't work for the new wallet, how do I get a list command line options ?

Same way you did with BitsharesX. You can use the import bitcoin wallet command, or you can avoid exposing private keys by using the new "import_wallet_by_signed_message" command that allows you to import your old balance by signing a message using the old client.

[mhps]

Guess I have overlooked somewhere obvious but how do I claim the "new" PTS in the new wallet with my "old" protoshares in the old wallet?
It seems that the commandline option -datadir and -conf don't work for the new wallet, how do I get a list command line options ?

[cube]

BitShares PTS Upgrade is launched. :)

See http://pts.cubeconnex.com/index.php?topic=71.0

[pc]

Thanks for the confirmation! https://poloniex.com/exchange/btc_pts

[mobydick]

Just want to mention that Poloniex will honor the December 14th PTS snapshot.

Source?

If there is any concern about the legitimacy of my identity or validity of the statement that Poloniex will honor the snapshot, please see that I posted to our announcement board on the exchange.  I would provide a live link, but apparently they are blocked here.  poloniex (dot) com/exchange/btc_pts

[cube]

I'll just post this here as it might be of interest:
https://bitsharestalk.org/index.php?topic=12160.msg161251#msg161251

For the ypool miners, good news!

See http://pts.cubeconnex.com/index.php?topic=67.msg522#msg522

[pc]

Anyway I can get my 2080 PTS that was proven stolen back in this snapshot?

It is unfortunately the nature of blockchain technology that it is impossible to prove or disprove that a given transaction was made with or without your consent. We cannot appoint ourselves judges in this case and meddle with the snapshot in your favour (or anyone elses).

Quite the opposite. If we did move these coins back to an address under your control, this could be seen as theft. An actual theft that could easily be proved by the owner of the address currently holding your coins. And I'm not even trying to hide my identity here - I would be an easy target. I'm sorry, but I cannot help you there.

[emski]

I'll just post this here as it might be of interest:
https://bitsharestalk.org/index.php?topic=12160.msg161251#msg161251