> In a hashed time-lock contract two of the on-chain transactions (one on both chains)...

yes, one on both chains, meaning you have to run nodes for both chains to make sure the info you're getting is correct.  If you trust someone else and they lie to you your reputation is gone forever.

Then we get into a situation where it might be fine to trust 2 or more nodes in consensus because what's the chance they are all telling the same lie?


>The only reason we can do 3 second blocks is the we do not have PoW.

Okay now you're obviously just trolling because that was completely irrelevant and you didn't acknowledge you were wrong about the thing that actually mattered.

We can do 3 second blocks because we know who is making the next block.  End of story.  Rewording it to "not POW" is not helpful.  "Not POW" and "known block producer" mean exactly the same thing in this context.  

The point that actually matters is that we don't have to broadcast unconfirmed transactions to every node in the network.  Yes? Good.  Next time I'll just say "not pow" and I'm sure everyone will just automatically get it.