# Trade limit downgraded **URL:** \ **Category:** Support\ **Created:** [December 20, 2018, 5:31pm UTC](https://bisq.community/t/trade-limit-downgraded/6811 "2018-12-20T17:31:17Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 20, 2018, 5:31pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/1 "2018-12-20T17:31:17Z")
Hi, After upgrading to 0.9.1 (without doing anything else) my trade limit was reset, going back to 0.0625. Was that expected? Thanks ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [December 20, 2018, 6:31pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/2 "2018-12-20T18:31:06Z")
Hi @mirelo , Do you know if your onion address with this 0.9.1 upgrade is the same as before ? It’s in Settings/Network Info/P2P network. What is your OS also ? ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 20, 2018, 6:43pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/3 "2018-12-20T18:43:04Z")
The address in …/btc\_mainnet/tor/hiddenservice/hostname is the same in the current installation as in my last backup before the upgrade. My OS is Linux Mint 19 Tara ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [December 20, 2018, 7:43pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/4 "2018-12-20T19:43:45Z")
ah, that’s strange. You may find help with this post: [How to switch to a new data directory](https://bisq.community/t/how-to-switch-to-a-new-data-directory/6753) Following the _How to keep my onion address and with that my local reputation?_ section. But do all necessary backups before. Of course, in such cases it’s always better to not have any offers/trades/disputes open. Hopefully it’s not your case ? Please keep us informed if this works. ---
**Author:** ![alexej996](https://bisq.community/user_avatar/bisq.community/alexej996/32/491_2.png) [@alexej996](https://bisq.community/u/alexej996)\ **Post date:** [December 20, 2018, 9:42pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/5 "2018-12-20T21:42:08Z")
Have you made a new account in Bisq? It is odd that it can reset itself just like that. Try restarting your PC of course, as usual, just in case. ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 21, 2018, 4:03am UTC](https://bisq.community/t/trade-limit-downgraded/6811/6 "2018-12-21T04:03:12Z")
I tried creating a new, empty “Bisq” directory and restoring the backup I have from before the upgrade, and the application tells me: _Account age: 2 days_. My **sig.key** file still has the same date as in the backup (while its backup has today’s date). Then I tried: - Exporting my account (from the restored installation). - Shutting down Bisq. - Creating a new, empty “Bisq” dir. - Restoring my backup **sig.key** file into “btc\_mainnet/keys”. - Starting Bisq. - Importing my account. After doing which the salt (for account age verification) didn’t change, and yet the application tells me my account is only 2 days old, which is false. ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 21, 2018, 4:20am UTC](https://bisq.community/t/trade-limit-downgraded/6811/7 "2018-12-21T04:20:21Z")
I restarted my computer, same thing. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [December 21, 2018, 11:27am UTC](https://bisq.community/t/trade-limit-downgraded/6811/8 "2018-12-21T11:27:07Z")
Hm… are you shure the account data and the salt are exactly the same and the sig key is the same. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [December 21, 2018, 11:28am UTC](https://bisq.community/t/trade-limit-downgraded/6811/9 "2018-12-21T11:28:12Z")
You can try to delete the AccountAgeWitnessStore file inside the db folder and then restart. ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 21, 2018, 11:40am UTC](https://bisq.community/t/trade-limit-downgraded/6811/10 "2018-12-21T11:40:25Z")
I reinstalled version 0.8.1, and it raised back my trade limit, recognizing the age of my account correctly. I will now try to delete the AccountAgeWitnessStore and upgrade again to 0.9.1. ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 21, 2018, 11:47am UTC](https://bisq.community/t/trade-limit-downgraded/6811/11 "2018-12-21T11:47:42Z")
I upgraded again to 0.9.1, deleted the file, started the application, and it still says my account is 2 days old. I closed the application, deleted the file and also the backup directory, restarted the application, same result. ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 21, 2018, 12:13pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/12 "2018-12-21T12:13:36Z")
I copied the salt, closed and removed version 0.9.1, reinstalled 0.8.1, restored my backup, started 0.8.1, then checked the salt, and it is the same. Again, 0.8.1 gives me back my old trade limit, recognizing my account’s age correctly. ---
**Author:** ![Homard](https://bisq.community/letter_avatar/homard/32/5_5575768a8748004e209b776fc1b2916d.png) [@Homard](https://bisq.community/u/Homard)\ **Post date:** [December 21, 2018, 1:40pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/13 "2018-12-21T13:40:42Z")
Thanks for all those trials @mirelo (… we scratch our heads ) ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 21, 2018, 1:46pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/14 "2018-12-21T13:46:33Z")
If you have new ideas of what to test to narrow down the problem, please let me know. ---
**Author:** ![ManfredKarrer](https://bisq.community/user_avatar/bisq.community/manfredkarrer/32/26_2.png) [@ManfredKarrer](https://bisq.community/u/ManfredKarrer)\ **Post date:** [December 23, 2018, 12:31pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/15 "2018-12-23T12:31:14Z")
I just tested with my own app and could not see any issue. Are you 100% sure you use the same data directory. You could add --appName=Bisq0-8-1 --appName=Bisq0-9-1and to run 2 instances at the same time with the different versions. Downgrading - once u used 0.9 and got back to 0.8 might be problematic (is not tested). Do you run the default binary or run from a locl jdk (from source)? As said the relevant file is the sig.key, and the relevant data are the account data (u can export, import) and the salt. If those 3 components are the same all should be correct. ---
**Author:** ![mirelo](https://bisq.community/user_avatar/bisq.community/mirelo/32/111_2.png) [@mirelo](https://bisq.community/u/mirelo)\ **Post date:** [December 27, 2018, 3:27pm UTC](https://bisq.community/t/trade-limit-downgraded/6811/16 "2018-12-27T15:27:43Z")
I uninstalled everything, restored my November backup, and installed 0.9.1. Then, I uninstalled everything again, restored my November backup, and installed 0.8.1. My account (with the same salt) had aged the same number of days in both versions, but with its age reset in 0.9.1. It’s as if the reset had happened sometime after the backup but before installation, although that information would not be stored anywhere. Could it be an age overflow due to some field type change?