zama-ai / evmos Goto Github PK

Tasks:

• squeeze commits?
• cleanup README
• check PRs and tags
• check CI: others should be able to trigge our processes
• make docker images publicly available?

Applies to both validators and full nodes.

• How do we deploy them
• How to configure multiple validator in evmos
• How to solve a consensus issue

Issue to overview SOTA regarding EVM implementations in Rust.

Context

State sync is useful for new nodes joining the network. It enables fast bootstrapping by providing state snapshots from which the new node can start syncing.

In the case of our testnet, enabling state sync removes the need to reset the chain when a bugged validator has been producing bad blocks. Indeed, after a "good" snaphshot has been reached, full nodes can ignore the past bad blocks and simply sync from this snapshot.

However, the total supply of native coins is fixed at genesis and since the chain is never reset, the total balance of all EOAs on the testnet in only ever decreasing. This is why a faucet is required together with enabling state sync.

We have to potentially disallow some of the RPC methods for outside users. This is to make sure testnet users can mainly query the blockchain and send transactions, but not mess it up in any way. Still, some RPCs might have to be allowed internally. For example, the debug RPC could be allowed internally for the block explorer, but not to outside users.