LNPBP-3: Deterministic definition of tx out with commitment about lnpbps HOT 2 OPEN

Future SIGHASH_NOINPUT standard BIP-118 [12] MAY BE compatible with this proposal, since a protocol utilizing the present standard MAY define that any transaction commitment with an input signature flag set to SIGHASH_NOINPUT MUST default to the zero value of commitment-specific parameter c. This will still preserve the privacy from the onchain analysis tools due to the presence of the protocol-specific parameter s, which will be unknown for any party that does know which protocol is used by some transaction (given the fact that the used protocol can't be guessed from the transaction itself).

I don't understand how SIGHASH_NOINPUT could interact with the described protocol.
Thank you

from lnpbps.

With SIGHASH_NOINPUT we do not know (at the moment of transaction creation) which transaction output we will be spending, so we do not have access/can’t predict the entropy from the off-chain proof that assigns assets to the future-spend txout.

_{Sent with GitHawk}

from lnpbps.