Viewing a response to: @dantheman/blockchain-state-representation-should-be-abstract-and-not-part-of-consensus
"...the exact form the game state takes is irrelevant so long as all players agree on the validity of new game inputs" From what I understood, trying to generate a canonical state doesn't make sense because all participants had already agreed with the state of the transaction in the first place when it was included in the ledger. I would say that it makes sense if you have the ability to make the participants agree in the transaction very fast, which I assume is the case of EOS, because you basically have very few of them. If not, making all participants agree with every transaction would take longer, that's why I assume you have to pack those transaction in a block and validate it with hashes.
author | marceltoma |
---|---|
permlink | re-dantheman-blockchain-state-representation-should-be-abstract-and-not-part-of-consensus-20181108t072032367z |
category | etheruem |
json_metadata | {"tags":["etheruem"],"app":"steemit/0.1"} |
created | 2018-11-08 07:20:33 |
last_update | 2018-11-08 07:20:33 |
depth | 1 |
children | 0 |
last_payout | 2018-11-15 07:20:33 |
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 | 706 |
author_reputation | 0 |
root_title | "Blockchain State Representation should be Abstract and not part of Consensus" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 74,899,392 |
net_rshares | 0 |