Can we discuss EIP-3756: Gas Limit Cap please?

Some additional note: link from above is not working yet, EIP is currently contained in the following PR: ethereum/EIPs#3756

Proposing to continue discussion on https://hackmd.io/@n0ble/consensus_api_design_space if we have a time during this call

🗓 Calendar link, just so less people (that are lazy like me) miss this important event.

@mkalinin yes, we absolutely will. Hopefully the Geth team have their write up ready :-)

Can we add these EIPs to be discussed?

• EIP-2364: eth/64: forkid-extended protocol handshake
• EIP-2464: eth/65: transaction announcements and retrievals

Here is the Geth writeup about the merge sync: https://github.com/fjl/p2p-drafts/blob/master/merge-sync/merge-sync.md

Followup on last week's discussion on EIP2046 -

I brought this up as the scope of precompiles is growing for L2 and alt-eth chains. In particular nearly all L2 chains have at least one system precompile to initiate exits back to L1.

The proposal was to make this proposal impactful by making the whole range "warm". Martin pointed out this would re-open the broken metre attack.

After thinking about it for two weeks I think the way forward may be to re-open EIP-1109, which is a PRECOMPILEDCALL opcode, that would fail if it called anything but a precompile, and mix it with EIP-2046, which wanted to reduce precompile costs but not make them zero. The proposed fee would be the same as all other CALL series for warm calls, and any call to a non-precompile (as determined by the chain, so hard forks and other-chain additions like L1 exit precompiles would adjust that set) would fail consuming all gas.

As far as when... the next "open" hard fork. It's not important enough to drive a hard fork and not essential to the merge. I posted this to F.E.M. as well. Considering the timing issue I don't think it needs to be discussed in this meeting but I want to put a bug in peoples minds for when the next feature fork happens. If someone has a good reason why it won't work (like undoing Berlin security fixes) please post it to the FEM thread.

Closed in favor of #384

@shemnon I'd recommend pasting your comment into the next call's agenda given we didn't have time to discuss 2046 today.