Viewing a response to: @markkujantunen/re-edicted-qbp8an
>No. A randomnly selected non-consensus witness signs a block every 1/21 times. Hm... not really. See for yourself. https://hive.arcange.eu/schedule/ The schedule is known and set in advance. >You cannot not share on chain transactions... 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. >Calculating a few hashes for the purposes of the time-locked contract is not too much work. 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.
| author | edicted |
|---|---|
| permlink | re-markkujantunen-qbpb1o |
| category | pob |
| json_metadata | {"tags":["pob"],"app":"peakd/2020.05.5"} |
| created | 2020-06-10 08:17:51 |
| last_update | 2020-06-10 08:17:51 |
| depth | 2 |
| children | 4 |
| last_payout | 2020-06-17 08:17:51 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 782 |
| author_reputation | 3,497,851,531,456,337 |
| root_title | "POB Part 3: The Progression of Hive Atomic Swaps" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 97,878,192 |
| net_rshares | 0 |
>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. The only reason we can do 3 second blocks is the we do not have PoW. >Calculating a few hashes for the purposes of the time-locked contract is not too much work. >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 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.
| author | markkujantunen |
|---|---|
| permlink | re-edicted-qbpblz |
| category | pob |
| json_metadata | {"tags":["pob"],"app":"peakd/2020.05.5"} |
| created | 2020-06-10 08:30:00 |
| last_update | 2020-06-10 08:30:00 |
| depth | 3 |
| children | 3 |
| last_payout | 2020-06-17 08:30:00 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,008 |
| author_reputation | 625,190,695,709,980 |
| root_title | "POB Part 3: The Progression of Hive Atomic Swaps" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 97,878,377 |
| net_rshares | 0 |
> 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.
| author | edicted |
|---|---|
| permlink | re-markkujantunen-qbpdnw |
| category | pob |
| json_metadata | {"tags":["pob"],"app":"peakd/2020.05.5"} |
| created | 2020-06-10 09:14:21 |
| last_update | 2020-06-10 09:14:21 |
| depth | 4 |
| children | 2 |
| last_payout | 2020-06-17 09:14:21 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.000 HBD |
| curator_payout_value | 0.000 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,116 |
| author_reputation | 3,497,851,531,456,337 |
| root_title | "POB Part 3: The Progression of Hive Atomic Swaps" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 97,878,929 |
| net_rshares | 0 |
Never explain by malice what you can explain by a misunderstanding.
| author | markkujantunen |
|---|---|
| permlink | re-edicted-qbpeaa |
| category | pob |
| json_metadata | {"tags":["pob"],"app":"peakd/2020.05.5"} |
| created | 2020-06-10 09:27:48 |
| last_update | 2020-06-10 09:27:48 |
| depth | 5 |
| children | 1 |
| last_payout | 2020-06-17 09:27:48 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.022 HBD |
| curator_payout_value | 0.023 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 67 |
| author_reputation | 625,190,695,709,980 |
| root_title | "POB Part 3: The Progression of Hive Atomic Swaps" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 97,879,066 |
| net_rshares | 171,856,464,325 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| edicted | 0 | 171,856,464,325 | 10% |
hiveblocks