[Bug] Default RPC does not support get_code on Polygon
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
📱 Interface Affected
The default RPC for polygon (polygon-rpc) stopped supporting get_code which is resulting in an error:
Here is the msg data: "id":"1772576074888221952","jsonrpc":"2.0","method":"eth_getCode","params":["0x21120bee87ead5c9131927e0bde380bc8673cfcf","latest"]}
and the error response:
{
"error": "message: API key disabled, reason: tenant disabled, json-rpc code: -32051, rest code: 403"
}
the message is made to polygon-rpc.com uniswaps default rpc configured for the chain. This request is used for smart wallets to determine whether they support 1271 style signatures.
Ideally you should catch this error and fallback to use the RPC configured with the user, this will mitigate all error's by allowing the user to configure their own rpc locally from their connected wallet.
Which application are you experiencing issues with?
- Web (app.uniswap.org)
🧩 App Version
- Version (if known):
- Production build
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the default Polygon RPC configuration and the request path for the shown eth_getCode payload. Reproduce the API-key-disabled error and inspect how the user-configured RPC is selected. Done means smart-wallet detection falls back to the user's RPC when the default request fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, typescript
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100