-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Not a paymaster contract: unknown account #0 #988
Comments
I found that after the release of the beta9 version, the beta9 version configuration cannot be loaded through the network, and the beta8 version was loaded before |
I see this message in the logs but I get it for any of the opengsn versions I've tried, including beta 8.
|
In the latest beta9 version, listAccount is called here, and the obtained address is used to build the paymaster contract object, which causes the contract construction to fail. I have been searching for a long time and do not know where to add this account. |
I have the same an error. |
Same issue in v3.0.0-beta.10 with ethers v5 provider |
Any updates for v3.0.0-beta.10 web3? |
Trying to run a NodeJS script to send a meta transaction for a simple example contract. I've followed the OpenGSN instructions here.
I'm getting the error when trying to initialize a RelayProvider. I'm using the TestPaymasterEverythingAccepted deployed to the Arbitrum Goerli network and I'm using the latest
^3.0.0-beta.9
versions of the@opengsn/contracts
and@opengsn/provider
packages. I'm passing the web3 provider into the newWeb3Provider function but it fails because there's no account. I'm not familiar with the web3 package and I can't seem to find how to configure it with accounts. I've triedweb3.eth.accounts.wallet.add(process.env.PRIVATE_KEY)
but that doesn't seem to affect the web3 provider. Any help would be appreciated!Error
My code
The text was updated successfully, but these errors were encountered: