Evidence and risk△Partial evidence/△CautionSome material claims still need confirmation.; those sources show trade-offs worth reading.
Last reviewedReviewed 5 Sep 2026KYC checked 5 Sep 2026 · unknown jurisdiction · Source → official documentationHow to cite this pageSource coveragePartial evidenceRecorded riskCaution
Evidence and facts
Evidence and facts
CUNICULA SCORE 4.0
49/100△Limited evidencePrivacy 17/25 · Control 12/20 · Transparency 12/20 · Security 13/25 · Accountability 2/10 · Cap 49 · Method
JURISDICTIONUnknown
INCIDENTPython CI workflow allowed pull-request code execution resolved · high · since 2026-08-20 GHSA-rxx8-rv5g-wpch describes a high-severity pull_request_target workflow flaw through 0.8.5-alpha. RoboSats identifies 0.8.6-alpha as patched and that release was already current when the advisory was published.RoboSats GHSA-rxx8-rv5g-wpch, Current latest RoboSats release
INCIDENTJavaScript CI workflow allowed pull-request code execution resolved · high · since 2026-08-20 GHSA-xjwx-6j4q-hrr6 describes high-severity arbitrary runner-code execution through 0.8.5. RoboSats identifies 0.8.6 as patched and that release was already current when the advisory was published.RoboSats GHSA-xjwx-6j4q-hrr6, Current latest RoboSats release
INCIDENTCoordinator notice raw HTML permits JavaScript execution monitoring · medium · since 2026-08-20 RoboSats published GHSA-p353-f8m7-8v95: coordinator notice HTML can execute JavaScript and expose robot root credentials across coordinators. Versions through 0.8.6-alpha are affected; 0.8.7-alpha is the patched line, while the current latest release is 0.8.6-alpha.RoboSats GHSA-p353-f8m7-8v95, Current latest RoboSats release
INCIDENTPrivate orders exposed through unauthenticated API filters monitoring · medium · since 2026-08-20 RoboSats published GHSA-r6f6-x59j-8q69: password-protected orders can be returned without authentication, including payment method, amount, maker nickname and face-to-face coordinates. Versions through 0.8.6-alpha are affected; 0.8.7-alpha is the patched line, while the current latest release is 0.8.6-alpha.RoboSats GHSA-r6f6-x59j-8q69, Current latest RoboSats release
INCIDENTConcurrent reward withdrawals could drain coordinator funds resolved · medium · since 2026-08-20 GHSA-vp6p-w2r2-jj2v describes a reward-withdrawal race condition affecting versions through 0.8.5-alpha. RoboSats identifies 0.8.6-alpha as patched and that release was already current when the advisory was published.RoboSats GHSA-vp6p-w2r2-jj2v, Current latest RoboSats release
KYC TRIGGERSNo account/KYC model found in official repository; robot identities are generated per use and Lightning hold invoices handle bonds/escrow.
FEE0.2% total: 0.025% maker and 0.175% taker; Lightning routing and on-chain payout fees can be additional
LIMITCoordinator-specific
CATEGORIESP2P / Lightning
COMMON USESBTC/fiat P2P trading, High privacy users, Tor-only workflows
FEATURESTor, LN escrow, Quick trades
TORYes
REGIONSGlobal availability
Review analysis, source material, related services, and history
About
Open-source P2P Bitcoin exchange using Lightning hold invoices, robot avatars and Tor-first access.
Analysis
OVERVIEW
Per-session robot identities, Lightning hold invoices for bonds and escrow, and Tor-first access: the venue is built so that nothing persistent identifies a trader across trades.
LIMITS
The record notes clearnet endpoints were unreachable during review and coordinator availability varies; amounts are Lightning-scaled, and the fiat leg remains a counterparty exposure.
USEFUL FOR
Quick Bitcoin-fiat swaps over Tor at Lightning-sized amounts.
No identity verification is recorded for typical use. No account/KYC model found in official repository; robot identities are generated per use and Lightning hold invoices handle bonds/escrow.
Which payment methods are accepted?
Please check the provider site for accepted payment methods.
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-09-05, and recorded risk is caution.
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.
Service history
Latest meaningful changes to the facts shown on this provider page.
Review overdue providers against current sources
Fee, KYC last checked, Last reviewed, Limit, and 3 more
Reconcile score 4.0 evidence
Audited by, Evidence status, Score assessment / Control model, Score assessment / Operator data exposure, and 1 more
Apply full-service rereview and score 4.0
Privacy warning, Recorded risk, Score assessment
Full service history
updated
Review overdue providers against current sources
Fee
0.2% → 0.2% total: 0.025% maker and 0.175% taker; Lightning routing and on-chain payout fees can be additional
KYC last checked
2026-06-22 → 2026-09-05
Last reviewed
2026-06-22 → 2026-09-05
Limit
not set → Coordinator-specific
Privacy warning
Tor-only access reduces network exposure but does not remove coordinator trust. In versions through 0.8.6, a coordinator can run JavaScript through raw-HTML notices and password-protected public orders can be read without authentication, including payment method, amount, maker nick and F2F latitude/longitude. Wait for or verify upgrade to 0.8.7+. → RoboSats is no-KYC and normally used over Tor, but users still trust the selected coordinator for availability, dispute handling and its configured trade limit. Versions through 0.8.6 had a raw HTML execution issue and a private-order data leak. Both are patched in v0.8.7-alpha, released September 4, 2026. Update before trading and verify the coordinator and client version.
Source reviewed
official site → https://github.com/RoboSats/robosats/releases/tag/v0.8.7-alpha
not set → Outcome: HOLD; Checked at: 2026-08-27; Inputs: Operator data exposure: moderate; Control model: federated; Source model: open; Audit: Score eligible: no; Reason: No dated, scoped independent audit of the score-critical core was evidenced; no audit points are granted.
Clearnet service URLs were unreachable from the VPS during review; official GitHub and indexed sources remain live. Use Tor/onion where available and verify current coordinator availability. → Tor-only access reduces network exposure but does not remove coordinator trust. In versions through 0.8.6, a coordinator can run JavaScript through raw-HTML notices and password-protected public orders can be read without authentication, including payment method, amount, maker nick and F2F latitude/longitude. Wait for or verify upgrade to 0.8.7+.
Recorded risk
standard → caution
Score assessment
not set → Operator data exposure: limited; Control model: decentralized; Source model: open
Open-source P2P Bitcoin exchange using Lightning hold invoices, deterministic robot avatars and Tor-first access to minimize custody and identity exposure. → Open-source P2P Bitcoin exchange using Lightning hold invoices, robot avatars and Tor-first access.
RoboSats — Tor-native, Lightning-based P2P Bitcoin exchange. Fully anonymous robot identities, no accounts, native onion service. → Open-source P2P Bitcoin exchange using Lightning hold invoices, deterministic robot avatars and Tor-first access to minimize custody and identity exposure.
Domain
robosats.com → robosats.org
Jurisdiction
not set → ??
KYC requirement
light → none
KYC last checked
2025-08-30 → 2026-06-22
Kyc note
Tor-only. Generates new robot identity per trade. No persistent account. → No account/KYC model found in official repository; robot identities are generated per use and Lightning hold invoices handle bonds/escrow.
Last reviewed
2025-08-30 → 2026-06-22
Privacy warning
not set → Clearnet service URLs were unreachable from the VPS during review; official GitHub and indexed sources remain live. Use Tor/onion where available and verify current coordinator availability.
Source reviewed
older source, not independently verified → official site