What is Nostr?
PolyD_
npub1775…9jcw
2024-02-01 14:10:29
in reply to nevent1q…dxlg

PolyD_ on Nostr: I'm aware but the information is dense and wanted to truncate the information to ...

I'm aware but the information is dense and wanted to truncate the information to bitsize. I tried doing it here but I prefer threads. It also allows people to boost specific paragraphs instead of having to boost the entire thing. More is sometimes less.

James O'Beirne made vaults with CTV but wished for further functionality and made OP_VAULT, however it still uses CTV itself for the withdrawal process.

Salvatore Ingala, the creator of MATT (Merkelize All The Things), intends to include OP_CTV in his spec for OP_CCV.

Steven Roose's TXHASH uses OP_CTV as its default mode but desires for more functionality such as Introspection.

Gregory Sanders (Instagibbs) tweaked his spec to include CTV-emulation to save a round trip for making LN-Symmetry channels.

Brandon Black (Reardencode) uses CTV in his LNhance proposal to more efficiently enable LN-symmetry than APO.

Why do I mention all this? It is clear that CTV itself has rough consensus, everyone wants to use it in their proposal but everyone (except Brandon) refuses to eat crow and admit that rough consensus has happened for CTV. Everyone wishes to extend beyond the capabilities for their own interests but we cannot simply enable everything at once.

We truly cannot know what advanced covenant proposals we will desire until we enable basic covenants. CTV has a very narrow design space and there's been no questions about its risks or design. The biggest issue holding it back is its lack of enabling LN-Symmetry and once it was discovered that CTV+CSFS is actually more efficient than APO, there's been no more excuses. Maybe today isn't the day we activate, but its time has come.

Author Public Key
npub1775tuvua6h9mkmlqm3ragxpv3z3eegahhshydj36u2xq72vve9lsq29jcw