-
-
### Current Behavior
Can't open wallet connect with the neversion of web3-onboard in local (other environment looks to work correctly)
```
"@web3-onboard/injected-wallets": "^2.8.5",
"@web3-on…
-
There's an issue signing off-chain transactions.
## Context
The wallet is returning a hash that is likely not using the standard https://eips.ethereum.org/EIPS/eip-712 because when we recover the…
-
Wallet Connect uses this package, which uses a fixed version of bn.js `4.11.8`
Wallet Connect also uses ethereumjs-util, which uses bn.js `^5.1.2`
If we upgrade here, we could eliminate this du…
-
It is normal to use the command NPM run start in the local environment and can connect successfully But when I upload it to the server after use npm run build it, it can't connect successfully. What s…
-
# Goal
WalletConnect has been renamed to Reown, and the Web3Modal project has migrated to AppKit. In order to be up-to-date and take advantage of the latest features and bug fixes, we need to migra…
-
hboon updated
2 years ago
-
When using the connector to call personal_sign, everything works when going to metamask however for any other wallet the message that pops up is in an incorrect format leading to a bad signature:
![…
-
## Problem
As a user, I have an existing GM subscription, then connect to gm.walletconnect.com, and the UI says "subscribe to gm". This is confusing because I thought I already had a subscription. …
-
I’m using Web3 v1.2.11 and the latest WalletConnect Web3 Provider to connect my app to the test wallet. When I send a transaction it shows up in the test wallet as expected. Now, if I confirm the pend…