Viewing a response to: @iang/the-message-is-the-medium
For the sake of completeness, one might add that instead of logging inputs or states, you could also store outputs. Given a deterministic statemachine will allow you to derive the list of consecutive states and thus inputs from that. Of course, storing outputs is not what you want :)
| author | xeroc |
|---|---|
| permlink | re-iang-the-message-is-the-medium-20170515t040737411z |
| category | eos |
| json_metadata | {"tags":["eos"],"app":"steemit/0.1"} |
| created | 2017-05-15 04:07:36 |
| last_update | 2017-05-15 04:07:36 |
| depth | 1 |
| children | 2 |
| last_payout | 2017-05-22 04:07:36 |
| 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 | 285 |
| author_reputation | 118,819,064,085,695 |
| root_title | "The Message is the Medium" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 3,419,395 |
| net_rshares | 365,743,564 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| iang | 0 | 365,743,564 | 100% |
Yes, there are lots of subtle variations. In practical implementations, we'd tend to store all three: inputs, state, outputs. But we'd be recovering only from one of them. The others would be debugging logs.
| author | iang |
|---|---|
| permlink | re-xeroc-re-iang-the-message-is-the-medium-20170517t210340117z |
| category | eos |
| json_metadata | {"tags":["eos"],"app":"steemit/0.1"} |
| created | 2017-05-17 21:03:39 |
| last_update | 2017-05-17 21:03:39 |
| depth | 2 |
| children | 0 |
| last_payout | 2017-05-24 21:03:39 |
| 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 | 211 |
| author_reputation | 7,337,084,277,651 |
| root_title | "The Message is the Medium" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 3,506,133 |
| net_rshares | 0 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| belerophon | 0 | 0 | 100% |
EOS at least will store the incoming messages **and** the outcoming messages. And if the outputs become inputs into a later contract, they are referenced again.
| author | iang |
|---|---|
| permlink | re-xeroc-re-iang-the-message-is-the-medium-20170523t171744617z |
| category | eos |
| json_metadata | {"tags":["eos"],"app":"steemit/0.1"} |
| created | 2017-05-23 17:17:45 |
| last_update | 2017-05-23 17:17:45 |
| depth | 2 |
| children | 0 |
| last_payout | 2017-05-30 17:17:45 |
| 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 | 161 |
| author_reputation | 7,337,084,277,651 |
| root_title | "The Message is the Medium" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 3,706,149 |
| net_rshares | 0 |
hiveblocks