{"type":"rich","version":"1.0","title":"waxwing wrote","author_name":"waxwing (npub1va…knuu7)","author_url":"https://nostr.now/npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7","provider_name":"njump","provider_url":"https://nostr.now","html":"Little update on Lichen: switching the onchain verification to BABE results in only a few onchain txs instead of 20-25 (so, a much smaller exit delay) and reduces onchain costs by about 7x in terms of bytes. Worst case attacks in terms of a mass exit can then allow scale of about 10k to 50k users with a single operator/hub. And fees kept in reserve are also far lower.\n\nAlready got a long way through building this out using LLMs and there are further optimizations possible afaik such as duty free bits.\n\nAfaict the bottleneck in lichen is all with the hub(s): how much liquidity can they provide, at what price, and they need to stay fully online and available. Very easy for the user: they don't have to watch the bitcoin chain at all. It's like an LSP model, but way better imo.\n\nThe synergy between BABE and lichen appears to be very strong,  enough that I would claim that switching from BitVMX changes this from 'possible' to 'practical'. Still got to do a lot of security analysis, but, optimistic."}
