Method not found for calling eth_accounts when using JsonRpcProvider in ethers 6.1.0

[daenamkim]

I am struggling to figure out the error on calling eth_accounts using JsonRpcProvider since BrowserProvider with window.ethereum (MetaMask) works as expected.

• eth_chainId => OK
• eth_blockNumber => OK
• eth_getBalance => OK
• eth_getBlockByNumber => OK
• eth_accounts => Method not found

It was working in ethers 5.7.2 perfectly but not int 6.1.0. Here is the my local geth options to allow access permissions

--ws --ws.addr localhost --ws.port 8646 --ws.api web3,eth,net,personal,admin

Sample in my code

provider = new ethers.JsonRpcProvider(RPC_URL);
console.log(await provider.getBlockNumber());
console.log(await provider.listAccounts());

Debugging in ethers

payload of async _send(payload: JsonRpcPayload | Array<JsonRpcPayload>): Promise<Array<JsonRpcResult>> in provider-jsonrpc.ts

{
  id: 7
  jsonrpc: "2.0"
  method: "eth_accounts"
  params: Array(0)
}

value of function _spelunkMessage(value: any, result: Array<string>): void in provider-jsonrpc.ts

{
  code: -32601
  message: "Method not found"
}

Does anyone have an idea for this? 🙇

[ricmoo]

Did you mean eth_list accounts in your list of ok instead of the second: eth_getBlockByNumber?

[daenamkim]

Did you mean eth_list accounts in your list of ok instead of the second: eth_getBlockByNumber?

Sorry it was typo, it should be eth_accounts and I have chagned.

[daenamkim]

FYI, I'm using

• geth

Geth
Version: 1.11.3-stable
Architecture: arm64
Go Version: go1.20.1
Operating System: darwin

• node: v18.14.0

[ricmoo]

Thanks. I’ll look into this in a second. I feel like it would make sense that itseth_accounts returns “unsupported operation”, an empty array should be returned. But it looks like coalescence is missing categorizing it as an unsupported operation.

[dahu33]

eth_accounts is not enabled by default since go-ethereum v1.11.0

See: https://github.com/ethereum/go-ethereum/releases/tag/v1.11.0

The personal RPC namespace is now deprecated. In order to interact with personal APIs, you need to specifically allow it via the --rpc.enabledeprecatedpersonal command-line flag.