RE: POB Part 3: The Progression of Hive Atomic Swaps
You are viewing a single comment's thread:
What happens then? Well, @anyx's node knows exactly which node is posting the next block.
No. A randomnly selected non-consensus witness signs a block every 1/21 times.
Rather than having to share that information with the entire network, he simply has to send it to the single node that's scheduled to produce the next block. This makes everything much more efficient, especially if it was @anyx's node that was going to post the next block.
On a blockchain, all transactions are public. You cannot not share on chain transactions with all witness nodes without breaking the chain.
Every atomic swap needs four transactions, two on both chains. The real efficiency gain is that Hive uses DPoS and not PoW. Calculating a few hashes for the purposes of the time-locked contract is not too much work.
Hm... not really. See for yourself.
https://hive.arcange.eu/schedule/
The schedule is known and set in advance.
I'm not talking about on-chain transactions.
I'm talking about transactions that aren't on the chain yet.
This is the only reason we can do quick 3 second blocks.
And how will those hashes be calculated? Using a node from that blockchain. How can a Hive witness trust a [Bitcoin] node they don't control? They can't they have to set up a node they do control.
There seems to be some pretty big misunderstandings here somewhere or another.
The only reason we can do 3 second blocks is the we do not have PoW.
The hashes I'm talking about have nothing to do with PoW where a large number of hashes is calculated. In a hashed time-lock contract two of the on-chain transactions (one on both chains) are done to store two hashed secrets each later to be revealed to the other party. The same key will reveal both secrets to ensure that two or none can move funds on the chain they're going to receive funds on.
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?
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.
Never explain by malice what you can explain by a misunderstanding.
lol man you crack me up
fine fine you win