eigenwallet vs PLATOV
eigenwallet has the higher grade on both axes: Safety 7.0 against 4.0, and Privacy 8.9 against 2.7.
eigenwallet
Desktop wallet for peer-to-peer BTC-to-XMR atomic swaps, formerly UnstoppableSwap
Privacy
8.9/ 10
Excellent
Safety
7.0/ 10
Strong
ID never required KYC 0 Docs reviewed Full review →
PLATOV
Broker-model crypto and fiat exchanger routing orders to partner exchanges since 2017
Privacy
2.7/ 10
Poor
Safety
4.0/ 10
Caution
ID on risk flag KYC 3 Docs reviewed Full review →
Side by side
| eigenwallet | PLATOV | |
|---|---|---|
| Category | Instant Swaps | Instant Swaps |
| KYC policy | ID never required | ID on risk flag |
| Custody | Non Custodial | Custodial |
| Sign-up | No account needed | No account needed |
| Open source | Yes | No |
| Tor onion address | No | No |
| Coins | BTC, XMR | BTC, ETH, USDT, XMR, LTC, XRP, SOL, TRX, ZEC, DASH |
| Pay with | Crypto, Monero | Crypto, Monero, Card, Bank transfer |
| Fees | Not published | About 0.5% service fee plus about 2% spread per the fee FAQ |
| Limits | Not published | Crypto-to-crypto $20 to $50,000; KYC may be requested above 1,000 USDT |
| Founded | Not published | 2017 |
| Jurisdiction | Decentralised / none | Not published |
| Not available in | Not published | AML/KYC policy section 9: United States, Canada, Singapore, Malaysia, Nigeria, Saudi Arabia, Iran, North Korea and others |
| Incidents on record | 0 | 0 |
| Published tests (180 days) | 0 | 0 |
Only eigenwallet
No email neededNo phone neededOpen sourceNon-custodial
Both
No registrationAccepts Monero
Only PLATOV
Third-party liquidityAML screeningMay request IDExcludes US usersClosed sourceAnonymous operator5+ years operating
Where they sit among instant swaps
Questions
Is eigenwallet or PLATOV safer?
eigenwallet has the higher Safety grade: eigenwallet 7.0, PLATOV 4.0, out of 10.
Does eigenwallet or PLATOV require KYC?
eigenwallet is KYC level 0 (ID never required). PLATOV is KYC level 3 (ID on risk flag).
Which has more incidents on record?
eigenwallet has 0 and PLATOV has 0 documented incidents in the registry.