Comments (1)
v3 txns:
- really happening now, one of the first thing merged
- 1p1c?
- questions re the zero conf setting, maybe v3 needs minor tweaks to make sure that you can't broadcast if you have two parents
- could potentially break zero conf
- only p2p? not sure what
- 1000 vbyte limit?
- constrains how much the attacker can may you pay
- smaller you put this, the more bounds you have on the attacker
- in theory w/ 483 HTLCs each direction, that's really large, so 800k sats of miner fee
- is the design too constrained as is?
- there's an upgrade path, with the current mempool stuff this is the initial path
- post cluster mempool and other research, then we can start to look at relaxing the rules
- commitment tx changes:
- zero fee commitment, one anchor
- can put the dust HTLCs inside the ephemeral anchor output, can use that to pay fees (?)
- eliminate
update_fee
- new tnx will still be non-std in the next code release, have more time to see how it interplays
- deployment pipeline:
- v3 code in bitcoind release
- update commitment format
- dyn commit to upgrade the commitment format
new DNS-based addr/invoice resolution:
- how do add offers stuff?
- add another round trip to be able to do the offer
- can just include the user name in the domain and the invoice request
- may not be able to have a distinct node for the offer vs responder?
- should also carve out a larger experimental range for the TLVs in the offer?
- minimal offer is pubkey + description
- how easy is DNSSEC to add on the server-side in 2024?
- should just be a check box for any base DNS service
- cloudflare, etc -- they all have them
- some shitty registrars will charge you
- all clients need to implement DNSSEC validation?
- matt has server+resolver impl: https://http-dns-prover.as97444.net/
- can use DoH (DNS over HTTPs) as well
- can connect out on TCP port 53, etc
zero reserve:
- feature bit route is more robust
- nodes able to distinguish those that support vs not
- asymmetric version?
- can also just relax what you accept at an initial version
- feature bit semantics: I accept and you accept it?
- move to migrate the bLIP to a BOLT, something ppl seem to be asking for a lot
funding v2 + dual funding:
- turns out can't remove the req to send the entire transaction
- needed to handle segwit edge cases
rbf coop close:
- lnd close to interop
- eclair has the branch open, will commit to it given another impl
- upgrade supported?
- if negotiate for old version, will it accept and allow you to try to RBF the old one?
- lnd looking to allow that, if possible
- if negotiate for old version, will it accept and allow you to try to RBF the old one?
trampoline:
- PR rebased, new test vectors
- LDK working on a version
taproot gossip stuff:
- are ppl planning on doing this before channels?
- CLN planning on starting on gossip before channels
- musig2 PR in secp: bitcoin-core/secp256k1#1479
channel jamming:
- PoC thing up, starts setting stuff in the interceptor
- can start to relay the field sooner
liquidity ads:
- JIT channels for liquidity ads
- is it helpful to pin the HTLC in the first state?
- may require more trust in either way, to actually relay the HTLC, etc
- thing t-bast worked on in the past related to this: https://gist.github.com/t-bast/69018875f4f95e660ec2cbbc80f711a6
- does something to tie things into
open
+accept
channel?
- does something to tie things into
peer storage:
- lnd to start working on new version
- has idea to also store HTLC state to improve the SCB recovery story
- trivia impl, can do w/e afterwards
from bolts.
Related Issues (20)
- to_self_delay cannot be updated after opening a channel HOT 3
- Lightning Specification Meeting 2024/03/11 HOT 1
- Lightning Specification Meeting 2024/03/25 HOT 2
- Lightning Specification Meeting 2024/04/08 HOT 3
- Lightning Specification Meeting 2024/04/22 HOT 10
- BOLT-4: Decrypt onion using b_i or k_i HOT 2
- Lightning Specification Meeting 2024/05/06 HOT 4
- Lightning Specification Meeting 2024/05/20 HOT 3
- Add support for bundled payments in BOLT12 HOT 1
- Lightning Specification Meeting 2024/06/03 HOT 2
- BOLT-11: add optional feature bit to indicate delayed settlement of invoice HOT 7
- Lightning Dev Summit Topics HOT 9
- Lightning Specification Meeting 2024/06/17 HOT 1
- Discussion: some confusion re blinded path `max_cltv` HOT 2
- Lightning Specification Meeting 2024/07/01 HOT 1
- Lightning Specification Meeting 2024/07/15 HOT 1
- missing bolt11 example where `n` field must be verified by reader
- Lightning Specification Meeting 2024/07/29 HOT 1
- Lightning Specification Meeting 2024/08/12 HOT 1
- Lightning Specification Meeting 2024/08/26 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bolts.