Here is a draft article based on your experience:
Title: Metamask + Chrome: Eth Sign Type v4 data no longer works as expected
Introduction
I recently developed a decentralized application (Dapp) on the Polygon network using 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 in my custom EIP-712 schema.
Problem
As expected, my Dapp worked fine on desktop and mobile, but when I tried to deploy it in Chrome (and other browsers) for web3 interactions, I encountered a strange error message. The specific issue was: „Metamask + Chrome: EthSignTypedData_v4 does not exist”. This error does not appear to be related to my actual deployed contract or schema.
Research and Investigation
I started by checking the MetaMask documentation and Ethereum 2.0 Beacon Chain settings for changes that might affect this specific 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 doing some thorough investigation, I found that the EthSignTypedDataV4 algorithm was deprecated in favor of eth_signTypedData. I updated my contract schema to use eth_signTypedData instead. I ran a series of tests using different wallets (MetaMask, WalletConnect, etc.) to confirm the change.
To verify the switch, I deployed an identical Dapp on Polygon with both 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” indicates a change in MetaMask or Ethereum 2.0 Beacon Chain settings that affected my own EIP-712 schema. Fortunately, I was able to resolve the issue by updating to a newer algorithm (eth_signTypedData). This experience highlights the importance of regularly reviewing and testing our deployed contracts for compatibility with changing technologies.
Note: If you encounter similar issues in the future, we recommend that you update your contract schema to use eth_signTypedData or explore alternative algorithms (such as EthSign) that still support your specific requirements.
