Andreas Fackler

> query a validator for its inbox state and the corresponding proofs Yes, exactly: So the question is what's needed to prove a certain inbox state. Specifically, for the recipient...

That's a good point. But it really doesn't belong to this issue here. Could you add this argument to the discussion in https://github.com/linera-io/linera-protocol/pull/3350?

Done in https://github.com/linera-io/linera-protocol/pull/3675.

Sure, I'm not against _also_ publishing all transactions in an event stream. I agree that could be useful, and I didn't mean to suggest that the overhead for _the network_...

> We need to decide what to do with `print_peg_certificate_hash` Maybe `linera wallet init` should just always synchronize the admin chain, and print its latest hash.

I realized we already don't sync automatically on wallet initialization anymore. I'll remove the info message for now and created https://github.com/linera-io/linera-protocol/issues/3909.

So the campaign chain would be configured with `open_multi_leader_rounds: true`, and the crowd-funding application as mandatory. That means that, in multi-leader rounds, the system accepts proposals from _anyone_, not only...

`communicate_with_quorum` currently takes a call operator that returns a `Result` (async). It feels like there are two or three nested categories of node errors: * The validator itself encounters an...

> newer certificate on that chain signed by an active committee But only if it refers to the old certificate by _hash_ (e.g. because it's its child, or because it...

I will add a single cache to `WorkerState`, next to the block cache, for now. (Both caches would work equally well if they were split up into one cache per...