7.1 KiB
layout | classes | title | permalink | toc | toc_stickly | sidebar | good | soso | bad | phone | laptop | cli | laptop_phone | remote | thumbsup | thumbsdown | unclear | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
single | wide | Wallets | /docs/wallets/ | true | true |
|
<i style='color:#4caf50' class='fa-solid fa-square-check fa-2xl'></i> | <i style='color:#ff9800' class='fa fa-triangle-exclamation fa-2xl'></i> | <i style='color:#ef5350' class='fa-solid fa-xmark fa-3x'></i> | <i class='fa-solid fa-mobile-screen fa-xl'></i> | <i class='fa-solid fa-laptop fa-xl'></i> | <i class='fa-solid fa-terminal fa-xl'></i> | <i class='fa-solid fa-laptop-mobile fa-xl'></i> | <i class='fa-solid fa-house fa-xl'></i> | <i style='color:#4caf50' class='fa-solid fa-thumbs-up fa-2xl'></i> | <i style='color:#ef5350' class='fa-solid fa-thumbs-down fa-2xl'></i> | <i style='color:#ff9800' class='fa-solid fa-question fa-2xl'></i> |
Wallet Compatibility Table
Wallet | Version | Device | UX1 | Bonds2 | Payout3 | Compatible4 | Recommended5 |
---|---|---|---|---|---|---|---|
Blixt | v0.4.1 | {{page.phone}} | {{page.soso}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.thumbsup}} |
Electrum | 4.1.4 | {{page.laptop}} | {{page.good}} | {{page.soso}} | {{page.soso}} | {{page.soso}} | {{page.unclear}} |
LND | v0.14.2 | {{page.cli}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.thumbsup}} |
Zeus | v0.6.0-rc3 | {{page.phone}}{{page.remote}} | {{page.soso}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.thumbsup}} |
SBW | 2.4.27 | {{page.phone}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.thumbsup}} |
Muun | 47.3 | {{page.phone}} | {{page.good}} | {{page.good}} | {{page.bad}} | {{page.bad}} | {{page.thumbsdown}} |
lntxbot | NA | {{page.laptop}}{{page.phone}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.thumbsup}} (info) |
BlueWallet | 1.4.4 | {{page.phone}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.unclear}} (buggy) |
WalletOfSatoshi | 1.15.0 | {{page.phone}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.thumbsup}} |
Phoenix | 35-1.4.20 | {{page.phone}} | {{page.good}} | {{page.bad}} | {{page.good}} | {{page.bad}} | {{page.thumbsdown}} |
Bitcoin Beach | v1.7.7 | {{page.phone}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.good}} | {{page.thumbsup}} (info) |
- UX: Does the wallet convey clearly that there is an "ongoing" payment (hodl invoice)?
- Bonds: Can the wallet lock the invoices with long expiry time needed for the bonds?
- Payout: Can the wallet receive payouts from RoboSats after the user buys Sats?
- Compatible: Is the wallet overally compatible end-to-end with RoboSats?
- Recommended: Is the wallet compatible and stable enough to be used consistently without issues?
Blixt (Android/iOS, LND light backend on device)
Most development testing for Robosats has been done using Blixt. This is one of the most complete lightning wallets around. I recommend it to use with RoboSats. However, it does lead to misunderstanding when hold invoices are locked. As it shows a spinner with payment in transit. The user needs to check on the website for confirmation. Blixt allows for multiple pending HTLCs, this is necessary as a seller since you need to lock a taker/maker bond and then a trade escrow (2 pending concurrent HTLCs). Might show as paid/charged invoices that are still pending, specially if the user force closes blixt and reopens it. Occasionally can display as charged fidelity bonds that have been returned.
Electrum (Desktop)
Experience using Electrum is limited. It does not seem to support more than one pending HTLCs (even if there is multiple channels). This wallet is not recommended to use with RoboSats. However, it works well if you are a buyer, as only one hold invoice for the fidelity bond is needed. The payment shows as pending with a spinner for the duration of the locktime.
LND (CLI Interface)
Raw, it shows exactly what is happening and what it knows "IN_FLIGHT". It is not user friendly and therefore not recommended to interact with Robosats by beginners. However, everything works just. If you are using LNCLI regularly, you will find no issue to use it with RoboSats.
Zeus (Mobile, LND remote backend)
It is an interface to LND. It works as expected. It is extremely misleading with a full red screen "TIME OUT" a few seconds after sending the HTLC. Yet, if the user checks on the website, the invoice is correctly locked.
Muun (Mobile)
Muun plays same nicely with hold invoices as Blixt or LND. You can be a seller in RoboSats using Muun and the user experience will be great. However, Muun is fee siphoning attacking any sender to Muun wallet. There is a mandatory hop trough a private channel with a fee of +1500ppm. RoboSats will strictly not route a buyer payout for a net loss. Given that RoboSats trading fees are 0.2% and it needs to cover the routing fees, RoboSats will never find a suitable route to a Muun wallet user.
Phoenix (Mobile)
Phoenix worked well when full trade pipeline was limited to 10 hours. Now that it is 24 hours of public order plus 24 hours for the fiat exchange step it will not allow users lock the bond (Cannot add htlc (...) reason=expiry too big
). Might become compatible with RoboSats again once trades are shortened.
Bluewallet (Mobile)
It works well. But they are having issues in the custodial mode. Escrows that RoboSats returns are charged to users (so Bluewallet is keeping that balance?). Bonds that are slashed...are charged twice by Blue! More info once they reply to us. EDIT: Blue has confirmed they are working to soon solve these accounting bugs!
Bitcoin Beach (Mobile)
The hodl invoice shows as a grey icon while waiting. Need to tap the back obvious back button to return to the main screen while the payment is pending.
Help keep this page updated
There are many wallets and all of them keep improving at lightning speed. You can contribute to the RoboSats Open Source Project by testing wallets, editing the content of this page and opening a Pull Request