Backend differences
Last updated
Last updated
Your overall BitBanana experience will depend on the backend you choose to connect with. Check the for a brief summary of the key differences. For a comprehensive explanation of the backend-specific limitations, visit the section.
Manage Peers
✔
✔
✕
✕
Manage channels
✔
✔
✕
✕
Rebalance Channels
✔
✕
✕
✕
View Routing Summary
✔
✔
✕
✕
Sign / Verify Message with Node Pubkey
✔
✔
✕
✕
Manage Watchtowers
✔
✕
✕
✕
View Backend Logs
✔
✔
✕
✕
Bolt11 receiving
✔
✔
✔
✔
Bolt11 sending
✔
✔
✔
✔
Bolt12 receiving
✕
✔
✕
✕
Bolt12 sending
✕
✔
✕
✕
Keysend
✔
✔
✔
✕
LNURL Pay
✔
✔
✔
✔
LNURL Withdraw
✔
✔
✔
✔
LNURL Channel
✔
✔
✕
✕
LNURL Auth
✔
✔
✕
✔
Pay Lightning Addresses
✔
✔
✔
✔
Lightning Fee estimation
✔
✕
✕
✕
Pick first Hop
✔
✕
✕
✕
Display lightning payment route
✔
✕
✕
✕
On-Chain receive
✔
✔
✕
✔ depends on backend
On-Chain send
✔
✔
✕
✕
On-Chain Fee estimation
✔
✕
✕
✕
Send All (On-Chain)
✔
✔
✕
✕
Coin Control
✔
✔
✕
✕
Lock / Unlock UTXOs
✔
✕
✕
✕
BIP 353 (DNS Payment Instructions)
✔
✔
✔
✔
No additional limitations
Incoming unconfirmed transactions are not recognized and therefore not reflected in the balance
Transaction history does not display internal transactions (channel events)
No keysend message display
No closing transaction id for closed channels < 100 confirmations
No legacy Segwit addresses (P2PSH)
No live updates of views (refresh manually)
No absolute on-chain fee calculation
UTXOs cannot be locked/unlocked with BitBanana
No live updates of views (refresh manually)
No live updates of views (refresh manually)
The Detailed Limitations section includes only constraints that aren't visible in the .