# Bisq v1 to v2 **URL:** \ **Category:** Uncategorized\ **Created:** [May 5, 2026, 4:29pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708 "2026-05-05T16:29:20Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Machine](https://bisq.community/letter_avatar/machine/32/5_5575768a8748004e209b776fc1b2916d.png) [@Machine](https://bisq.community/u/Machine)\ **Post date:** [May 5, 2026, 4:29pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/1 "2026-05-05T16:29:20Z")
I gave someone my btc deposit address which I generate before the exploit. The deposit will be made next week, will it still arrive in the old wallet we generated? Unfortunately we are not able to update the deposit address from our side so I really hope somehow it will still arrive and I will be able to withdraw or trade with it. ---
**Author:** ![Reece505](https://bisq.community/letter_avatar/reece505/32/5_5575768a8748004e209b776fc1b2916d.png) [@Reece505](https://bisq.community/u/Reece505)\ **Post date:** [May 5, 2026, 7:24pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/2 "2026-05-05T19:24:36Z")
Hi @Machine Yes, the BTC can still arrive to the old address. But the real risk is access—if the platform changed or old wallets aren’t supported after the exploit, you might not be able to use or withdraw it. Best move: have them send to a new address if possible. ---
**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\ **Post date:** [May 5, 2026, 8:37pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/3 "2026-05-05T20:37:43Z")
you can ignore the last part of the first reply that was given to you internal wallet was not affected by the exploit, funds will be there waiting for you, you can access them even without the new hotfix release, wallet access will not be modified in that new version ---
**Author:** ![Machine](https://bisq.community/letter_avatar/machine/32/5_5575768a8748004e209b776fc1b2916d.png) [@Machine](https://bisq.community/u/Machine)\ **Post date:** [May 6, 2026, 4:03am UTC](https://bisq.community/t/bisq-v1-to-v2/13708/4 "2026-05-06T04:03:53Z")
Thank you! ---
**Author:** ![FRIDON21](https://bisq.community/letter_avatar/fridon21/32/5_5575768a8748004e209b776fc1b2916d.png) [@FRIDON21](https://bisq.community/u/FRIDON21)\ **Post date:** [May 11, 2026, 1:49pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/5 "2026-05-11T13:49:41Z")
When will there be a new version? ---
**Author:** ![militao-spbr](https://bisq.community/user_avatar/bisq.community/militao-spbr/32/3555_2.png) [@militao-spbr](https://bisq.community/u/militao-spbr)\ **Post date:** [May 11, 2026, 3:15pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/6 "2026-05-11T15:15:24Z")
We are waiting for the “in the next few days” that was mentioned here ---
**Author:** ![caoswizard](https://bisq.community/letter_avatar/caoswizard/32/5_5575768a8748004e209b776fc1b2916d.png) [@caoswizard](https://bisq.community/u/caoswizard)\ **Post date:** [May 11, 2026, 5:14pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/7 "2026-05-11T17:14:15Z")
For non developers is easy to imagine that a fix is just a little thing, but depending on the complexity of the software architecture and code design sometimes the estimatives are not reached. I’m waiting for the fix as well to sell BTC, but is better keep waiting rather than release something wich allows other attacks. ---
**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\ **Post date:** [May 12, 2026, 8:58pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/8 "2026-05-12T20:58:37Z")
it is worth to mention that releasing the new version asap is at least as important for bisq as it is for users, because trades on the platform are what pays contributors… but it would be a disaster if a fast release were to lead to yet another attack, so first and foremost the new release will have to be bulletproof, then it can be “fast” 🙂 ---
**Author:** ![hardheadarea](https://bisq.community/letter_avatar/hardheadarea/32/5_5575768a8748004e209b776fc1b2916d.png) [@hardheadarea](https://bisq.community/u/hardheadarea)\ **Post date:** [May 13, 2026, 8:14pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/9 "2026-05-13T20:14:05Z")
Yes, of course. Better to take the time. Can you explain why there was a message saying that there is already a new version to be downloaded? It was very confusing seeing this message, but not seeing a new version. Was it just a mistake, taken in the early moments of the exploit? ---
**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\ **Post date:** [May 13, 2026, 8:17pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/10 "2026-05-13T20:17:52Z")
requiring a non existing new version was the fastest way to stop trading and contain the damage ---
**Author:** ![hardheadarea](https://bisq.community/letter_avatar/hardheadarea/32/5_5575768a8748004e209b776fc1b2916d.png) [@hardheadarea](https://bisq.community/u/hardheadarea)\ **Post date:** [May 13, 2026, 9:36pm UTC](https://bisq.community/t/bisq-v1-to-v2/13708/11 "2026-05-13T21:36:09Z")
Maybe so, but that doesn’t explain why the message said that the user should download a new version. The message could just say - well, it could say what was really going on, like “the developers have instructed the app to require a mandatory upgrade, but this can not be downloaded at present” instead of saying that a new version _is_ (present tense) available. The concern, since the message in the app does not match the messaging on this forum, is that the team that performed the exploit might have sent that message to get people to upgrade to _their_ version of Bisq. Otherwise, why was the messaging (like what you said above) different from what is in the app? This is fairly basic exploit recovery/management, especially for an app with bank account information. It’s important to address this (and to use the GPG key with fingerprint B493319106CC3D1F252E19CBF806F422E222AA02 to sign the new release, once the new release is out.) ---
**Author:** ![suddenwhipvapor](https://bisq.community/user_avatar/bisq.community/suddenwhipvapor/32/3291_2.png) [@suddenwhipvapor](https://bisq.community/u/suddenwhipvapor)\ **Post date:** [May 14, 2026, 6:18am UTC](https://bisq.community/t/bisq-v1-to-v2/13708/12 "2026-05-14T06:18:11Z")
This is my final response regarding the misinformation that I read from you about about Bisq. Both topics have been addressed in prior threads: rationale of “new version” requirement popup and signing of new releases. Continued crossposting of unverified claims will not be tolerated, as it disrupts discussion.