having to manage onchain and lighting balance seperately
Splicing solves this, no?
Splicing solves this, no?
I was under impression that Bitkit had a separate account for LN and onchain. I tried to verify this, but the software required me to agree to "terms and conditions". Realizing that Bitkit was not built for cypherpunks, I uninstalled it.
reply
10 sats \ 1 reply \ @ek 7 Feb
I was under impression that Bitkit had a separate account for LN and onchain
They might have, I don't know. My reply was more a question if you think that splicing would solve this -- independent if Bitkit uses splicing or not.
reply
Splicing could be a solution. Pheonix seems to manage a unified balance well using splicing. But seems the folks at Synonym Software Ltd. prefer to write satsymbol campaigns, terms and conditions, and blog posts that create problems instead of writing code that solves problems.
reply
we'll add splicing whenever LDK supports it.
every wallet with embedded LSPs will eventually have terms and conditions. the largest and most reliable LSPs will become companies, and opening a channel is a service being provided by a company, after all!
reply
₿ the change! Contribute to FOSS! How can Synonym help LDK get splicing?
Why wouldn't a company focus everything on the biggest problem? Why would any employee settle to work on anything less than the biggest problem at the company?
If the biggest problem is trying not to get sued or finding the right words or phrasing for your legal contracts and terms for compliance, sorry, you're doing it wrong. What would satoshi do?
reply
Contribute to FOSS!
Synonym literally maintains React Native LDK, and everything we develop is open-source.
Why wouldn't a company focus everything on the biggest problem?
Who said we aren't? Changing the sats symbol required only a few hours and a few lines of code from one single developer. Our main priorities remain!
reply