Bisq2 v2.1.14 has been released.

Please update as soon as possible!

https://github.com/bisq-network/bisq2/releases/tag/v2.1.14

Bisq v1.10.9 is released.

This important security update fixes vulnerabilities identified during our recent security audit and includes the latest Tor security release.

Updating to this version is required to continue trading.

https://github.com/bisq-network/bisq/releases/tag/v1.10.9

Bisq v1.10.8 is released.

This important security update fixes vulnerabilities identified during our recent security audit.

Updating to this version is required to continue trading.

https://github.com/bisq-network/bisq/releases/tag/v1.10.8

Bisq 2 v2.1.13 is released

This is an important security update which includes the latest Tor security release.

Updating to this version is required to continue trading.

https://github.com/bisq-network/bisq2/releases/tag/v2.1.13

Bisq v1.10.7 is now available.

This hotfix resolves DAO resync issues caused by corrupted DAO data included in versions 1.10.5 and 1.10.6.

Please update as soon as possible:

https://github.com/bisq-network/bisq/releases/tag/v1.10.7

Bisq v1.10.6 is released.

This hotfix resolves the altcoin trading bug introduced in v1.10.5.

Updating is required to continue trading and using the Bisq DAO.

For failed altcoin trades, please open mediation and do not move them to “Failed Trades” yet.

https://github.com/bisq-network/bisq/releases/tag/v1.10.6

Bisq 2 v2.1.12 is available

This is an important security update that fixes vulnerabilities identified during our recent security audit. Updating to this version is required to continue trading.

Reputation Privacy and Integrity

• Account-age and signed-witness reputation is bound to proven ownership and the requesting Bisq 2 profile.
• Public reputation records use a nullifier and day bucket rather than raw witness identifiers and exact timestamps.
• Legacy and conflicting claims receive conservative scoring.

Bonded Roles

• Bonded-role registrations identify the exact accepted proposal and lockup transaction.
• Oracle-authored registrations are persisted, recovered, and revalidated against Bisq 1 DAO state.
• Bonded-reputation unlock status is committed to oracle signatures.

Bridge Reliability

• Bisq 1 bridge state recovery enforces contiguous blocks, handles gaps and duplicates, and replays buffered blocks after catch-up.
• RPC deadlines and fail-safe retry behavior prevent an unavailable bridge from blocking interactive services.

Update from inside the Bisq app or from the Github release page: https://github.com/bisq-network/bisq2/releases/tag/v2.1.12

Altcoin trading temporarily disabled

Due to a bug introduced in Bisq v1.10.5, altcoin trades are currently failing. To prevent further failed trades, we have temporarily disabled altcoin trading. We are working on a fix and will release an update as soon as possible. Altcoin trading will be re-enabled once the fix is available. The failed trades should be automatically recovered with the new release and don't need to be handled by mediation.

We apologize for the inconvenience.

Bisq v1.10.5 is released.

This important security update fixes vulnerabilities identified during our recent security audit.

Updating to this version is required to continue trading and for using the Bisq DAO.

https://github.com/bisq-network/bisq/releases/tag/v1.10.5

Bisq v1.10.4 is released.

This important security update fixes vulnerabilities identified during our recent security audit.

Updating is required to continue trading. BSQ Swaps are re-enabled.

Release notes

This is an important security update that fixes vulnerabilities identified during our recent security audit. Updating to this version is required to continue trading. BSQ Swaps have also been re-enabled.

Security

• DAO block signatures: DAO blocks received from the network can now be signed by trusted BSQ block providers. Bisq verifies these signatures before accepting the blocks.
• Blind-vote validation: Bisq rejects blind votes whose encrypted payload does not match the on-chain commitment, and decrypts vote results only from the ballots that match the majority hash.
• Dispute-opening validation: New dispute cases are validated before being accepted. Disputes that fail validation are rejected.
• Arbitrator-witness signatures: Signed witness records are now checked for valid DSA signatures before being used for account aging.
• Seed-only data filtering: Network data that is intended to come only from seed nodes is now rejected when received from non-seed peers.
• Price-zero offer rejection: Offers with a price of zero are rejected and not added to the offer book.
• Burning Man fee routing: The Burning Man distribution address list is now used when selecting BTC fee receivers.
• Trusted seeds: Trusted seed nodes are used during network bootstrap.

Other changes

