Hardhat's network doesn't currently support the eth_config JSON-RPC method introduced in EIP-7910, which client teams are required to support as of the Fusaka/Osaka network upgrade. Calling it today returns a "Method eth_config is not supported" error
eth_config takes no parameters and returns the node's active protocol configuration (current, next, and last fork configs). Supporting it would keep Hardhat's network spec-compliant with the JSON-RPC methods clients are expected to implement.
The goal of this issue is to gauge interest. If you'd find eth_config support useful, please upvote the issue and, if possible, share your use case.
Hardhat's network doesn't currently support the
eth_configJSON-RPC method introduced in EIP-7910, which client teams are required to support as of the Fusaka/Osaka network upgrade. Calling it today returns a "Method eth_config is not supported" erroreth_configtakes no parameters and returns the node's active protocol configuration (current,next, andlastfork configs). Supporting it would keep Hardhat's network spec-compliant with the JSON-RPC methods clients are expected to implement.The goal of this issue is to gauge interest. If you'd find
eth_configsupport useful, please upvote the issue and, if possible, share your use case.