falls sich jemand gewundert hat, was bei Tezos los war/ist....
Tezos Glitch Stops Block Production In Early Tech Trouble
The Reddit user explained the situation as follows:
“The baker under the public key tz1KksC8RvjUWAbXYJuNrUbontHGor26Cztk committed a safety fault at level 194934, which was later denounced, causing the baker to lose security deposits, rewards, and fees.”
https://usethebitcoin.com/tezos-glitch-stop-block-production-tech-trouble/der daraus resultierende Patch:
Protocol 003_PsddFKi3
Description of the patch
Fix to prevent account creation spam
While creating accounts currently requires a .257 tez burn, there is currently no cost to create implicit accounts, despite them occupying space in the context. This patch adjusts the cost to .257 tez for both regular (KT1) and implicit (tz1) accounts.
Error handling for nonce revelation
In cycle 48, a baker who lost their deposits and rewards due to double baking also did not inject nonce revelation. The protocol reached an error condition after trying to take away rewards from an account for which rewards had already been slashed. As a result, no new blocks could be accepted unless the nonces were revealed. The patch ensures correct handling of this scenario.
...
The node will automatically switch over to the new protocol at block height 204762 expected to occur after 2018-11-26T17:30:00 UTC.
After updating, all processes (the node, baker, endorser, and accuser) should be restarted. The updated node handles multiple protocols but notice that there are several, protocol-specific, versions of every other processes. In order not to miss a block or an endorsement, you may run versions 002_PsYLVpVv and 003_PsddFKi3 of the baker and endorser in parallel. Versions 003_PsddFKi3 of the baking and endorsement processes will not start baking or endorsing until the target block height. Version 002_PsYLVpVv will stop by themselves and it will be safe to stop them at that time. This has been tested and the processes do not attempt to bake at the same height.
However, as an extra precaution, specially if you do not use a hardware key or a remote-signer with a high water-mark, you may consider waiting until the target block height to shut down the old process and start the new one.)
https://tezos.gitlab.io/master/protocols/003_PsddFKi3.html 
).
).