• Alert authors can remove all alerts they created.
• Legacy arbitrator data has been removed from trade and deposit flows. https://blossom.primal.net/740a78a73a45eb66a72c3ec1ff0f32e6272fe1feea4dbe9fd86693f285a1851e.png

Why can a decentralized exchange halt trading or temporarily deactivate features?

This question comes up regularly, and it's a fair one.

First, these measures are not strictly enforced. Users can opt out by starting Bisq with the ignoreDevMsg=true program argument. This option exists to ensure developers cannot unilaterally force restrictions on users.

The purpose of these emergency mechanisms is to help prevent greater harm in exceptional situations, such as the May 1 security incident or the recent discovery of critical vulnerabilities. In those cases, temporarily disabling certain functionality is the safest way to reduce the risk of users losing funds while a fix is being prepared and deployed.

Why not leave that decision entirely to users?

The challenge is that disclosing the details of a critical vulnerability before a fix is widely available would also reveal the information needed to exploit it. That means users would have to make a decision without access to the very information that would allow them to assess the risk. In practice, this makes informed individual decision-making difficult.

Isn't that centralized?

Emergency mechanisms like this are not unique to Bisq. Bitcoin itself originally included an Alert system that allowed developers to notify users of critical issues. Once Bitcoin had matured and the ecosystem no longer depended on it, that feature was removed.

Bisq is still evolving and operates in a very different environment, with a smaller user base and more rapid protocol development. At its current stage, we believe these emergency tools provide an important layer of protection against severe incidents.

At the same time, users who prefer full control can opt out of these protections. That choice is respected, but it also means accepting responsibility for the additional risk. If emergency warnings or temporary safeguards are intentionally bypassed and an exploit occurs, the Bisq project cannot provide support or compensation for resulting losses.

Update from our security audit:

It was unfortunate that we had to halt trading, but we are sure you understand that security comes first.

Our security audit identified two critical vulnerabilities affecting the trade protocol and dispute handling. If exploited, they could have led to the loss of users' funds. Those issues, along with several other security improvements, have been fixed in the 1.10.3 release.

Our audit is still ongoing and will continue to address additional, less critical issues in upcoming releases. One remaining issue affects BSQ swaps and is considered critical. To avoid putting users at risk, we have decided to temporarily disable BSQ trading until a fix is available.

We hope to release an update removing that restriction soon.

Please understand that Bisq is not a company with the luxury of a dedicated communications department. We fully recognize the importance of keeping our users informed during situations like this, but our contributors are already working overtime to complete the audit, implement fixes, and prepare releases. The limited communication is a consequence of focusing our efforts on resolving the security issues as quickly and safely as possible.

Thank you for your understanding.

Release 1.10.3 has been released.

This important security update closes vulnerabilities in trade protocol validation, message authentication, and filter safety.

Please update as soon as possible.

Download the release from within the app or from GitHub:

https://github.com/bisq-network/bisq/releases/tag/v1.10.3

Update on the trading halt:

We are close to publishing a new release, provided the final testing and audit do not reveal any further issues. Thanks for your patience and understanding. Security has the highest priority for Bisq.

As a precautionary measure, trading on Bisq 1 has been temporarily halted until a security update is released. The update is expected very soon. We apologize for the inconvenience, but we're sure you'll agree that security comes first. Open trades can be resumed after updating.

A new Bisq release (v1.10.2) is available.

All users are strongly encouraged to update as soon as possible.

Release highlights: • Strengthens DAO consensus validation and merit verification. • Improves precision in DAO voting and issuance calculations. • Adds protections against invalid consensus states. • Includes extensive regression testing to ensure consensus integrity and compatibility.

Update directly from within Bisq or download here:

https://github.com/bisq-network/bisq/releases/tag/v1.10.2

https://bisq.network/blog/where-bisq-stands-after-security-incident/ https://blossom.primal.net/71ae7f8be9a816d4a35cc2d6ec1029283524e1bbfb17a2772a60421130788ac5.png

Bisq v1.10.1 has been released

https://github.com/bisq-network/bisq/releases/tag/v1.10.1

This release mainly addresses concerns about the overly restrictive trade amount limits introduced in the previous release and fixes a bug affecting BSQ swap trades.

Release notes

Trading

