Here is a draft article based on your experience:
Title: Metamask + Chrome: Eth Sign Input Data v4 no longer works as expected
Introduction
I recently built a decentralized application (Dapp) on the Polygon network using the Ethereum 2.0 Beacon Chain and MetaMask for web3 integration. After a few weeks of smooth operation, I encountered an unexpected issue with the signed data using the EthSignTypedDataV4 algorithm on my custom EIP-712 template.
Problem
As expected, the Dapp worked fine on desktop and mobile, but when I tried to deploy it in Chrome (and other browsers) for Web 3 compatibility, I got a strange error message. The specific issue was: “Metamask + Chrome: EthSignTypedData_v4 does not exist.” This error did not appear to be related to the actual contract or template installed.
Research and Investigations
I started by checking the MetaMask documentation and Ethereum 2.0 Beacon Chain settings for any changes that might have affected this algorithm. I also checked with my team members who were familiar with the codebase, but none of them could explain the issue.
Solution and Next Steps
After extensive research, I discovered that the EthSignTypedDataV4 algorithm is no longer used, and is being replaced by “eth_signTypedData”. I updated the contract template to use “eth_signTypedData” instead. To confirm the change, I ran several tests on different wallets (MetaMask, WalletConnect, etc.).
To test if the switch was correct, I deployed an identical Dapp on Polygon with the old and new algorithms. Surprisingly, the Dapp worked fine in Chrome and other browsers.
Conclusion
The unexpected error message “Metamask + Chrome: EthSignTypedData_v4 does not exist” suggests a change in MetaMask or Ethereum 2.0 Beacon Chain settings that affected my custom EIP-712 model. Fortunately, I was able to resolve the issue by upgrading to a newer algorithm (“eth_signTypedData”). This experience shows that it is important to regularly review and test existing contracts to ensure they are compatible with changing technologies.
Note: If you encounter similar issues in the future, it is recommended to upgrade your contract model to use “eth_signTypedData” or explore alternative algorithms (e.g. EthSign) that still support your specific requirements.