<oembed><type>rich</type><version>1.0</version><title>matthewjablack wrote</title><author_name>matthewjablack (npub1wf…qsxhy)</author_name><author_url>https://yabu.me/npub1wf7w8mrzqs3uvd8wsp774462d3rtttzwetuhpmzjccgn63emy4ls5qsxhy</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>&gt; My point was that Peter had overlooked the other case, specifically the risk that CTV could motivate people to pay for faster transactions.&#xA;&#xA;Why would CTV motivate people to pay for faster transactions more than any other normal transaction? I don&#39;t see how it would create more motivation for paying OOB for faster transactions than lightning or on-chain payments. &#xA;&#xA;&gt; and I don’t believe anyone can know for certain — because our assumptions are based on the past and not what people might invent in the future&#xA;&#xA;CTV has been pretty well researched over the past 4 years since it&#39;s inception. It&#39;s gone through several iterations to make it safer. In fact there&#39;s been way more scrutiny and edge cases researched for CTV than was ever done with Taproot. &#xA;&#xA;&gt; I could imagine that this could be solved by the coordinator frequently reissuing the contracts with the current value.&#xA;&#xA;The key thing here, is you can&#39;t exit the contract if your counterparty is offline. So once the DLC options contract is created, unless you&#39;ve pre-signed for all the possibilities ahead of time, if your counterparty goes offline, then you can&#39;t exit, and you have to hold to expiry. &#xA;&#xA;You could have dedicated market makers that take the other side of contracts, but that means the market maker can&#39;t exit if their counterparty goes offline, making this process very capital inefficient (not to mention you can&#39;t do portfolio margining obviously, since risk is defined within the DLC contract itself). &#xA;&#xA;So unless you have all those pre-signed outcomes, you won&#39;t have secondary markets. But you won&#39;t have secondary markets without infinite compute. &#xA;&#xA;So as much as I would like that use case to work, CTV just doesn&#39;t enable it. &#xA;&#xA;CAT on the other hand would enable it, since you can commit to specific inputs and outputs, whereas with CTV you must commit to ALL inputs and outputs. &#xA;&#xA;This is why CTV is actually incredibly conservative. At face value things that you think are possible, aren&#39;t actually possible. It&#39;s a very restrictive covenant scheme. </html></oembed>