• Maximum trade limits were increased to 0.250 BTC.
• The risk-based reduction factors for the 4 risk classes were changed from 1, 2, 4, 8 to 1, 2, 3, 4. This results in trade limits of up to 0.250 BTC for Altcoins and up to 0.0625 BTC for higher-risk fiat payment methods such as SEPA or Zelle.
• Fixed a bug in BSQ swap fee validation and added additional validation checks.
• Trade statistics validation was adjusted for the reduced trade limits introduced in the previous release.

UX And Settings

• Updated the user agreement.
• Trade rules are now shown when users create or take an offer for the first time.
• Trade rules and the user agreement are now available from Settings → About.
• The cold-storage reminder threshold is now configurable in preferences.

Release Process

• Debian package dependency generation now relaxes t64 dependencies while preserving the original constraint or qualifier on the non-t64 alternative.

See full release notes at: https://github.com/bisq-network/bisq/tree/master/release-notes/1.10.1

Bisq v2.1.11 released.

Main focus of this release: • Major security and hardening improvements • Stronger release verification and update protection • Better Tor reliability and macOS Apple Silicon support

Please update as soon as possible! https://blossom.primal.net/131090ffb65a2d2def4033ffada67ecaac9c3bbf247729420610354ce3f64298.png

The Bisq v1 security incident post-mortem is now available. It details the exploit, investigation findings, reimbursement proposal, and the security improvements introduced in v1.10.0 following the attack.

https://bisq.network/blog/security-incident-post-mortem/

Bisq is back!

Bisq 1.10.0 is released!

This release focuses on security hardening following the recent security incident and includes major improvements to trade protocol validation, network message handling, release verification, and protection against supply chain attacks.

Please download the new app from inside your Bisq application which includes automated verifications or download and verify manually at:

https://github.com/bisq-network/bisq/releases/tag/v1.10.0

A full post-mortem covering the incident, investigation, impact assessment, and all security improvements will be published on the Bisq website in the coming days.

Reimbursement for affected traders

A proposal has been published and if it gets accepted by the DAO in the upcoming voting cycle it will lead to a timely, full refund in Bitcoin.

https://github.com/bisq-network/proposals/issues/481

Release notes:

Security Improvements

• Hardened validation of trade protocol messages, deposit transactions, payout transactions, trade contract data, and peer-provided wallet data.
• Improved protection against supply chain attacks by adding PGP signature verification to dependency resolution.
• Updated Java, JavaFX, Tor, bitcoinj, and other dependencies to their latest stable versions.
• Improved the build process with additional verification of the build toolchain.
• Added Docker-based DAO and end-to-end trade tests to GitHub Actions. This work will continue over the coming weeks.

Security Improvements Affecting the Trading Experience

• The maximum trade amount is now limited to 0.125 BTC.
• Offers and trades are now restricted to a maximum price deviation of 25%.
• Disabled XMR auto-confirmation. No issues have been identified, but a more in-depth security audit is planned for this area.
• Removed the webcam library used for QR code scanning to reduce security risks. A more secure replacement will be introduced in the next release.
• Removed dispute chat attachments and dispute log file transfers for security reasons.
• Added a popup reminder advising users not to use the Bisq wallet as a long-term storage wallet when holding higher balances.

UX

• Improved performance by updating JavaFX and Java versions.

Deployment

• macOS releases now support both Apple Silicon and Intel-based Macs.
• The reproducible build system is now partially in place, though not yet applied to this release. The next release will fully benefit from it.

Thank you to everyone who helped review, test, investigate, and support the project.

Bisq Exploit Update 2

Data points

We have now received all reports from affected users. The total amount of funds lost is 11.59104 BTC. A total of 10 users were affected. Only altcoin trades were impacted. Fiat trades are protected by the account age witness signing system, which likely acted as a deterrent to the attacker. Three trades accounted for almost 90% of the total loss, while three traders suffered only very small losses.

What is the current status of reimbursement?

No final proposal has been completed yet. Our goal remains to submit a proposal for DAO voting, and the current proposal period ends in about one week. The intent remains the same as initially communicated: we plan to fully reimburse all victims and provide the option to receive reimbursement in Bitcoin or BSQ. What remains unresolved is how to fund the reimbursement in a way that minimizes the impact on the DAO, BSQ stakeholders, and Bisq contributors.

When will a new version be released?

Our initial plan was to deploy a hotfix based on the latest release, with only minimal changes to address the vulnerability used in the exploit. However, this approach proved too risky. We must assume that the same attacker — and potentially others — will actively probe for additional vulnerabilities across all parts of the application.

