BitShares Forum
Main => General Discussion => Topic started by: emailtooaj on September 10, 2015, 02:19:57 am
-
Seeing that Operation PitchFork 2.0 has just been announced and is underway; IMO it would make sense starting a Pregame to-do check list.
Doing this will help avoid countless and redundant threads of people asking "How do I import my old BTS wallet to the new one?"
So maybe we can use this thread as a brainstorm for a temporary "how to" template and then create a Sticky of it once it's cleaned up and organized?
- What Steps Should I Take Saving My Old BTS Wallet Before Migrating?
First you should update to the most current BTS wallet (v0.9.2). Download links here... https://github.com/bitshares/bitshares/releases/tag/bts%2F0.9.2
*note- please be aware BTS may have one more wallet update from v0.9.2 making migrating easier... so these steps may have to be done one more time*
(Windows) Here's a quick how-to for updating older wallet versions to v0.9.2
1. For your current client version, copy the C:\Users\*account name*\AppData\Roaming\Bitshares\wallet directory as a backup in another dir. (Export your wallet as .json as well for safety). If you don't have the wallets dir, create it by importing your .json file & running the client.
(IMPORTANT-Make sure you're 120% positive you did step 1 correclty BEFORE proceeding!!!)
2. Uninstall your current version by deleting the C:\Users\*account name*\AppData\Roaming\Bitshares folder. Reboot Windows
3. Install v0.9.2. Before running the new client do these initial steps...
a) go to your C:\Program Files\Bitshare\bin folder and right click BitShares.exe, go to properties>compatibility and check mark "Run this program as Admin".
Please do this same step for the bitshares_client.exe.
b) Make sure firewalls are set to allow Bitshares.exe and are not blocking it. Set it to allow for "Private" and "Public" network access (just in case).
4. Now launch the BTS wallet (click yes when Admin rights pop-up) and let it download and sync the network (*fingers crossed)
5. If wallet sync was successful... Close the program... go back to C:\Users\*account name*\AppData\Roaming\Bitshares\wallet and proceed to copy and paste your old wallet
backup (from step 1) over the newest Bitshares dir.
6. Run the new client again, enter password, allow it to re-scan for transaction history and you should be up and running.
- Where Can I Get The New 2.0 Wallet?
Actually... you don't need to download anything!
BitShares 2.0 front-end (UI) is now browser-based, so continue using your favorite Firefox, Chrome or Windows browsers.
If you want to help support the networks back-end, you can either download the full node software (witness node)
or the GUI and host your own wallet (graphene-ui).
Both are hosted here on github _____link to github?_____
- I Have Multiple Accounts In My Current Wallet, Now What?
You can import all of your accounts and funds easily.
Under Bitshares 2.0 you'll be given a choice as to which "New" account you would like your previous balances/funds transferred to.
- What Steps Are Involved To Transferring My Account(s) Into Graphene BTS 2.0?
Upon opening the BTS2.0 wallet (per web browser) you'll be prompted to import the wallet data that you exported from BTS1.
***Note*** Importing your wallet data does NOT mean you're uploading your wallet details to some other's server.
All key management is secured on your end and is stored within your local browser database.
Hence, the browser will offer a tool to help make regular backups as often as you'd like!
- I Currently Have a UIA. What Steps Should I Take Before Migrating?
Erm .. None!
- What If I Still Have Unclaimed BTS From The Genesis and/or
Unclaimed Vested BTS From The Merger?
Should I Claim My Stack From The Genesis Before Migrating To Bitshares 2.0?
Genesis stake will move over as is. All vesting balances should report correctly and still appear as vesting in BTS 2.0
- What's The Status Regarding Privacy of Transactions in 2.0? Give Me The tl;dr?
There will be Blinded, Stealth, and Stealth-blinded transactions.
Blinded: transactions will "hide" the amount and keep everything else readable by everyone
Stealth: addresses remove the identity of the receiver
Stealth-Blinded: is a transaction with "hidden" amount to an unknown receiver.
***Keep in mind that stealth addresses will not work on web wallets AFAIK.
- Will Leaving My BTS On External Exchanges Be Converted Automatically Into BTS 2.0?
During any snapshot or migration period it's ALWAYS advised to move ALL funds off ANY External Exchanges and into your local wallet that YOU have the Keys too!!
Doing this is a sure fire way of keeping your funds safely in your control while going through the transition phase. In addition this will allow you to backup your nest egg!!
Otherwise, you're trusting any External Exchange (ie 3rd Party) to honor the snapshot/migration period and hoping nothing gets botched up and lose your BTS funds.
***NOTE*** If you have BTS/Assets on the DEX (Bitshares Internal Decentralized Exchange) there's no need to remove funds.
Trading will stop and any outstanding funds will be refunded to the their appropriate accounts.
_______________________________________________________________________________________________________________________________________________
Anyone in the Community can chime in and post additional info/answers/topics/questions.
Once compiled I'll take the posted information, clean it up, make a new Thread and see if we can't make it a sticky.
I find this could be very helpful, do you?
If so, please help :P
-
thanks for this much needed thread.
Also minimum or recommended computer and operating system requirements.
-
Seeing that Operation PitchFork 2.0 has just been announced and is underway; IMO it would make sense starting a Pregame to-do check list.
Doing this will help avoid countless and redundant threads of people asking "How do I import my old BTS wallet to the new one?"
So maybe we can use this thread as a brainstorm for a temporary "how to" template and then create a Sticky of it once it's cleaned up and organized?
Good idea .. Let me contribute some answers:
What Steps Should I Do Before Saving My Old BTS Wallet Before Migrating?
Unless you are missing some of your funds you are good to go by simply exporting
your wallet. As far as I know the exported file needs a proper format and a
special function is already implemented in the sources of the BTS 0.9 client.
Either the devs will release a new BTS0.9 version with a prominent new button or
there will be a distinct tool to convert your regular exports into graphene
import format.
Where Can I Get The New 2.0 Wallet?
Actually .. you don't need to download anything. BitShares 2.0 will be
browser-based ... at least the frontned.
If you want to participate, you can either download the full node software
(witness node) or the GUI and host your own wallet (graphene-ui). Both are
hosted on github.
I Have Multiple Accounts In My Current Wallet, Now What?
You can import all of them easily and you will be given the choice where you
want to import which of your balances/funds.
What Steps Are Involved To Transferring My Account(s) Into Graphene BTS 2.0?
Upon opening the BTS2.0 wallet (per web browser) you will be asked to import
your wallet exported from BTS1. Note that importing does *not* mean you upload
your wallet to some other's server. All key management is done on your end, in
the browser and stored in a local browser database. Hence, the browser will
offer a tool to make regular backups again!
I Currently Have a UIA. What Steps Should I Take Before Migrating?
Erm .. None!
-
What if I still have some unclaimed BTS allocation from the genesis and/or vesting BTS from merger? Should i claim my stack from the genesis before migrating to bitshares 2.0?
-
What is the status of the privacy of transactions in 2.0? I have been away traveling for a few weeks now and only occasionally check. Could someone provide the tl;dr?
-
Migrating: https://bitshares.org/blog/2015/06/08/migrating-to-bitshares-2.0/
-
Thanks to everyone who's helped out so far ;D
@Xeroc - do we have a general idea which direction will be used for the wallet export function? A new 0.9.5 wallet update or stand alone tool?
@fav - thanks for the link. I'll integrate what I can into this thread
-
Thanks to everyone who's helped out so far ;D
@xeroc - do we have a general idea which direction will be used for the wallet export function? A new 0.9.5 wallet update or stand alone tool?
@fav - thanks for the link. I'll integrate what I can into this thread
IIRC, there will be another wallet pre-release to format the wallet/make integration easier. (was mentioned in one of the hangouts)
-
*bump
added material
-
What if I still have some unclaimed BTS allocation from the genesis and/or
vesting BTS from merger? Should i claim my stack from the genesis before
migrating to bitshares 2.0?
Genesis stake is moved over as is. Vesting balances should appear as vesting in
BTS2 again.
What is the status of the privacy of transactions in 2.0? I have been away
traveling for a few weeks now and only occasionally check. Could someone provide
the tl;dr?
There will be blinded, stealth, and stealh-blinded transactions. Blinded
transactions "hide" the amount and keep everything else readable by everyone,
while stealth addresses remove the idendity of the receiver .. combined they is
a transaction with "hidden" amount to an unknown receiver. Through keep in mind
that stealth addresses will not work on web wallets AFAIK.
@Xeroc - do we have a general idea which direction will be used for the wallet
export function? A new 0.9.5 wallet update or stand alone tool?
I think there will be a wallet release of verison 0.9.3 .. or maybe they call it
1.0 for the fun :)
-
@Xeroc Thanks for helping with this!!
I think there will be a wallet release of verison 0.9.3 .. or maybe they call it
1.0 for the fun :)
Yes, that would be! The shortest lived v1.0 in history :P
@everyone else, Great questions!! Keep'em coming. If you can think of any other migrating questions/issues please post them!!
I'll be sure to get it updated :D
-
It would be nice to have a screencast video showing exactly how to migrate from v0.9x to v2.0
-
I understand that BTS2 is not a snapshot but an upgrade. So leaving BTS1 in external exchanges will get converted automatically to BTS2 or do we need to move BTS1 to our wallets?
-
I understand that BTS2 is not a snapshot but an upgrade. So leaving BTS1 in external exchanges will get converted automatically to BTS2 or do we need to move BTS1 to our wallets?
Good one! I'll add this to the OP
-
Since BitUSD interest will be removed in 2.0, what will happen to BitUSD interest on the switch? Will the fund in the pool be dispatched to all BitUSD holders on a shot?
-
I'm curious what will happen to UIA names after the switch? I haven't been able to get information on whether we will be able to keep the MKRCOIN name.
-
does I have the old translation history ?
-
I'm curious what will happen to UIA names after the switch? I haven't been able to get information on whether we will be able to keep the MKRCOIN name.
Yes, you still have your UIAs.
-
does I have the old translation history ?
No you do not.. Assuming you mean transaction history.. that will disappear. Your balance stays, but your transaction history goes.
-
Once i am using BTS 2.0 via a hosted web wallet and my keys are stored locally in my web browser, what happens if i clear my browser cache?
I'm guessing keys can be loaded into multiple browsers so as to have access from different devices without causing issues?
-
Once i am using BTS 2.0 via a hosted web wallet and my keys are stored locally in my web browser, what happens if i clear my browser cache?
I'm guessing keys can be loaded into multiple browsers so as to have access from different devices without causing issues?
Great question!
-
Once i am using BTS 2.0 via a hosted web wallet and my keys are stored locally in my web browser, what happens if i clear my browser cache?
I'm guessing keys can be loaded into multiple browsers so as to have access from different devices without causing issues?
After you have created your wallet you want to create a backup.
As I understand it (devs chime in if I am off) it will be the similar type of tech wallet.bitshares.org uses.. so what you want to do is as soon as you have created your account, create a backup file. This will save you from browser cache erasure.
For other devices I would guess you can use that backup to then load into your other devices for us. (again devs can correct me if I am wrong)
-
What is the status of the privacy of transactions in 2.0? I have been away
traveling for a few weeks now and only occasionally check. Could someone provide
the tl;dr?
There will be blinded, stealth, and stealh-blinded transactions. Blinded
transactions "hide" the amount and keep everything else readable by everyone,
while stealth addresses remove the idendity of the receiver .. combined they is
a transaction with "hidden" amount to an unknown receiver. Through keep in mind
that stealth addresses will not work on web wallets AFAIK.
Will this be implemented when the 2.0 comes out or is left to be implemented later?
-
What is the status of the privacy of transactions in 2.0? I have been away
traveling for a few weeks now and only occasionally check. Could someone provide
the tl;dr?
There will be blinded, stealth, and stealh-blinded transactions. Blinded
transactions "hide" the amount and keep everything else readable by everyone,
while stealth addresses remove the idendity of the receiver .. combined they is
a transaction with "hidden" amount to an unknown receiver. Through keep in mind
that stealth addresses will not work on web wallets AFAIK.
Will this be implemented when the 2.0 comes out or is left to be implemented later?
@dev
I'm almost certain this will be implemented at launch.
Dan was talking about this structure a couple months ago.
-
Once i am using BTS 2.0 via a hosted web wallet and my keys are stored locally in my web browser, what happens if i clear my browser cache?
I'm guessing keys can be loaded into multiple browsers so as to have access from different devices without causing issues?
After you have created your wallet you want to create a backup.
As I understand it (devs chime in if I am off) it will be the similar type of tech wallet.bitshares.org uses.. so what you want to do is as soon as you have created your account, create a backup file. This will save you from browser cache erasure.
For other devices I would guess you can use that backup to then load into your other devices for us. (again devs can correct me if I am wrong)
@datasecuritynode
Thanks for helping out [emoji2]
-
What is the status of the privacy of transactions in 2.0? I have been away
traveling for a few weeks now and only occasionally check. Could someone provide
the tl;dr?
There will be blinded, stealth, and stealh-blinded transactions. Blinded
transactions "hide" the amount and keep everything else readable by everyone,
while stealth addresses remove the idendity of the receiver .. combined they is
a transaction with "hidden" amount to an unknown receiver. Through keep in mind
that stealth addresses will not work on web wallets AFAIK.
Will this be implemented when the 2.0 comes out or is left to be implemented later?
@dev
I'm almost certain this will be implemented at launch.
Dan was talking about this structure a couple months ago.
Yes, it's confirmed here (https://bitshares.org/blog/2015/09/11/BitShares-2.0-Launching-on-October-13th/):
2. Added Confidential / Stealth Transfers
One of the things we lamented in our original announcement was that bitcoin-style privacy was an illusion. Ironically on the same day we announced Graphene and BitShares 2.0 Blockstream released an implementation of Confidential Transactions which is well understood and computationally viable. After reviewing their approach we decided to implement them in Graphene for BitShares 2.0.
Confidential Transfers hide the amounts being transfered while still allowing those who validate the blockchain to verify that the balances transfered sum to 0 and are not negative. Stealth transfers are used to automatically generate a unique key for every transfer. The combination of these two features means that it becomes pratically impossible for a 3rd party to identify how much you have sent or received or who is sending money to whom.
If you are willing to reveal who is sending to whom (but not how much) then it is even possible to use confidential transfers with regular hierarchical threshold multi-sig accounts.
Currently the web wallet does not support generating or receiving confidential transactions, but the command line wallet has full support for them. More details on how to use confidential/stealth transfers will be made available in the weeks ahead.
-
There is a draft release that has the necessary rpc command to export keys easily for graphene. You can test importing it into the test net
Sent from my iPhone using Tapatalk