fix: Handle new error message, remove devMode.

examples/angular/src/app/pages/wallet-selector/wallet-selector.component.ts

@@ -46,7 +46,7 @@ const projectId = "30147604c5f01d0bc4482ab0665b5697";
 // TODO: Replace with the NEAR chain after the protocol upgrade.
 const near: Chain = {
   id: 398,
-  name: "NEAR wallet playground",
+  name: "NEAR Protocol Testnet",
   nativeCurrency: {
     decimals: 18,
     name: "NEAR",
@@ -156,7 +156,7 @@ export class WalletSelectorComponent implements OnInit {
         setupNearMobileWallet(),
         setupMintbaseWallet({ contractId: CONTRACT_ID }),
         setupBitteWallet({ contractId: CONTRACT_ID }),
-        setupEthereumWallets({ wagmiConfig, web3Modal, devMode: true }),
+        setupEthereumWallets({ wagmiConfig, web3Modal }),
       ],
     });
 

examples/react/contexts/WalletSelectorContext.tsx

@@ -77,7 +77,7 @@ const projectId = "30147604c5f01d0bc4482ab0665b5697";
 // TODO: Replace with the NEAR chain after the protocol upgrade.
 const near: Chain = {
   id: 398,
-  name: "NEAR wallet playground",
+  name: "NEAR Protocol Testnet",
   nativeCurrency: {
     decimals: 18,
     name: "NEAR",
@@ -188,7 +188,7 @@ export const WalletSelectorContextProvider: React.FC<{
         setupNearMobileWallet(),
         setupMintbaseWallet({ contractId: CONTRACT_ID }),
         setupBitteWallet({ contractId: CONTRACT_ID }),
-        setupEthereumWallets({ wagmiConfig, web3Modal, devMode: true }),
+        setupEthereumWallets({ wagmiConfig, web3Modal }),
       ],
     });
     const _modal = setupModal(_selector, {

packages/ethereum-wallets/README.md

@@ -17,7 +17,7 @@ NEP-518 doesn't support multiple actions within the same transaction, so when mu
 
 NEP-518 rpc relayer uses a FunctionCall access key to execute transactions on behalf of the user by calling `rlp_execute`. If this key is not yet added, the wallet will be onboarded before the first transaction is made.
 
-`signMessage` and `verifyOwner` are not implemented because Ethereum wallets are not compatible with these standards, instead a dApp can use `eth_sign` or `eth_signTypedData_v4` to authenticate the wallet by interacting with it directly.
+`signMessage` and `verifyOwner` are not implemented because Ethereum wallets are not compatible with these standards, instead a dApp can use `personal_sign` or `eth_signTypedData_v4` to authenticate the wallet by interacting with it directly.
 
 ## Installation and Usage
 

packages/ethereum-wallets/src/lib/index.ts

@@ -439,6 +439,8 @@ const EthereumWallets: WalletBehaviourFactory<
       logger.error(error);
       if (
         !error.message?.includes("does not exist while viewing") &&
+        !error.message?.includes("doesn't exist") &&
+        !error.message?.includes("does not exist") &&
         !error.message?.includes("has never been observed on the node")
       ) {
         throw new Error(
@@ -936,14 +938,14 @@ const EthereumWallets: WalletBehaviourFactory<
     async verifyOwner({ message }) {
       logger.log("EthereumWallets:verifyOwner", { message });
       throw new Error(
-        "Not implemented: ed25519 N/A, use eth_sign or eth_signTypedData_v4 instead."
+        "Not implemented: ed25519 N/A, '\x19Ethereum Signed Message:\n' prefix is not compatible, use personal_sign or eth_signTypedData_v4 instead."
       );
     },
 
     async signMessage({ message, nonce, recipient }) {
       logger.log("EthereumWallets:signMessage", { message, nonce, recipient });
       throw new Error(
-        "Not implemented: ed25519 N/A, use eth_sign or eth_signTypedData_v4 instead."
+        "Not implemented: ed25519 N/A, '\x19Ethereum Signed Message:\n' prefix is not compatible, use personal_sign or eth_signTypedData_v4 instead."
       );
     },