This includes the wallet, the P2P network, the DAO, and infrastructure components such as external market price providers.

Given the breadth of this attack surface, a full review could not be completed in a short timeframe. We therefore focused on hardening the trade protocol and addressing other short-term risks that could realistically be mitigated.

In addition, we decided to merge the hotfix branch into the main branch, which already contained the work for the upcoming 1.9.23 release and was close to completion. This introduced a substantial number of additional changes and naturally requires more extensive testing — which is why this option was not initially considered. However, as the hotfix itself grew significantly in scope, the original argument no longer applied and merging became the more reasonable path. As a result, our release schedule has been delayed. We are now in the final stages and hope to begin testing and release within the next few days. We understand that this delay is frustrating for users. However, security requires discipline, and we cannot take shortcuts that could create the risk of a follow-up incident.

What did we find during the security analysis?

The main findings that could affect user funds are limited to the trade protocol. No new exploit path has been identified. That said, we discovered and addressed a number of potential issues. Based on our current understanding, none of them could have been used to directly steal funds. Some, however, could have caused transactions to become invalid, potentially leading to secondary damage and operational risk.

Wallet security

No wallet-related vulnerability has been identified. We are currently evaluating additional measures to further reduce wallet-related risk, but these would require significantly more time to implement.

While no wallet vulnerability has been found, we cannot completely exclude the possibility that undiscovered issues may exist. Because a hot wallet integrated into a P2P application inherently carries more risk than a traditional wallet, we strongly recommend that users do not keep more funds in the Bisq wallet than are necessary for active trading. This should already be standard security practice: keep savings in a hardware wallet, not in the Bisq wallet.

Other areas

Our analysis of the DAO, P2P network, and node infrastructure did not uncover any critical vulnerabilities. However, we did address several existing issues and will continue working to reduce attack surface and strengthen protective safeguards.

Some learnings

One important lesson from this work is that structural friction and layer boundaries can act as valuable security safeguards.

In Bisq 1, the maker fee transaction allocates the UTXO required by the maker for the trade. This transaction is created only through direct user action, not by network messages, and it exists outside the trade protocol itself. That separation created an important boundary and limited the maximum possible damage the exploit could cause. In the Bisq 2 MuSig protocol, we removed that extra transaction as an optimization. At the time, we viewed that as clear progress. With the learnings from this incident, we need to reconsider that assumption — or at minimum recognize that the protective boundary created by that separate layer no longer exists in the new protocol. Security often works against intuition. Friction can be beneficial. Layer boundaries create risk boundaries.

Bisq Protocol Exploit Update

This is a brief update on what we have learned so far, the current state of reimbursement planning for affected users, and some broader observations about the growing role of AI-assisted attacks.

Estimated impact

Based on preliminary estimates from data analysis and reports from affected users, the total amount stolen appears to be approximately 11 BTC.

The attacker used a 0.001 BTC multisig output together with an unusually high 10,000 sat miner fee in the reported transactions. That combination created a recognizable transaction fingerprint, which helped identify suspicious transactions within the time window in which the attack occurred.

So far only Altcoin trades have been reported.

This remains a preliminary estimate. The final amount may change as additional reports are reviewed.

How are victims getting reimbursed?

We are currently discussing several reimbursement options. Our goal is to enable fast and complete reimbursement with minimal friction for victims.

There are, however, practical constraints:

• Protocol constraints: victims must open arbitration cases. Arbitration can only be opened after a time lock of 10 days for altcoin trades and 20 days for fiat trades. • DAO constraints: the DAO has limits on how much can be issued per DAO cycle. • DAO governance: the proposal for the reimbursement has to be confirmed by the DAO via voting. The current DAO cycle will end around 25th of May.

The current intention is to allow victims to choose between reimbursement in Bitcoin or BSQ.

At this stage we cannot make a final commitment on the exact mechanism, but we wanted to share our intentions.

