understanding the brilliance of immutable transactions protected by a blockhash(confirm), then protected by the chain of blockhashes and difficulty of retrying hashes as more go ontop (more confirms as more blocks are added)
knowing that lightening doesnt have that immutable hash protection because the transactions are not settled
You know what I like about facts, Franky? Their immutability
And you're ignoring the fact that all outputs originate from chained hashing when they are mined to begin with, Bitcoin 101. What you're saying in essence is that Lightning will break double-spend protection, which isn't the case, as the Merkle root hash of every output is validated both today and with Lightning transactions.
what is your personal trust level opinion of a single signee zero-confirm transaction (trustless off-chain)
would you consider that as secure as a several confirmed immutable transaction..(onchain)
then having to rely on a multisig contract between multiple users (trust-based)
would you consider that as secure as a single signee zero-confirm (trustless off-chain)
would you consider that as secure as a several confirmed immutable transaction..(onchain)
You're talking gibberish man, there is no reliance on multiple parties for transaction immutability in Lightning. You're conflating multi-party addresses/transactions with Lightning's operation, likely in the hope that your bizarre presentation might confuse some poor frightened individual to believe it. More research needed, Franky lol
my question about asking his trust level is 2 parts.
1. standard traditional transaction with no confirms vs standard traditional transaction with confirms2. lightning transaction not yet settled, vs the two mentioned in point 1eg onchain, several confirm=100% trust
eg onchain, 1 confirm=98% trust
eg offchain traditional, 0 confirm=<50% trust(pre-malle fix/orphan/51%/low fee transaction drop, etc etc)
eg offchain traditional, 0 confirm=>50% trust(post-malle fix/orphan/51%/low fee transaction drop, etc etc)
eg offchain LN multisig, 0 confirm=90% trust(post-malle/orphan/51%/low fee transaction drop, etc etc)
i asked what was his personal opinion on trust.. as you can see i just wrote mine
however
your confusing the immutability of a settled transaction(onchain)..
with a separate situation of the unsettled transaction(offchain) just sitting in a hubs mempool that is signed by user and hub(trusted offchain),
i do laugh that you think while a channel is open the transactions are immutable
just being signed is not enough, if it was there would be no need to ever settle and no need for bitcoin blockchain ever again.. think hard about why there is a settlement mechanism. and why the blockchain exists with its many security features beyond a signature
the short and curlies of it is
although a (starbucks) LN hub may be online all month.. the user wont be. and when the customer signed the final transaction for the month and got their 30th coffee.. that customer wont go back to the app
meaning customer is not there to authorise a change of fee when the hub finally wants to settle to match the current fee war price at the time of settling.
the customer has his coffee, nothing more the customer cares to do.
even CPFP is not fool proof trick to guarantee a sub-fee settlement gets higher priority.
all starbucks can do is keep rebroadcasting and hope someday the fee war settles down to finally get in a block
there are a few other loopholes lightening need to fix before its ready for general public use, but that was just one.
seems before today you didnt even know lightening uses multisig.. maybe you need to check it out a bit more.. bt take off your glory hat of fluffy cloud perfection. and put on a critical thinking cap on
have a nice day though