Antoine Riard

If you have specific nits feel free to let them, I’ll address them or please add them with a follow-up PR. Happy to add the recommendations we’re working for fee-bumping...

> That said, I do see how we already have precedence for this with the "cltv_expiry_delta selection" section. Note here the distinction between mechanism vs policy is maintained, as there...

Yes current state of the TLV format discussion is here: https://github.com/ariard/bips/pull/1 and implementation here: https://github.com/bitcoin-inquisition/bitcoin/pull/9

Updated at 6f3dcc2 with the suggestions from https://github.com/ariard/bips/pull/1. I think I still have two issues with the current approach: - in case of script path spend, we might have a...

> I thought the taproot upgrade introduced the annex field to allow for future protocol expansions without requiring further soft forks? There is an interesting design open question - If...

Yes browsed over the hacker news post where a 128-bit prefix varint is argued to be dramatically faster to decode and encode. I think this is unclear if performance-over-space or...

I’m more likely to work on the great consensus cleanup for the coming future. If someone wish to shepherd forward the taproot annex from here, feel free to ask AJ...

@jonatack somehow the annex is one of the best known way to fix technical debt in l2s: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-December/022198.html when i say i don’t currently plan to work on it, it’s...

Closing it, I did backup of the comments for my own archive. If someone wants to grab it, feel free to do it.

Thanks for the feedback so far. Working on a simplified protocol description: "one credential per HTLC", without the complexity of the onions or accounting for accounting HTLC amount/time. The main...