Sort:  

A full node needs to store state to validate transaction.
There are multiple block producers
No need to use a always online TTP, you can run your own node
Not all writers are known (though in practice they are known)
Writers are not trusted, they cannot accept invalid transactions
The public can verify the blockchain.

In practice all writers (mining pools) are known for BTC & ETH, especially the top 80% of writers. The bottom 20% of writers only do so with the "permission" of the top 80%. In EOS & Steem anyone can write a block periodically by simply voting for themselves.

Design for you @dan
daniel lamiver.jpg

@dan, sorry for bothering you. But I need your help. I revealed a spammer of Steemit in my post. Now the spammer, @firepower, and @s4s come to flag me. Also the @firepower threatening me. I would like to know whether you can help to clean the spammer, @firepower, and his friend (a robot?) s4s. Thanks

I don't believe that those threatening words were from firepower. Sounds like Mafia. Wondering whether these words are allowed on Steem.

It is and it does store state, just not the unnecessary stuff (like pixel of every picture) 'cos it won't be feasible, in like decades, even in other blockchains. The reason why there are entities called messages is to distinguish between other actions such as voting, liking, transferring, etc., where their addresses can be used by other accounts for these accounts to be able to perform those actions too.

You might want to ask if they store important information of these messages (voting, liking, transferring), of course EOS does! And these specific important information on these messages becomes what you call "state" when block producers bundle them together inside blocks and then store it in the database permanently.

Sure more will be known come the end of the ICO. But interesting post nonetheless @n-ur