The inputs used when signing the channel opening transaction (the first signed transaction passed) use SIGHASH NOIPUT to ensure the funds can be spent from the address without the need for an input transaction being broadcast or signed
• In order to ensure the last Commitment Transaction is pushed to the blockchain, OP_CHECKSEQUENCEVERIFY is a suggested soft fork. Based on what the paper suggests, his information is currently stored in a bitcoin transaction but it isn’t enforced by miners or empool broadcasters and can’t be relied upon.
hey jack
in your lesson fortnight thread, you ought to amend the wording concerning SIGHASH_NOINPUT and OP_CHECKSEQUENCEVERIFY. The current text implies that SIGHASH_NOINPUT is a usable opcode in Bitcoin script, and that OP_CHECKSEQUENCEVERIFY is not usable, whereas the opposite is in fact the truth! OP_CHECKSEQUENCEVERIFY was activated by soft-fork (as BIP68 IIRC) several years ago, maybe 2016, while the precise details of a SIGHASH_NOINPUT opcode (including both it's precise fashion of operating _and_ in turn it's final name) have been subject to debate in the development community for many months, that process has not yet finished (although 1 proposal was accepted as a draft BIP...
edit BIP118 authored by Christian Decker)
I think you've just mixed historical documents together with documents that look to future upgrades, should be easy to untangle.