Andreas Fackler

## Motivation Chains with restricted block operations can't process e.g. new events because system operations are not allowed. ## Proposal Allow `Process*Epoch` regardless of permissions. ## Test Plan A test...

## Motivation If all incoming messages are covered by grants, the chain owner should not have any fees left to pay. ## Proposal Remove the base block fee. Disallow empty...

If something goes wrong when trying to propose a new block, the client needs to determine whether to retry or to give up. Make sure all error cases are handled...

## Motivation The validators are not currently expected to start client processes automatically. So chains that enter fallback mode are effectively bricked. ## Proposal Set the default fallback timeout to...

Once a chain is closed, the chain listener should terminate the corresponding tasks ans stop listening for notifications from the validators.

These two `ChainClient` functions do almost the same thing, and both not in an optimal way: * `synchronize_chain_state` downloads the whole chain from _all_ validators in parallel (wasteful) until a...

The faulty test validators currently return an error immediately, which in some cases means the requests to some of the honest test validators are canceled before they get processed. One...

To improve performance for `wallet init --with-new-chain`, the faucet should, whenever its chain gets too long, create a new one and move all its tokens there.

The backport of https://github.com/linera-io/linera-protocol/pull/3887 fails on `testnet_babbage`. The main problem seems to be that we try to use "local" validators (i.e. the ones in the to-be-synchronized chain's state) in several...

Often after `follow-chain`, the user also wants to synchronize the chain. Adding this as an option allows doing that in the same command.