For Bisq users — whether affected directly or not — discussion is ongoing in the Matrix channel: (https://matrix.to/#/%23bisq:bitcoin.kyoto)

And on GitHub: (https://github.com/bisq-network/bisq/discussions/7628)

The final reimbursement model will be submitted as a DAO proposal for voting.

The exploit caused a significant challenge for both Bisq and the DAO, but we are confident it is manageable. It was serious, but it was not a fatal blow.

How did the exploit happen?

In short, the exploit was caused by a missing validation that should have rejected negative input values provided by the taker.

The maker and taker must use the same miner fee. That fee value is provided by the taker.

The attacker supplied a negative miner fee.

When the maker calculated the multisig output amount — which includes the miner fee for the payout transaction — the negative value reduced the multisig amount to 0.001 BTC, while the remaining funds were redirected to the taker’s change output.

Unfortunately, the taker change output was a leftover from older protocol versions. It had already been identified as something that should be removed, but that cleanup had unfortunately not happened.

Was it an AI-assisted attack?

We cannot answer that with certainty. However, based on our own experience during the investigation, we think it is likely.

After the issue was discovered, one group of developers started manual code inspection to understand how the exploit could have happened.

A second group used AI-assisted analysis.

The AI-assisted group was faster and identified the exploit path in a relatively short time.

The first AI-generated attempt turned out to be a false positive, but a second attempt by another developer successfully reproduced the exploit. It also produced both an attack patch and a corresponding fix.

AI tools include safeguards, so simply asking them to identify an exploit will usually not work.

However, with enough context, careful prompting, and a degree of social engineering of the model, those safeguards can be bypassed.

Based on our experience, it is reasonable to assume that the attacker may have followed a similar path.

A warning shot

Some Bisq developers are highly proficient with AI tools. However, we had not systematically used them as part of an actual security audit process.

One developer attempted to get Bisq into an external security audit program, but the application was rejected.

In hindsight, this was a serious failure on our side.

The mistake was not only the missing validation check. It was also failing to react early enough to the changing security landscape and the increasing practical relevance of AI-assisted vulnerability discovery.

We must assume that there will be further attempts.

Over the coming weeks we will invest significant effort into hardening the codebase and actively using AI tools ourselves to search for failure modes.

We are particularly focused on vulnerabilities that could directly affect the wallet.

Until additional review and hardening are completed, we recommend that Bisq users do not keep more BTC in their Bisq wallet than is necessary for active trading.

We also hope this serves as a useful warning to other projects in the space.

If our experience helps others identify similar risks earlier and strengthen their defenses, something positive may still come out of it.

Release plans

We have already fixed the immediate vulnerability and are currently working on additional hardening for a hotfix release.

We expect to publish that release in the coming days.

After that, we will continue with a follow-up release focused on further hardening, broader review, and additional security auditing.

Bisq v1 has experienced an exploit in its trade protocol that allowed an attacker to drain a portion of available offers.

The impact was limited to open offers that were actively taken by the attacker over the last 12 hours. Funds held in users’ Bisq Bitcoin wallets were not affected.

As an immediate mitigation, an emergency mechanism was activated to disable trading by setting the required trading version to 2.0.0 — a version that does not exist. This effectively prevents the attacker from continuing the exploit.

The attack appears to have started on May 1 in the early morning hours. The development team is continuing to investigate the full extent of the damage. Users with trades initiated on or after this time are advised to open mediation by selecting the trade and pressing Ctrl + O. A mediator will assess whether their trade was affected.

Preliminary investigation indicates that the attacker exploited a missing validation check using a modified client. The team is working to reliably reproduce the issue and verify a fix. Once confirmed, a hotfix will be released based on the latest stable version. In parallel, a comprehensive security review is being conducted to identify any related or additional vulnerabilities.

For affected users, reimbursement options are being evaluated. Bisq recognizes that both the exploit and a consequent response are critical to its integrity, and is dedicating all available resources to finding a solution that helps restore confidence.

Bisq 2, with the Bisq Easy trade protocol, is not affected. It is a separate codebase with a fundamentally different protocol design.

Bisq will continue to provide updates through its official communication channels, including Matrix, the Bisq Forum, Telegram, Reddit, X, and Nostr.

Bisq sincerely apologizes for the impact this incident has had on its users, and is fully committed to addressing both the root cause and its consequences.

Bisq has reached a major milestone.

With the release of Bisq Connect v0.3.2, the Bisq Easy mobile initiative is now complete.

Running a full P2P app over Tor on mobile is challenging. Android supports Java, iOS does not, so we built two approaches:

• Bisq Easy Mobile (Android): full node with complete P2P stack.

Same privacy and security as desktop, no extra infrastructure. Trade-offs: Android only, higher resource usage, background connectivity issues, no desktop sync, backups required.

https://play.google.com/store/apps/details?id=network.bisq.mobile.node

• Bisq Connect (Android + iOS): lightweight client connecting to a Bisq 2 backend (desktop, headless node, or VPS).

– Self-hosted: maximum privacy and control – Trusted node: easier setup (e.g. friend/family), but requires trust

Benefits of Bisq Connect: • Cross-platform • Low resource usage • Seamless desktop + mobile access (self-hosted) • No mobile backups needed

iOS note: distributed via TestFlight due to App Store restrictions.

https://play.google.com/store/apps/details?id=network.bisq.mobile.client

https://testflight.apple.com/join/abBmehCw

What About Bisq 1 and the MuSig Trade Protocol? For Bisq 1, the Bisq Notifications app remains available to receive trade-related notifications from your desktop node.

Bisq 2 MuSig is in development as successor to Bisq 1. On mobile, it faces challenges: full node → technical limits connect mode → significant UI effort Future support depends on adoption.

We’ll continue improving stability and the mobile experience. Feedback and adoption will shape what comes next.

Learn more:

https://bisq.network/blog/mobile-apps-completed/

https://bisq.wiki/Bisq_2_mobile

https://bisq-network.github.io/bisq-mobile

🚀 Bisq 2 v2.1.10 is released!

https://github.com/bisq-network/bisq2/releases/tag/v2.1.10

🔄 Trade Rule Update The “reason for payment” field should now be left blank whenever possible. If required, use your name (no more Trade ID).

✨ New Features • Trade history is now available • QR-based pairing for Bisq Connect • TLS support for clearnet connections when using Bisq Connect

⚙️ Improvements • Switched to price nodes instead of mempool → More reliable reference time

🐛 Bug Fix • Fixed incorrect display of last user activity in contact profiles

🛠️ Behind the Scenes Most dev work is focused on the MuSig trade protocol, which is progressing well.

Stay tuned!

Bisq v2.1.9 is released!

This update focuses on improved internationalization, better data resilience, and several usability and stability improvements. Users are recommended to upgrade to benefit from the latest fixes and enhancements.

✨ New features

• Support for 50+ languages, including new script and regional variants (e.g. Simplified & Traditional Chinese, Brazilian and European Portuguese).
• Automatic restore from the latest backup if local data becomes corrupted.
• Backup files are now visible in the Resources UI.
• Added pairing support for Bisq Connect (requires Bisq Connect v0.2; not yet released).
• Added a reference time check to detect when the system clock is out of sync.

🔧 Improvements

• Added a loading banner while initial data is being prepared.
• Improved handling of BSQ bond unlocking.
• Set proper file permissions for the user data directory.
• Support alerts and update messages for desktop, mobile node (Bisq Easy), and mobile client (Bisq Connect).
• Updated API configuration.

🐛 Bug fixes

• Fixed an issue related to Bulgaria’s transition to EUR.
• Fixed a bug in log masking.

✅ Update via your existing Bisq app or download from GitHub: 👉 https://github.com/bisq-network/bisq2/releases

#Bitcoin #Bisq #P2P #DEX

The chainwork bug in Bisq 1 has been fixed, and a new release is now available: https://github.com/bisq-network/bisq/releases/tag/v1.9.22 You can also update directly from within the Bisq app.

If you experience any wallet issues, a SPV resync should resolve them, though no problems are expected. Thank you for your patience and continued support. Happy Xmas!

Bisq is experiencing issues related to a cumulative proof-of-work bug in BitcoinJ.

An upstream fix exists but hasn’t yet been ported to our branch. We expected this issue to surface around March 2026, which turned out to be a miscalculation.

We’re actively working on the fix and aim to release a new version soon. If you have open trades, please be patient—mediators and arbitrators will take this situation into account.

Bisq Easy Mobile v0.2.1 is now available on the Play Store and as an APK download.

This release fixes the out-of-memory issue that affected previous versions.

📱 Play Store: https://play.google.com/store/apps/details?id=network.bisq.mobile.node 📦 APK: https://github.com/bisq-network/bisq-mobile/releases/anode_0.2.1

Bisq Easy on Mobile

Bisq Easy on Mobile It’s never been easier to get Bitcoin — peer-to-peer and privacy-preserving over Tor.

We’re happy to announce that Bisq Easy is now available for Android — both as an APK and on the Google Play Store.

https://github.com/bisq-network/bisq-mobile/releases/anode_0.1.1

https://play.google.com/store/apps/details?id=network.bisq.mobile.node

Full node in your pocket. Your phone runs a P2P node over the Tor network — just like Bisq on desktop. Tor is fully integrated, no extra setup required.

When the app goes into the background, network connectivity usually remains active for a while (depending on usage and system resources). If it disconnects, the app automatically reconnects within seconds when reopened.

Why no iOS (yet)? Bisq is built in Java, which integrates easily with Android but not with iOS. A full rewrite for iOS would be a prohibitive effort.

But stay tuned — we’re working on Bisq Connect, a companion app that acts as a “remote control” for your desktop or VPS-hosted Bisq node, also running over Tor. It will be available for both Android and iOS.

Excited? Give it a try! We’d love your feedback — and if you find it useful, help spread the word.

https://bisq.network/blog/mobile-app-survey-results/ https://blossom.primal.net/1471b9aa077a49228f203a0286c7e5d95d8dc169105aff4a15da09422425f5f8.png

Dive into the evolution of Bisq’s Multisig protocol and see how Bisq 2 is laying the foundation for a modular, multi-protocol trading platform.

https://bisq.network/blog/trade-protocols

Bisq Easy Mobile App — User Survey

We are developing Bisq Easy mobile applications and would like to better understand your needs.

Your feedback will help us optimize resource allocation and deployment strategy.

Bisq Easy mobile apps will come in two modes:

• Full Node Mode (Android only): Runs a full Bisq node directly on the device, connects over Tor, follows the same P2P network model as the desktop app, requires higher CPU, memory, and battery resources.

• Light Client Mode (Android and iOS): A lightweight app that acts as a remote control for a hosted Bisq node, with minimal resource usage and no P2P networking on the mobile device itself.

Why no mobile support for Bisq 1 MultiSig protocol?

Resource demands and the need for makers to stay online make it impractical for mobile use.
Bisq 1 will be replaced by Bisq 2 MuSig, offering better privacy and efficiency.
However, even with MuSig, Full Node operation on mobile remains infeasible; only Light Client mode is realistic.

Why Full Node mode is Android-only?

Bisq is written in Java, which runs natively on Android but not on iOS.
Rewriting the full node for iOS in Swift would require substantial effort.
Additionally, Apple's restrictive App Store policies and Tor challenges on iOS make such an investment high risk.

Why two modes?

This two-mode approach ensures that both advanced and casual users are supported, giving users flexibility to prioritize privacy, decentralization, or usability.
It also provides a feasible model to support a mobile experience on iOS.

We want your input

Please take our quick survey to help guide development priorities:

https://bisq.network/blog/mobile-app-survey

Thank you for your support!

For additional feedback or suggestions, please visit:

https://bisq.chat

Bisq's first-ever hackathon has kicked off!

Want to help shape Bisq’s future? Join us in Matrix at: https://matrix.to/#/#bisq:bitcoin.kyoto (room: #bisq-hackathon:http://matrix.org)

Details & topics:

https://bisq.network/blog/bisq-hackathon

Pick a topic or bring your own idea—Bisq contributors are here to help. Happy hacking!

Bisq is hosting its first-ever Hackathon, April 10–13!

A unique chance for passionate devs who care about privacy and decentralization to build, connect, and shape Bisq’s future.

https://bisq.network/blog/bisq-hackathon/

Why join? 🚀 Work on high-impact, real-world challenges 🧠 Collaborate directly with core Bisq developers 🧩 Help shape the next evolution of Bisq 💰 Earn compensation for meaningful contributions

Challenges & Ideas: 🎯 Fee Payment in the MuSig Trade Protocol ⚡ Lightning trade protocol 🕵️‍♂️ I2P integration 🤖 AI Integration in Bisq 🔐 Decentralized Reputation System 📈 Scaling the DAO and BSQ

Ready to hack on the future of p2p exchange? 👉 Join us: https://matrix.to/#/#bisq:bitcoin.kyoto

🔥 Bisq v2.1.7 is released!

This update brings critical improvements for more reliable message delivery and bugfixes in the trade process. Please upgrade ASAP to benefit from enhanced resilience and stability.

✨ New features

• A splitpane to calibrate sizes between offerbook chat and offer list has been added. https://m.primal.net/PzFE.png

• Official Bisq mediators and moderators can now be identified by the badge next to their nickname. https://m.primal.net/PzFF.png

🔧 Improvements

• The Bisq Easy protocol has been enhanced to protect against triangular scams. Now, when the buyer does the Fiat transfer, trade ID must be set as "Reason for payment".
• Splash screen now shows the loading progress for each required step: Starting Tor, publishing onion service, connection to P2P network and, finally, data inventory request.

📬 Message delivery improvements

• Send message as mailbox message in case no connection to the peer is yet established, which speeds up message delivery and provides better resilience.
• Send mailbox message in case the node associated with the user profile has not yet published it's onion service. This case could happen specially with multiple user profiles and if Tor is slow/unstable.

🔄 Trade process improvements

• Allow multiple takers to take the same offer of a maker who is offline. Before only the first take offer message was successfully processed and the remaining led to a failure when the maker went online.
• Add new version for trade ID creation, including the take offer date. This allows that an offer can be taken by the same taker multiple times. This will get activated with June 1st.

⚖️ Mediation improvements

• Add support for message delivery status with multiple peers in case of mediation.
• Add new version for mediator selection which includes the offer ID. Now the same pair of traders would always get the same mediator selected. This will get activated with June 1st.
• Add mediation case details popup (for mediators)
• Add "remove mediation case" button (for mediators)

🐛 Bug Fixes

• Fixed bug with trade messages arriving out or order, which led to failed or stuck trades.
• Fixed several issues related to mediation and the mediation request process.
• Fixed bug preventing from taking new offers.

✅ Download from inside your current Bisq 2 app or from Github: 👉 https://github.com/bisq-network/bisq2/releases/tag/v2.1.7

#Bitcoin #Bisq #P2P #DEX

Bisq is looking for Senior Java Developers!

Help build censorship-resistant financial infrastructure. Bisq is looking for self-driven Java experts passionate about Bitcoin, privacy, and decentralization.

Bisq v2.1.6 release notes

⚠️ Security update

• To enhance security for buyers, sellers must have sufficient reputation to secure a trade for the specified amount. The required reputation score is determined using the following formula:

Reputation score = max. selling amount * 200

For a minimum trade amount of 6 USD, the required reputation score would be 1200, which can be achieved through any of the following methods:

• Burn 12 BSQ (approximately 25 USD). • Lock 120 BSQ as a bond for approximately one year. • Have a Bisq v1 signed account for at least 120 days. • Have a Bisq v1 account age of at least 280 days.

BSQ can be purchased with Bisq 1.

For more details, visit the Bisq reputation system Wiki:

https://bisq.wiki/Reputation

• Since this release is a critical security update, the new version will be enforced shortly after its release to ensure the protection of all buyers.

✨ New features

• The new Profile Card comes with many features. Find the user profile details, trade terms, reputation, offers created and the public messages posted by clicking on the profile icon or profile name anywhere in the app.

• To improve on privacy, sensitive trade data will be automatically deleted after a certain period of time. This can be adjusted in Settings > Offer and trade.

• See trade details in the trade process window by clicking on the "Show details" button.

🔧 Improvements

• The create offer wizard has been consolidated into three steps to improve quickness and ease of use. You can choose the amount and price in the same screen and see the BTC conversion display.

🐛 Bug Fixes

• Fixed reputation display at start up.

• Resolved issues during the trade process with peer messages not being processed correctly, and other bugs.

See all changes in this release:

https://github.com/bisq-network/bisq2/milestone/9?closed=1

Bisq v2.1.2 has been released, offering an improved reputation system, easier to follow chat rooms and more flexible offer book filtering.

Trades up to 25 USD no longer require sellers to have reputation, with higher amounts becoming available as sellers establish and increase their reputation scores.

This change makes it easier for new sellers to get started and should increase small trade liquidity.

The multiple, topic-specific chat rooms found in previous versions have now been consolidated into Chat and Support sections, with both public discussions and private chats being brought together under a single screen.

Offer listings can now be sorted and filtered more granularly by parameters including price, payment method and on-chain (BTC) vs. off-chain (LN⚡️) settlement. Try shift-clicking on column headings to set secondary sort conditions.

Many additional fixes and improvements are included. See the full set of changes and download Bisq v2.1.2 here:

https://github.com/bisq-network/bisq2/releases/tag/v2.1.2

Hello Nostr!

This npub will now be a primary outlet for Bisq news and announcements.

New posts will be published here and then cross-posted to the bisq_network X handle.

Decommissioning X will be considered when this npub has more followers.