---
tags: merge
---

# Merge Call 1 Open Issues

Call agenda: https://github.com/ethereum/pm/issues/290
Design doc: https://hackmd.io/@n0ble/ethereum_consensus_upgrade_mainnet_perspective

## Potential issues

1. What happens if the Application client crashes? Can it ping the Consensus client or does it need to wait for a `NewHead` message?
1. Post-1559, we can have blocks with the same state root. This is more likely post-merge given the block subsidy is 0. Application clients need to be able to handle this
- This may already be possible on Goerli. We should investigate what happens.
1. How do Eth1 clients "know" the Merge has happened?
- Maybe have a release post-merge which hardcodes the merge block / last PoW block / etc.
1. How do clients handle cannonical chains which don't have the highest difficulty?
- Clique increments difficulty upon each valid block