Sam Wilson

> On further reflection - much of the content of this EIP is now duplicated here https://github.com/ethereum/execution-apis/ - maybe it would be better for this EIP to specify the generics...

We've discussed this change on today's EIPIP, and we will not be modifying EIP-155 to add this chain id. EIPs are not the best place to maintain tables that are...

May I ask why we're switching to warnings?

> * Some external links are now allowed Those exceptions are already supported: https://github.com/ethereum/eipw/blob/4e4bc7b50a094ea9b02551113780b380a096120d/eipw-lint/src/lib.rs#L360-L363 > * EIP-1 doesn't say that you can't use sections not defined in EIP-1 While true,...

This seems reasonable. I'd like to have a bit of discussion on it before we make a decision though. I think we need a few more checks in `eipw` before...

@poojaranjan brought up a great point. A lot of EIPs die in the draft stage, so the first pull request is the only point editors have to influence these EIPs....

I am also interested in providing a meson build configuration for blst. If I (or someone else) were to put up a pull request switching over, is there a chance...

Thanks for getting back to me! > I don't quite follow. It's a Rust project and blst is handled transparently by cargo... So what would "switching over" actually mean in...

> No. blst instructs cargo what to do, no additional steps are required on the user side. Same with Go. Corresponding users simply do what they are accustomed to do,...

I can certainly do meson in addition to what you already have, but that's just adding yet another build system to an already complicated build. If that's what you want,...