You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Meeting Date/Time (please note there will be two separate meetings held by me on that date - you can attend any of these or both):
Europe / East Coast Edition
Wednesday 31 March 2021, 14:00 UTC.
Meeting Duration: 45 minutes
Asia / Pacific Edition
Wednesday 31 March 2021, 22:00 UTC.
Meeting Duration: 45 minutes
Agenda
We will review the EIP-3410 (eth_blockNumber EIP) and discuss how to add tests.
We will define eth_getTransactionByHash.
EIP team does not want our EIPs:
Micah — Today at 06:21
My recommendation in the last EIPIP call (when this was brought up) was that it shouldn't be merged because it shouldn't live in the EIPs repository. Specifically, I think this should be added to the ETH2.0-specs repository (if possible, need to coordinate with them) because that will hopefully be the long term living place for Ethereum specifications and the JSON-RPC endpoints are in a perfect position to move over there since they effectively don't exist as EIPs really at all right now.
I think it was @remarks (not sure their handle here on Discord) was who brought it up because they wanted to get https://eips.ethereum.org/EIPS/eip-1474 merged and they seemed to be generally in favor of not using the EIP process for JSON-RPC stuff as well.
Next Call:
Europe / East Coast Edition
Wednesday 14 April 2021, 14:00 UTC.
Asia / Pacific Edition
Wednesday 14 April 2021, 22:00 UTC.
The text was updated successfully, but these errors were encountered:
ETH 1.x JSON RPC API Standard Meeting 5 Agenda
Europe / East Coast Edition
Wednesday 31 March 2021, 14:00 UTC.
Meeting Duration: 45 minutes
Asia / Pacific Edition
Wednesday 31 March 2021, 22:00 UTC.
Meeting Duration: 45 minutes
Agenda
We will review the EIP-3410 (eth_blockNumber EIP) and discuss how to add tests.
We will define eth_getTransactionByHash.
EIP team does not want our EIPs:
Micah — Today at 06:21
My recommendation in the last EIPIP call (when this was brought up) was that it shouldn't be merged because it shouldn't live in the EIPs repository. Specifically, I think this should be added to the ETH2.0-specs repository (if possible, need to coordinate with them) because that will hopefully be the long term living place for Ethereum specifications and the JSON-RPC endpoints are in a perfect position to move over there since they effectively don't exist as EIPs really at all right now.
I think it was @remarks (not sure their handle here on Discord) was who brought it up because they wanted to get https://eips.ethereum.org/EIPS/eip-1474 merged and they seemed to be generally in favor of not using the EIP process for JSON-RPC stuff as well.
Next Call:
Europe / East Coast Edition
Wednesday 14 April 2021, 14:00 UTC.
Asia / Pacific Edition
Wednesday 14 April 2021, 22:00 UTC.
The text was updated successfully, but these errors were encountered: