Bisq's avatar
Bisq
_@bisq.network
npub1sqn6...5net
A peer-to-peer bitcoin exchange system
Bisq's avatar
bisq 1 month ago
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:
GitHub
Release v2.1.12 · bisq-network/bisq2
Release notes v2.1.12 This is an important security update that fixes vulnerabilities identified during our recent security audit. Updating to this...
Bisq's avatar
bisq 1 month ago
**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's avatar
bisq 2 months ago
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. image
Bisq's avatar
bisq 2 months ago
## 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.
Bisq's avatar
bisq 2 months ago
**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.
Bisq's avatar
bisq 2 months ago
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.
Bisq's avatar
bisq 2 months ago
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.
Bisq's avatar
bisq 3 months ago
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:
GitHub
Release v1.10.2 · bisq-network/bisq
Release notes DAO Consensus Security DAO merit validation is hardened at and after block 954_200. V2 merit validation checks embedded merit issuan...
 image
Bisq's avatar
bisq 3 months ago
# Bisq v1.10.1 has been released
GitHub
Release v1.10.1 · bisq-network/bisq
This release addresses concerns about the overly restrictive trade amount limits introduced in the previous release and fixes a bug affecting BSQ s...
 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:
GitHub
bisq/release-notes/1.10.1 at master · bisq-network/bisq
A decentralized bitcoin exchange network. Contribute to bisq-network/bisq development by creating an account on GitHub.
Bisq's avatar
bisq 4 months ago
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! image
Bisq's avatar
bisq 4 months ago
# 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:
GitHub
Release v1.10.0 · bisq-network/bisq
Bisq 1.10.0 follows the recent security incident with a focused hardening release that improves trade protocol security, network message validation...
 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.
GitHub
Proposal for Refunds to Victims of the May 1st Bisq 1 Trade Protocol Incident · Issue #481 · bisq-network/proposals
Proposal for Refunds to Victims of the May 1st Bisq 1 Trade Protocol Incident An anonymous group (referred to here as the “Refund Angels” or ...
 ## 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.
↑