owenkemeys

I've written two threads trying to put covenants (specifically CTV) into more visual language to help people reason through how it works and onto the possibilities. [This thread](https://x.com/OwenKemeys/status/1741575353716326835?s=20) covers the...

That's not correct. Let's walk through the use case. I am going to interchangeably use the term "batched" and "zipped" which I think helps people understand the compress/decompress type logic...

That's a very odd example that may be confusing you. I think that's demonstrating how you could achieve a batching effect *without* CTV. Transaction A, the payment into the 10of10...

I built a Figma UX demo of Phoenix wallet with CTV powered Cold Channels, you can check it out here: https://www.figma.com/proto/o4sxu0rEIR1zmletrxtXRn/Phoenix-CTV?type=design&node-id=2-60&t=A12KsqXSncbdgstk-1&scaling=contain&page-id=0%3A1&starting-point-node-id=2%3A60&mode=design This is a working document so bear with me...

Perhaps something got upgraded in the move to calling it CTV then, all I can tell you is the structure described in your quote does not require, take advantage of,...

> Awesome work there. It will be really tricky to weave this smoothly into the experience without putting explainers everywhere. For cold channels, I like the idea of a user...

> If it's possible to chain several claims in a row, and some people earlier in the chain forget their secrets, are the bitcoin for the rest of the chain...

> Not sure if I'm getting it right, but seems like the idea of scaling via covenants highly depends on this nesting, which then might cause these other dependency issues....

> I like the idea of a "scan" button on the home screen for lightning wallets, since user might scan for either sending or receiving. It would also address Owen's...