Repository navigation
Add Splicing #1191
Description
Hello, I would like to request some guidance for users receiving splice transactions.
Potential places it can be added:
https://bitcoin.design/guide/how-it-works/liquidity/
https://bitcoin.design/guide/daily-spending-wallet/requesting/receiving/
I'll follow up with detailed suggestions but this flow can be tested in the Phoenix mobile wallet.
Activity
swedishfrenchpress commentedon Aug 20, 2025
Are there any other wallets that have a GUI for splicing? I think Phoenix is the only one that comes to my mind.
ConorOkus commentedon Aug 25, 2025
Only Phoenix that I'm aware of...
yashrajd commentedon Aug 28, 2025
Splicing is one the those things where the UX conflict-of-visions comes up: do you want users to form an understanding or a sort of mental model about these thing, even if it comes at the cost of some complexity & mental overhead? Or do you want to hide the inner workings and explain as less as you can to minimise the new things users have to learn as they transact?
Here's what I'd say in terms of basic guidance:
end of rant, what do you guys think?
agree.
GBKS commentedon Sep 8, 2025
Let's break this down. Can you maybe share an example situation? Is this for when you want to receive an amount larger than your current receive limit (aka inbound liquidity)? So your channel partner would put more bitcoin in the channel to send over to you?
This is not super easy to recreate, so sharing a screenshot would also be helpful.
yashrajd commentedon Sep 9, 2025
No screenshot, but here's the thread.
An interesting one from the same thread: https://x.com/yashraj__/status/1764871285199478841
GBKS commentedon Sep 10, 2025
Thanks for sharing that context. I agree with the commenters saying that you sound like you are broke and that you should use Bitcoin Cash. Jokes aside, it is a total no-brainer that wallets should inform users about fees. And not just in an extreme situation like this one, but as a general practice (starting with the website). Fees are essential for us to evaluate whether we want to use a service/product or not. We are pretty sensitive to this from our experience with banks (for example, surprise extra charges for credit card use when traveling). And one bad experience can really break trust in the service.
ConorOkus commentedon Sep 12, 2025
I've started adding content related to splicing here: #1194
Should we change https://bitcoin.design/guide/daily-spending-wallet/requesting/receiving/#receiving-on-chain-payments to recommend splicing by default instead of submarine swaps? This might be a better place to express the need to show users fees upfront and the provide the corresponding UI mock ups
yashrajd commentedon Sep 17, 2025
Good to see splicing starting to be added to guidance now that all ln implementations support it.
The requesting page has fee mockups that kinda cover the splicing case. But agree, with bolt-12 the user might never go through a 'request' flow but find themselves receiving funds like require splicing.