Note: Please feel free to add comments to this document! (login with github) About Splicing Best starting point is Dusty Daemon's lightningsplice.com site. What is Splicing? Splicing can change the capacity of a channel, without closing it. It's possible to increase or decrease the capacity, by adding or removing some funds on-chain. Why Splicing? Splicing can be used for different goals. e.g.:

Eredeti: The Little Bitcoin Book https://littlebitcoinbook.com/ A fordítás elérhető PDF-ben, Google Docs-ban, és Asciidoc formátumban GitHub alatt. Bármelyik használható. PDF: ez a nyomtatási kép, de nem kommentezhető jól (kb. 4MB). Itt érhető el: https://drive.google.com/file/d/1H1Vb5oJh7Y05VLRwD3pWVjWeyyM3jVr5/view?usp=sharing Google Docs: a formázás nem pontos, de jól kommentezhető. Tudok hozzáférést adni (Google ID kell hozzá), itt érhető el: https://docs.google.com/document/d/1jBM4luVNtz0ja4PwunWDFD_P5DUdA2ZFOcDJDaL8wfQ/edit?usp=sharing

Overview, Use Nostr has many clients, and it's common to use multiple clients, e.g. an app on mobile and a web app on larger screens. Or event several. But every client that has your secret key is a securtiy risk. One can use 'read-only' mode in secondary clients, by importing npub only, but then you can't post, reply, like or do any action. A propsed solution is NIP-26 delegations, whereby you use two identities, allowing a secondary client/identity to post on your behalf without risking your main secret key. Typical case case details (NIP-26)