Reply to this note

Please Login to reply.

Discussion

What’s LNhance?

OP_CTV + OP_CHECKSIGFROMSTACK + OP_INTERNALKEY

A very productive, probably safe improvement that allows lightning symmetry and all sorts of other great things (mostly coming from OP_CTV alone)

OP_CHECKSIGFROMSTACK is the only potentially dangerous opcode in that, CTV and INTERNALKEY are both very, very safe.

What’s OP_INTERNALKEY? Never heard of it. 🤷‍♀️

If you're familiar with taproot, a taproot output is

tweak(internal_pubkey, fancy_hash(taptree)) (the result of this is also a pubkey)

When you spend with the taptree (script path) your witness (spending info) includes that `internal_pubkey` which takes up 32 bytes. It's a very important part of validating a script spend, but it's also kind of 32 wasted bytes.

OP_INTERNALKEY just pushes those 32 bytes of pubkey onto the stack so you can use it in your script. (32:1 compression ratio for a public key used in your scripts!)

It's not always usable, but it often is, nice, significant space savings.

APO is much less risky than what's presented here, certainly if you ignore Lightning itself and just think about the base layer.

oh right. ugh, nothing is safe.

CTV is! ;-)

Why is vault so much further along the curve than CTV? I’ve seen other analysis suggesting that vault is closer to the left/bottom.

what's scary about VAULT?

Nothing wrong.

> Both CCV and VAULT give rise to hashrate escrow type recursive contracts, which may be a reason to be cautious about adding them to bitcoin script.

https://twitter.com/reardencode/status/1756185478716657830