Skip to content
CUNICULA

Bisq

Open-source P2P Bitcoin trading over Tor with DAO governance; no central exchange account.

bisq.network

Open-source P2P Bitcoin trading over Tor with DAO governance; no central exchange account.

Common useMaximum decentralizationP2P / DesktopOperator dataUnknown
Identity checksNo routine KYCNo document check recorded · identity exposure level 0/4
Evidence and riskPartial evidenceDocumented riskSome material claims still need confirmation.; those sources document a material risk.
Last reviewedReviewed 8 Nov 2026KYC checked 8 Nov 2026 · unknown jurisdiction · Source → official siteHow to cite this pageSource coveragePartial evidenceRecorded riskDocumented risk
Evidence and facts

Evidence and facts

CUNICULA SCORE 4.0
39/100Limited evidencePrivacy 21/25 · Control 18/20 · Transparency 12/20 · Security 0/25 · Accountability 5/10 · Cap 39 · Method
JURISDICTIONUnknown
WARNINGBisq shares payment details with peers and, in disputes, agents; banks may identify users. Official disclosures describe exploited trade-protocol flaws in April 2020 and May 2026; the latter affected 10 users and 11.59104 BTC. The June update reports reimbursement but also notes one trader had not requested it. Current security releases as of 2026-11-08 are Bisq 1 v1.10.11 and Bisq 2 v2.1.15. Bisq 2 v2.1.3–v2.1.13 logs contain onion private keys, and API-node logs also user-profile keys: v2.1.14 redacts local logs, not previously shared copies or backups. Do not share old logs. No later XMR auto-confirmation audit completion was established. The integrated hot wallet is not suitable for long-term savings.
INCIDENTSecurity Incident Post-Mortem
monitoring · high · recorded 2026-05-01
May 1, 2026 Bisq 1 trade-protocol validation exploit affected 10 altcoin traders and 11.59104 BTC. Emergency halt and release 1.10.0 hardening contained the exploit; June follow-up reports reimbursement while noting one trader had not requested it and XMR auto-confirmation audit remained pending. Bisq security incident postmortem, Bisq June incident and reimbursement update
AUDITED BYNo audit listed
OPERATOR DATAUnknown
SOURCE COVERAGE
Partial evidenceTHIRD-PARTY REPORTED2/11Reviewed 8 Nov 2026 · Source → official site
LAST CHECKED2026-08-27
LAST UPDATED2026-09-05

Specs

DOCUMENT CHECKNone recorded
IDENTITY EXPOSURELevel 0/4
KYC TRIGGERSNo central registration, email or routine document-KYC in the core protocol. Fiat payment details must match real account data and are shared with the peer; banks apply their own requirements and dispute agents can request payment/bank evidence.
FEEBisq 1: BTC maker 0.15%, taker 1.15%; BSQ target maker 0.1125%, taker 0.8625% (rates vary by DAO cycle). Minimums 0.000075 BTC or 0.03 BSQ; mining/payment-rail fees and deposits separate. Bisq Easy: no trade fee or deposit; seller transfer fees and offer spread can apply.
LIMITVaries by payment method, account signing and protocol/version; current wiki and security-release numeric caps conflict. Check the current client before trading.
CATEGORIESP2P / Desktop
COMMON USESMaximum decentralization, BTC/fiat P2P, Privacy-maximalist
FEATURESTor, Non-custodial, Bank/Cash/SEPA
TORYes
REGIONSGlobal availability
Review analysis, source material, related services, and history

About

Decentralized open-source desktop P2P Bitcoin exchange over Tor, with no registration stated as required.

Analysis

OVERVIEW

Bisq is open-source P2P Bitcoin exchange software over Tor, with no central registration in the core protocol. Multisig escrow and security deposits differ by software generation and trade model; payment peers and dispute processes still handle records.

LIMITS

Fiat peers and banks can see payment identity, and disputes can require bank/payment evidence. Official disclosures describe exploited trading-protocol flaws and legacy Bisq 2 logs containing private keys. Use current releases and follow the published log/key precautions; decentralized governance is not an incident-free guarantee.

USEFUL FOR

P2P Bitcoin trading for users assessing the selected trade protocol, counterparty payment exposure and current software/security requirements.

Ownership and funding

Ownership and funding chain

Corporate identity

Other cited research. Not audited. Each claim links its own source.

Corporate identity research · reviewed 2026-08-08

We wrote about this

Frequently Asked Questions

Is identity verification required?

No identity verification is recorded for typical use. No central registration, email or routine document-KYC in the core protocol. Fiat payment details must match real account data and are shared with the peer; banks apply their own requirements and dispute agents can request payment/bank evidence.

Where is it available?

Recorded availability: GLOBAL.

Is the operator based in a Five Eyes country?

The jurisdiction is not publicly confirmed. Check the provider site for incorporation details.

How are identity, operator, and evidence fields reported?

Identity exposure is level 0 of 4. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is partial evidence, last reviewed 2026-11-08, and recorded risk is danger.

Sources and history

Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.