The Ropsten testnet hit TTD at ~16:00 UTC (~2h after the planned time, great accuracy for PoW standards!). The chain was at ~99.2% participation rate with healthy proposals and sync committee performance - Pretty much the perfect beacon chain to merge, easy to see what breaks!
With the help of the community, we hit TTD and the participation rate dropped by ~13%. We began looking at the missing indexes and knocked on some doors. A large % of the drop was from a config issue on the Nimbus team's nodes, that was easy fixable.
The remaining missing participants are from a config issue in the besu team's nodes that affected just the nimbus CL. The EF nimbus-besu node continues to work fine, reinforcing that it isn't a bigger issue.
The last missing percentage points are explained by a bug found by the nethermind team shortly before the ropsten merge. Thankfully a simple restart fixed the issue.
After the fixes were in place, we quickly saw the participation and proposal rates go back up towards ~99%! About what we had pre-merge!
Does this mean there were no bugs? Almost..
While we have proposals (vital for consensus), some client pairs timeout while building a block and propose with 0 transactions in them. This would affect the throughput of the chain. We saw this in shadow forks too! Fixes incoming!
We're going to monitor the chain over the next few weeks to make sure no client pairs go out of sync. We'd hope that community members raise alarms if they see dapps/tooling not work as expected! Sync nodes in weird ways to find bugs! Send txs!
Not only is Ropsten the first existing testnet to get merged, its also the first testnet where every client team is running an equal part of the network. That's at least a dozen unique ways of setting up a node!
A hearty congratulations to every client team on a great merge! :D