This may be a relatively simple question to a tech savvy witness, but a complicated question to most steemians. I don't know the answer to this question either, that's why I use the [SteemHelp community](https://beta.steemit.com/trending/hive-111390) to ask and hopefully receive an informed answer. But I have two potential scenarios I believe can happen: 1. all blockchain operations attempted during the 3-second window when a block failed to be produced return an error 2. same as above, except user interfaces re-attempt the operation after a failed block and the user only notices a delay, not an error, unless there really is an error to report. Same as it happens when a node fails to respond, and another one is tried, right? An answer to this question will help us better understand the significance of missed blocks for witnesses. All weighted by how often a witness is scheduled to produce blocks, because 1 missed block for a top 20 witness weighs less than 1 missed block for a backup witness, which is scheduled to produce blocks less often.
| author | gadrian |
|---|---|
| permlink | what-happens-with-blockchain-operations-attempted-during-the-3-second-window-scheduled-to-a-witness-who-misses-the-block |
| category | hive-111390 |
| json_metadata | "{"tags": ["blockchain", "witnesses", "missed-blocks", "steem", "palnet", "neoxian"], "links": ["https://beta.steemit.com/trending/hive-111390"], "app": "steemit/0.2", "format": "markdown", "canonical_url": "https://peakd.com/hive-111390/@gadrian/what-happens-with-blockchain-operations-attempted-during-the-3-second-window-scheduled-to-a-witness-who-misses-the-block"}" |
| created | 2020-01-14 12:08:45 |
| last_update | 2020-05-24 17:20:48 |
| depth | 0 |
| children | 2 |
| last_payout | 2020-01-21 12:08:45 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.349 HBD |
| curator_payout_value | 0.337 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1,058 |
| author_reputation | 643,798,599,957,532 |
| root_title | "What happens with blockchain operations attempted during the 3-second window scheduled to a witness who misses the block?" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 94,389,667 |
| net_rshares | 3,401,720,474,162 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| gregory-f | 0 | 7,724,945,923 | 0.45% | ||
| anomaly | 0 | 127,736,273 | 1% | ||
| erikaflynn | 0 | 4,929,985,134 | 12% | ||
| borislavzlatanov | 0 | 119,721,964,227 | 100% | ||
| techken | 0 | 0 | 0.08% | ||
| ralph-rennoldson | 0 | 1,080,526,823 | 0.37% | ||
| viorel | 0 | 639,733,689 | 75% | ||
| crokkon | 0 | 62,274,710,029 | 100% | ||
| espoem | 0 | 11,376,362,976 | 5% | ||
| qurator | 0 | 93,138,981,400 | 0.76% | ||
| che-shyr | 0 | 1,032,337,339 | 50% | ||
| mytechtrail | 0 | 43,840,482,744 | 25% | ||
| qustodian | 0 | 2,442,090,864 | 0.76% | ||
| abitcoinskeptic | 0 | 117,849,438,436 | 18% | ||
| znnuksfe | 0 | 2,125,510,847,347 | 40% | ||
| raise-me-up | 0 | 0 | 0.01% | ||
| simplymike | 0 | 170,366,711,538 | 49% | ||
| erikah | 0 | 53,873,042,176 | 25% | ||
| stmdev | 0 | 108,384,633 | 1% | ||
| flaxz | 0 | 74,625,244,002 | 30% | ||
| gadrian | 0 | 271,135,226,825 | 100% | ||
| acesontop | 0 | 16,833,718,966 | 100% | ||
| sbi4 | 0 | 148,060,597,675 | 4.88% | ||
| ga10 | 0 | 619,760,444 | 100% | ||
| carolinaelly | 0 | 2,633,797,073 | 100% | ||
| ro-witness | 0 | 62,626,841,429 | 30% | ||
| skylinebuds | 0 | 906,158,137 | 2% | ||
| laissez-faire | 0 | 13,908,797 | 100% | ||
| ga-sm | 0 | 673,260,522 | 100% | ||
| constant-flux | 0 | 69,857,689 | 100% | ||
| gaming-for-fun | 0 | 67,001,412 | 100% | ||
| coredump | 0 | 0 | 10% | ||
| tinyhousecryptos | 0 | 539,886,198 | 5% | ||
| diceshark | 0 | 583,025,648 | 50% | ||
| budwizard | 0 | 0 | 1% | ||
| imbartley | 0 | 1,480,526,503 | 50% | ||
| goldentouch | 0 | 525,772,928 | 50% | ||
| sbi-tokens | 0 | 0 | 0.54% | ||
| organduo.pal | 0 | 0 | 0.76% | ||
| laputis.pal | 0 | 0 | 0.76% | ||
| spinvest-leo | 0 | 3,819,505,625 | 5% | ||
| tonimontana.neo | 0 | 0 | 0.69% | ||
| neoxvoter | 0 | 98,260,219 | 1.5% | ||
| bilpcoinpower | 0 | 200,108,388 | 8% | ||
| toni.pal | 0 | 0 | 0.73% | ||
| steemhelp-cmnty | 0 | 142,692,817 | 100% | ||
| steemhelp-qa | 0 | 0 | 100% | ||
| steemhelp-guides | 0 | 27,041,314 | 100% |
| author | crokkon |
|---|---|
| permlink | q43tco |
| category | hive-111390 |
| json_metadata | "{"app": ""}" |
| created | 2020-01-14 15:50:48 |
| last_update | 2022-09-17 20:12:45 |
| depth | 1 |
| children | 1 |
| last_payout | 2020-01-21 15:50:48 |
| cashout_time | 1969-12-31 23:59:59 |
| total_payout_value | 0.022 HBD |
| curator_payout_value | 0.022 HBD |
| pending_payout_value | 0.000 HBD |
| promoted | 0.000 HBD |
| body_length | 1 |
| author_reputation | 81,214,366,861,104 |
| root_title | "What happens with blockchain operations attempted during the 3-second window scheduled to a witness who misses the block?" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 94,395,117 |
| net_rshares | 278,926,069,928 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| ismailkah | 0 | 5,658,811,002 | 25% | ||
| gadrian | 0 | 273,120,664,251 | 100% | ||
| steemhelp-cmnty | 0 | 146,594,675 | 100% | ||
| steemhelp-qa | 0 | 0 | 100% |
Very interesting! I didn't know about this pool of transactions, but it makes sense that the blockchain itself has a mechanism to deal with missed blocks. Great investigation about the last missed block and what happened around it. Even if you don't have a define answer either, it seems to confirm the idea that no ops are created when a block is missed. But they seem to be included in the next block. Based on your explanation and my observations, I think I can actually spot some moments when it may be possible a missed block just occurred: when an op on Steem takes unusually long, when all the rest before and after had no delay. Thanks for taking the time to respond!
| author | gadrian |
|---|---|
| permlink | re-crokkon-q43u6j |
| category | hive-111390 |
| json_metadata | {"tags":["hive-111390"],"app":"steempeak/2.2.6"} |
| created | 2020-01-14 16:08:45 |
| last_update | 2020-01-14 16:08:45 |
| depth | 2 |
| children | 0 |
| last_payout | 2020-01-21 16:08: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 | 678 |
| author_reputation | 643,798,599,957,532 |
| root_title | "What happens with blockchain operations attempted during the 3-second window scheduled to a witness who misses the block?" |
| beneficiaries | [] |
| max_accepted_payout | 1,000,000.000 HBD |
| percent_hbd | 10,000 |
| post_id | 94,395,655 |
| net_rshares | 0 |
| author_curate_reward | "" |
| voter | weight | wgt% | rshares | pct | time |
|---|---|---|---|---|---|
| steemhelp-qa | 0 | 0 | 100% |
hiveblocks