You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 5, 2025. It is now read-only.
There is an issue specifically with diamonds proxy contract. Probably some or all other proxy contracts work.
When calling the proxy contract address an error is throw:
ContractExecutionError: Error happened while trying to execute a function inside a smart contract
455 | // However, more processing will happen at a higher level to decode the error data,
456 | // according to the Error ABI, if it was available as of EIP-838.
> 457 | if (error?.message.includes('revert')) throw new ContractExecutionError(error);
| ^
458 |
459 | return false;
460 | }
at Function._isReverted (../../../web3v4.x/packages/web3-core/src/web3_request_manager.ts:457:48)
at Web3RequestManager._processJsonRpcResponse (../../../web3v4.x/packages/web3-core/src/web3_request_manager.ts:396:35)
at Web3RequestManager.<anonymous> (../../../web3v4.x/packages/web3-core/src/web3_request_manager.ts:226:16)
at fulfilled (../../../web3v4.x/packages/web3-core/lib/commonjs/web3_request_manager.js:21:58)
Cause:
Note: As shown above the Cause: is empty and no text after it.
It turns out only registered facets functions of a diamonds proxy would be callable. And getName is not available in the proxy contract. So, no issues with web3.js.
Calling methods in a diamonds proxy contract works well and here is an example:
description
There is an issue specifically with diamonds proxy contract. Probably some or all other proxy contracts work.
When calling the proxy contract address an error is throw:
Note: As shown above the
Cause:
is empty and no text after it.The diamonds proxy standard is defined in the EIP 2535: https://eips.ethereum.org/EIPS/eip-2535
Fixing this is needed for the zkSync plugin. Kindly check: ChainSafe/web3-plugin-zksync@37b1615
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: