pull down to refresh
i feel like you're using this as an opportunity to propose your own solutions rather than asking my insight about something i actually have good context for
i think you're presuming bad faith -- i asked an open ended question, and asked a follow up. you could have responded with anything -- you said eltoo, and said for the purposes of state compaction being the issue. in the ranking of all problems i didn't think that was so severe. i'm mostly an outsider to lightning development, and AJ's proposal has nothing to do with anything i work on. but if it's a solution for state compaction you didn't know about, that's groovy and i hope useful information. if it's not, i'd love to learn why you don't think so.
deleted by author
deleted by author
deleted by author
doesn't getting rid of state work with just AJ's proposal from https://lists.linuxfoundation.org/pipermail/lightning-dev/2021-October/003278.html
should everyone be focused on that?
w.r.t. musig being the barrier, could we just start using Taproot with a NUMS point and a traditional multisig & still get this benefit?