All Collections
Known Issues
Known DApp compatibility issues
Known DApp compatibility issues

Known issues using MetaMask or WalletConnect to access DApps

Written by Mark Hornsby
Updated over a week ago

This article outlines known issues interacting with DApps using the TrustVault MetaMask fork or using WalletConnect directly with the DApp.

TrustVault supports four widely adopted signing methods when interacting with DApps:

  1. eth_signTransaction - The DApp asks TrustVault to sign a transaction and return the signature to the DApp. The DApp is responsible for submitting that transaction to the Ethereum network

  2. eth_sendTransaction - The DApp asks TrustVault to sign a transaction and send directly to the Ethereum network. The DApp will receive the transaction hash

  3. eth_sign - The DApp asks TrustVault to sign a message (which may not be human readable) and return the signature directly. This method is common when voting with governance tokens on a site like

  4. eth_signTypedData aka EIP-712 - The DApp asks TrustVault to sign some structured data with additional information like the type and domain to which the data belongs. This method is commonly used with gnosis-safe for example

Due to the variety of signing methods and DApps out there we will document any known issues in the table below



Depositing funds and trading appears to work successfully via WalletConnect, however exporting your wallet to access your off-chain keys and api key fails and will require a key reset. The cause of this is under investigation and has been reported to the Loopring team. Forced withdrawal back to the L1 chain also works and takes several hours. MetaMask is not supported

Did this answer your question?