Andreas Fackler

Reopening as a draft. I will mark it ready for review when https://github.com/linera-io/linera-protocol/issues/3453 is fully implemented.

With https://github.com/linera-io/linera-protocol/pull/3108, this is solved for confirmed blocks. For block proposals, we _do_ want to have the published blobs available at validation time, to check their size. And for validated...

Obsolete because of https://github.com/linera-io/linera-protocol/pull/3672.

Related: #3605, #3781

It means you can't do admin operations from the command line, and the `export` statements it prints make no sense. Also, it's not the way the faucet is intended to...

In those places where we do that (search `shuffle` in `local_node.rs`) we only download things that we immediately verify. So the first validator in line can't _censor_ anything there, they...

Not sure if this is still needed. Instead, maybe `Client::download_certificates` needs a similar treatment as https://github.com/linera-io/linera-protocol/pull/3232? Probably needs discussion, at least.

I know, this issue is just a necessary first step: Separating the two kinds of processing in the code. For scalability we have a different solution in mind: Add a...

Yes, but the skip list doesn't tell you which height you need. We'd still need to at least add the height of the previous block that sent a message to...

Within each validator, the outbox is maintained by the worker with the sender chain, the inbox by the worker with the recipient chain. * First the sender puts the message...