mbaxter

Nice - I like that idea 👍

@rolfyone - No, this is about completing the transition of moving specific `SszSchema` definitions for [eth2 containers](https://github.com/ethereum/eth2.0-specs/blob/dev/specs/phase0/beacon-chain.md#containers) (`BeaconState`, etc) to spec-versioned [`SchemaDefinitions`](https://github.com/ConsenSys/teku/blob/66979d8087a8a8e03a51a2baa7f0523aef1c78be/ethereum/spec/src/main/java/tech/pegasys/teku/spec/schemas/SchemaDefinitions.java#L21-L30). Many of the container schemas reference `SpecConfig` values,...

I still see a number of [static SSZ_SCHEMA definitions](https://github.com/ConsenSys/teku/search?q=SSZ_SCHEMA). For [example](https://github.com/ConsenSys/teku/blob/45b4375239ef26d0f1141a289cfdd60e3285eea8/ethereum/spec/src/main/java/tech/pegasys/teku/spec/datastructures/operations/Deposit.java#L46) :D

Just checking on the status of this work - Is https://github.com/hyperledger/besu/pull/3945 the latest approach?

@pinges - Have you found the source of the issue? I'm seeing a similar problem on some nodes on the Palm network. I ran a node locally for a bit...

@pinges - have you found the root cause of the mismatch between `EthPeers.connections` and `RlpxAgent.connectionsById` ? `RlpxAgent` is the source of truth wrt connection management, so this should just be...

Cool, that makes sense. Will update 👍

### Question 2 > Due to the expected slowly changing nature of the piece of data, I have a slight preference for putting it in `MetaData` but would like to...

### Question 3 I lean towards returning an error as well, as this is the most explicit option. Would it make sense to add a new standard error response code...

Plugin development has been started in a new repo here: https://github.com/Consensys/besu-bad-block-plugin