EIP-695: Create `eth_chainId` method for JSON-RPC

@ligi do you recommend that 695 should revert to Draft based on those concerns, or are you just noting them for posterity?

Not sure if we need to move it back to draft for it. I think just explicitly specifying what the behavior should be to avoid problems like the one above should be enough.

@sorpaas @rekmarks I think the update merged still doesn’t clarify what to return when there’s no chan id – 0?

Also the EIP/ERC is missing the “Security Considerations” section.

@axic, @sorpaas will review my PR specifying what to return in case there’s no chainId (treat as unsupported; return suitable error): https://github.com/ethereum/EIPs/pull/2629

Regarding “Security Considerations,” it’s possible that @sorpaas already knows what to do there, but out of my own curiosity, what exactly are you looking for in that section?

EIP-1 states:

The reviewers here I believe predominantly means those who are very familiar with the Ethereum RPC system.

PR up, feedback appreciated! https://github.com/ethereum/EIPs/pull/2642

Edit: The PR was merged.