ProviderError: the method has been deprecated: eth_accounts when deploying with defender.deployProxy on Polygon Mainnet

[saholo21]

Trying to deploy an upgradeable contract using Hardhat and OpenZeppelin Defender with defender.deployProxy on Polygon Mainnet.

The issue arises specifically when attempting to deploy the proxy contract. The deployment fails with the following error: ProviderError: the method has been deprecated: eth_accounts

This problem only occurs on Polygon Mainnet and only when using deployProxy. Other deployment methods work correctly across all networks tested.

Attempts Made

• Deployed two other contracts using deployContract and deployImplementation functions on Polygon Mainnet, both deployed successfully.
• Used defender.deployProxy to deploy the same contract on other networks (Sepolia, Avalanche, etc.), worked without issues.
• Attempted different configurations on Polygon Mainnet, issue persists.

Constraints

• I cannot modify the contract code.
• I can modify the deployment script.

Expected Behavior

The contract should be deployed successfully on Polygon Mainnet using defender.deployProxy, just as it is on other networks.

Actual Behavior

Deployment using defender.deployProxy fails on Polygon Mainnet with the following error: ProviderError: the method has been deprecated: eth_accounts

Steps to Reproduce

1. Use defender.deployProxy to deploy an upgradeable contract on Polygon Mainnet.
2. Observe that deployment fails with the mentioned provider error.
3. Deploy the same contract using the same deployProxy function on other networks (Sepolia, Avalanche, etc.), it succeeds.

Possible Solutions / Help Needed

• Is there a way to avoid or work around the deprecated eth_accounts call during proxy deployment?
• Are there any recommended configurations or versions to ensure compatibility?

Any insights or suggestions would be appreciated!

[charlie-kim]

eth_accounts is deprecated in polygon.
https://www.chainnodes.org/docs/polygon/eth_accounts

[ericglau]

Thanks for reporting. I wasn't able to reproduce this issue on Polygon Amoy testnet.

Would you be able to provide the following information so that we can investigate this further?

• As much of the information listed here as possible (at least the debug logs and installed versions of packages): https://forum.openzeppelin.com/t/required-information-when-requesting-support-for-upgrades-plugins/30530
• Have you noticed the issue on Polygon testnets?
• As a workaround, could you try deploying without using Defender? (e.g. just deploy directly using the Hardhat Upgrades plugin with upgrades.deployProxy)

[saholo21]

Hi @ericglau

• Here are the installed packages and debug logs

@layerzerolabs/hardhat-deploy@0.11.45-lz.4
├── @layerzerolabs/hardhat-tron@3.0.79
├── @matterlabs/hardhat-zksync-verify@1.6.0
├── @matterlabs/hardhat-zksync@1.2.0
├── @nomicfoundation/hardhat-chai-matchers@2.0.6
├── @nomicfoundation/hardhat-ethers@3.0.8
├── @nomicfoundation/hardhat-ignition-ethers@0.15.2
├── @nomicfoundation/hardhat-ignition@0.15.2
├── @nomicfoundation/hardhat-network-helpers@1.0.10
├── @nomicfoundation/hardhat-toolbox@5.0.0
├── @nomicfoundation/hardhat-verify@2.0.13
├── @nomicfoundation/ignition-core@0.15.2
├── @nomiclabs/hardhat-etherscan@3.1.8
├── @npmcli/agent@2.2.0 extraneous
├── @npmcli/fs@3.1.0 extraneous
├── @opentelemetry/api@1.9.0
├── @opentelemetry/auto-instrumentations-node@0.48.0
├── @opentelemetry/core@1.25.1
├── @opentelemetry/exporter-trace-otlp-proto@0.52.1
├── @opentelemetry/propagator-b3@1.25.1
├── @opentelemetry/sdk-node@0.52.1
├── @opentelemetry/sdk-trace-node@1.25.1
├── @openzeppelin/contracts-upgradeable@4.9.6
├── @openzeppelin/contracts@4.9.6
├── @openzeppelin/defender-sdk@2.6.0
├── @openzeppelin/hardhat-upgrades@3.9.0

• Here is the debug log

