-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TABConf Lightning Socratic Seminar #12
Comments
Splicing merged into CLN @ddustin 10101.finance is building DLCs on lightning Blockstream Greenlight launches, a low-resource non-custodial cloud node service |
How the Voltage LSP Enhances Privacy for Mutiny Wallet Users |
blatantly stolen directly from bitcoin optech...open source woo! @ddustin LND v0.17.0-beta.rc2 is a release candidate for the next major version of this popular LN node implementation. A major new experimental feature planned for this release, which could likely benefit from testing, is support for “simple taproot channels”. @arik-so LDK #2468 allows users to provide a payment_id which is encrypted in an invoice request’s metadata field. LDK checks the metadata in received invoices and will only pay if it recognizes the id and hasn’t already paid another invoice for it. This PR is part of LDK’s work toward implementing BOLT12. |
Welcome
Hello Bitcoiners! This is where we'll organize the topics of discussion for our upcoming Socratic Seminar.
Please use this issue to suggest topics that you'd like to see discussed at the seminar. To suggest a topic, simply add a new comment to this issue with the topic title as the comment's title.
As we work through organizing the topics, feel free to edit and update your comments as needed. This will help us keep everything organized and easy to follow.
To help get us started, here are some main topics of discussion that we could consider:
Remember, this is Bitcoin only, do not post about your favorite clown-coin.
Thank you for your contributions and we look forward to a great seminar!
The text was updated successfully, but these errors were encountered: