danny

I see. Do we use the preview of supported protocols in implementations today?

It we keep `identify`, I suppose that we should specify an [agentVersion](https://github.com/libp2p/specs/tree/master/identify#agentversion) to include the client version as well. Maybe `libp2p-agent-name/version/client-name/version` It looks like there isn't currently an application callback...

I'm sure py-ethereum dependency is likely planned to be removed from eth-testrpc when py-evm is ready, but looking for a bandaid for the meantime.

> the block can be imported. It can be imported "optimistically" or can be imported with some extra annotation to show that the block was not validated by the EL....

Let's swap this feature name/dir to reflect the EIP number -- https://eips.ethereum.org/EIPS/eip-6800

> Every Ethereum Hard Fork should be designed such that the system is indefinitely stable if that hard fork is the last hard fork ever. Agreed that this can't be...

I'm worried that although you can now model the cost of eclipsing a node as non-zero, this cost will still likely be relatively insubstantial to an attacker if we keep...

We don't intend to use any of the fancy `!!` YAML notation due to the more simple parsers not supporting this usage. The `0x` is super common in ethereum and...

I expect we _might_ hit the 100GB limit sometime in the future, but because we are currently only using 10GB, we are needlessly introducing these bandwidth constraints on the repo...

Never mind, I think a normal repo would have worse bandwidth restrictions. Looks like all of the teams are now caching for CI. Hope that works. Otherwise need to look...