# Bisq v.5.0 not updating from old app nothing carried over either

**URL:** <https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366>\
**Category:** Support\
**Created:** [June 28, 2017, 10:20pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366 "2017-06-28T22:20:44Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![scarar](https://bisq.community/letter_avatar/scarar/32/5_5575768a8748004e209b776fc1b2916d.png) [@scarar](https://bisq.community/u/scarar)\
**Post date:** [June 28, 2017, 10:20pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/1 "2017-06-28T22:20:44Z")

</div>

I started the new version, but nothing was carried over. I even Restored my wallet and still nothing was restored from old app. Is their a way to use ALL my info from the old app version 4.9.9.3 into v0.5.0 ?

---

<div class="post-metadata">

**Author:** ![in-cred-u-lous](https://bisq.community/letter_avatar/in-cred-u-lous/32/5_5575768a8748004e209b776fc1b2916d.png) [@in-cred-u-lous](https://bisq.community/u/in-cred-u-lous)\
**Post date:** [June 28, 2017, 11:01pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/2 "2017-06-28T23:01:24Z")

</div>

As stated in the announcement:

> As that release has very profound changes it is NOT backward compatible to the earlier versions.  
> It uses a new network which is separated from the current trade network. So your offers from the current application will not be visible for users who are using the new version.  
> If you want to migrate to the new version you need to close your offers and withdraw your funds to the new application. You can run both applications in parallel as they are using a different data directory.  
> You cannot move over the wallet or application data because the wallet format has changed (BIP44) and we use a different data structure for the data base files. So you need to transfer the Bitcoin with a BTC transaction and set up your payment account(s) manually.

---

<div class="post-metadata">

**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\
**Post date:** [June 29, 2017, 12:18am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/3 "2017-06-29T00:18:23Z")

</div>

As in-cred-u-lous said, it is not compatible with an earlier version. It is practically a different program. Different network, different protocol, different files, different name… It is nice to have something brand new 🙂

---

<div class="post-metadata">

**Author:** ![MnM](https://bisq.community/user_avatar/bisq.community/mnm/32/257_2.png) [@MnM](https://bisq.community/u/MnM)\
**Post date:** [June 29, 2017, 9:26am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/4 "2017-06-29T09:26:28Z")

</div>

I came here looking for that exact problem.  
If we have to restart the wallets, we’re going to lose some reputation in the exchange, and it’s possible that in the future this will be something valuable in bisq.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 29, 2017, 2:59pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/5 "2017-06-29T14:59:09Z")

</div>

Yes that is a drawback. I am sorry but the changes was just too much to make it backward compatible, or it would have taken another 3 months…

---

<div class="post-metadata">

**Author:** ![MnM](https://bisq.community/user_avatar/bisq.community/mnm/32/257_2.png) [@MnM](https://bisq.community/u/MnM)\
**Post date:** [June 30, 2017, 10:23am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/6 "2017-06-30T10:23:25Z")

</div>

Do you think that there might be any possibility to “rescue” at least only the reputation, somehow, from the old “accounts”?

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 30, 2017, 11:55am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/7 "2017-06-30T11:55:01Z")

</div>

i will look into it…

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 30, 2017, 11:57am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/8 "2017-06-30T11:57:12Z")

</div>

one thing is that u need to copy over the tor private\_key and hostname.  
…/tor/hiddenservice/hostname  
…/tor/hiddenservice/private\_key

with that u have the same network ID (onion address)

not sure if that is enough though… will check out later…

---

<div class="post-metadata">

**Author:** ![6wAotI](https://bisq.community/letter_avatar/6waoti/32/5_5575768a8748004e209b776fc1b2916d.png) [@6wAotI](https://bisq.community/u/6wAotI)\
**Post date:** [June 30, 2017, 6:24pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/9 "2017-06-30T18:24:30Z")

</div>

Sorry but isnt it possible to export accounts below on the button to Export Accounts. Wont that make the process a little easier? or is that also not compatible to import it into the new version?

---

<div class="post-metadata">

**Author:** ![6wAotI](https://bisq.community/letter_avatar/6waoti/32/5_5575768a8748004e209b776fc1b2916d.png) [@6wAotI](https://bisq.community/u/6wAotI)\
**Post date:** [June 30, 2017, 6:28pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/10 "2017-06-30T18:28:33Z")

</div>

Also. Honestly, i personally only care about Transactions and History tabs to be easily imported. I know it can be exported to CSV, but to import it is a problem.

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 30, 2017, 9:31pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/11 "2017-06-30T21:31:04Z")

</div>

No the data format has changed

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [June 30, 2017, 9:32pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/12 "2017-06-30T21:32:24Z")

</div>

It is just work to build some import tool. Import was also not supported int eh old version.  
Any dev could help here, a low hanging fruit… But I have too much other things on my table…

---

<div class="post-metadata">

**Author:** ![6wAotI](https://bisq.community/letter_avatar/6waoti/32/5_5575768a8748004e209b776fc1b2916d.png) [@6wAotI](https://bisq.community/u/6wAotI)\
**Post date:** [July 1, 2017, 12:08am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/13 "2017-07-01T00:08:54Z")

</div>

@ManfredKarrer eventually i just used half an hour to setup everything again. Not a big deal, reputation can always be rebuilt i guess.

---

<div class="post-metadata">

**Author:** ![fab](https://bisq.community/letter_avatar/fab/32/5_5575768a8748004e209b776fc1b2916d.png) [@fab](https://bisq.community/u/fab)\
**Post date:** [July 12, 2017, 9:16pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/14 "2017-07-12T21:16:45Z")

</div>

Hello,

I just tried to paste over my old Bitsquare data (tor private\_key and hostname) to my new Bisq directory but it didn’t worked out.  
I would be nice to keep track of our reputation…

---

<div class="post-metadata">

**Author:** ![scarar](https://bisq.community/letter_avatar/scarar/32/5_5575768a8748004e209b776fc1b2916d.png) [@scarar](https://bisq.community/u/scarar)\
**Post date:** [July 13, 2017, 12:05am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/15 "2017-07-13T00:05:36Z")

</div>

Has the Devs be able to help with the reputation to be carried over? Maybe have a backup option that saves the rep in a .json or some other type that the new update/upgrades wouldn’t affect it during compile of new programming syntax. If Devs is able to give insight on this that be great. 😉

V/r

Scarar

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [July 13, 2017, 10:08am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/16 "2017-07-13T10:08:19Z")

</div>

I am too busy with a new release (additional security features, remove requirement for email exchange and id check, add in-app downloader with automatic sig check) and with completing the DAO and preparing 100 things regarding DAO launch (mainly to get our weakness in the communication area solved, e.g. find a dedicated person for it).

So no, I did not had time to look into it more closely and I fear it is too late to fix that.  
The main reason is that the reputation is based on the onion address. If users have already offers they cannot change the onion address. So it does not help you if you change it for yourself and get the reputation data imported, but you would need that all your past trade peers also change back to the old onion address, which will not happen if they have already offers/trades going on. Beside that I never tested if changing the onion address will have further side effects, so I don’t recommend to do that.  
I am sorry that I did not implement that in the 0.5.0 release, but it would have added another delay and I was not aware that this feature is so highly appreciated by users.

You can see it also positive as that with a new onion address you get disconnected from previous trade activities which gives you more privacy. The reputation has always 2 sides and some people value privacy higher than the reputation history. In future we probably add a feature to optionally renew the onion address exactly for the privacy reason (but it would reset reputation history, you cannot have both but its the users choice).

Beside that it is NOT a security feature. A scammer could build up reputation and then abuse that (long con).

So in summary: I fear that train has left, sorry. Please keep in mind that such a “hardfork” update is exceptional and the first after more than one year since we launched. Once we have more developers we also will have better resources to plan such an event better in future.

---

<div class="post-metadata">

**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\
**Post date:** [July 13, 2017, 11:34am UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/17 "2017-07-13T11:34:46Z")

</div>

You can use that hidden service directory to make a website on that onion address that can point to the new onion address, if it helps.

Maybe even an onion proxy…who knows…

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [July 13, 2017, 12:16pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/18 "2017-07-13T12:16:34Z")

</div>

Interesting idea 😉

---

<div class="post-metadata">

**Author:** ![shrike](https://bisq.community/letter_avatar/shrike/32/5_5575768a8748004e209b776fc1b2916d.png) [@shrike](https://bisq.community/u/shrike)\
**Post date:** [July 13, 2017, 1:51pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/19 "2017-07-13T13:51:20Z")

</div>

> [@ManfredKarrer](#):
>
> You can see it also positive as that with a new onion address you get disconnected from previous trade activities which gives you more privacy. The reputation has always 2 sides and some people value privacy higher than the reputation history. In future we probably add a feature to optionally renew the onion address exactly for the privacy reason (but it would reset reputation history, you cannot have both but its the users choice).

👍

---

<div class="post-metadata">

**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\
**Post date:** [July 13, 2017, 10:30pm UTC](https://bisq.community/t/bisq-v-5-0-not-updating-from-old-app-nothing-carried-over-either/2366/20 "2017-07-13T22:30:45Z")

</div>

Check out [https://forum.bisq.io/t/new-requirement-for-payment-accounts-with-charge-back-risk/2376/65](https://forum.bisq.io/t/new-requirement-for-payment-accounts-with-charge-back-risk/2376/65)

There might come a new form of reputation. Not planned immediately as not enough time yet but seems we found a good solution for a decentralized and privacy protecting reputation system.