Waiting for pending deployment of contract Factory with deployment id f132e5c4-9182-4889-ab15-2f79369caa55...
{"level":50,"time":1747245522939,"pid":15304,"hostname":"host","@type":"type.googleapis.com/google.devtools.clouderrorreporting.v1beta1.ReportedErrorEvent","msg":"Admin contract defender deployment failed","error":{"name":"ProviderError","_stack":"ProviderError: the method has been deprecated: eth_accounts\n    at HttpProvider.request (C:\\Users\\working-project\\node_modules\\hardhat\\src\\internal\\core\\providers\\http.ts:107:21)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async AutomaticSenderProvider._getSender (C:\\Users\\working-project\\node_modules\\hardhat\\src\\internal\\core\\providers\\accounts.ts:366:25)\n    at async AutomaticSenderProvider.request (C:\\Users\\working-project\\node_modules\\hardhat\\src\\internal\\core\\providers\\accounts.ts:345:31)\n    at async callOptionalSignature (C:\\Users\\working-project\\node_modules\\@openzeppelin\\hardhat-upgrades\\node_modules\\@openzeppelin\\upgrades-core\\src\\call-optional-signature.ts:7:12)\n    at async inferProxyAdmin (C:\\Users\\working-project\\node_modules\\@openzeppelin\\hardhat-upgrades\\node_modules\\@openzeppelin\\upgrades-core\\src\\infer-proxy-admin.ts:12:17)\n    at async Proxy.deployProxy (C:\\Users\\working-project\\node_modules\\@openzeppelin\\hardhat-upgrades\\src\\deploy-proxy.ts:96:49)\n    at async AdminContractsDeployer.deployOrGetFactory (C:\\Users\\working-project\\lib\\blockchainManager\\evm\\v2\\deployment\\hardhatTasks\\adminContractsDeployer.ts:334:25)\n    at async AdminContractsDeployer.deployAll (C:\\Users\\working-project\\lib\\blockchainManager\\evm\\v2\\deployment\\hardhatTasks\\adminContractsDeployer.ts:139:40)\n    at async SimpleTaskDefinition.action (C:\\Users\\working-project\\lib\\blockchainManager\\evm\\v2\\deployment\\hardhatTasks\\deployAdminContractsWithDefender.ts:125:7)","code":-32000,"_isProviderError":true}}
An unexpected error occurred:
ProviderError: the method has been deprecated: eth_accounts
    at HttpProvider.request (C:\Users\working-project\node_modules\hardhat\src\internal\core\providers\http.ts:107:21)     
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async AutomaticSenderProvider._getSender (C:\Users\working-project\node_modules\hardhat\src\internal\core\providers\accounts.ts:366:25)
    at async AutomaticSenderProvider.request (C:\Users\working-project\node_modules\hardhat\src\internal\core\providers\accounts.ts:345:31)
    at async callOptionalSignature (C:\Users\working-project\node_modules\@openzeppelin\hardhat-upgrades\node_modules\@openzeppelin\upgrades-core\src\call-optional-signature.ts:7:12)
    at async inferProxyAdmin (C:\Users\working-project\node_modules\@openzeppelin\hardhat-upgrades\node_modules\@openzeppelin\upgrades-core\src\infer-proxy-admin.ts:12:17)
    at async Proxy.deployProxy (C:\Users\working-project\node_modules\@openzeppelin\hardhat-upgrades\src\deploy-proxy.ts:96:49)
    at async AdminContractsDeployer.deployOrGetFactory (C:\Users\working-project\lib\blockchainManager\evm\v2\deployment\hardhatTasks\adminContractsDeployer.ts:334:25)
    at async AdminContractsDeployer.deployAll (C:\Users\working-project\lib\blockchainManager\evm\v2\deployment\hardhatTasks\adminContractsDeployer.ts:139:40)
    at async SimpleTaskDefinition.action (C:\Users\working-project\lib\blockchainManager\evm\v2\deployment\hardhatTasks\deployAdminContractsWithDefender.ts:125:7)

• I have not been able to test this deployment on polygon amoy, when trying to deploy it always throws the error Sending deploy transaction failed, ensure your EOA is connected and provider operational: Internal JSON-RPC error. The rpc endpoint configured for amoy seems to be working https://rpc-amoy.polygon.technology and trying with different nodes I get the same error

• Yes, the same contracts were already deployed to polygon mainnet without using defenders and it works as expected

For the record, I ran the same test again in the last few hours against Polygon mainnet without changing anything, and it worked, it seems to be an intermittent issue, but I don't know the root cause or how to make it consistent for future deployments

[ericglau]

Thanks for providing those details. This look like the same root cause as NomicFoundation/hardhat#6632 -- you can try one of the workarounds described there.