# \[Archive\] Invalid signatures **URL:** \ **Category:** Embedded Wallets (Web3Auth)\ **Created:** [July 10, 2023, 5:44pm UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741 "2023-07-10T17:44:21Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![ajagoe](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@ajagoe](https://builder.metamask.io/u/ajagoe)\ **Post date:** [July 10, 2023, 5:44pm UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/1 "2023-07-10T17:44:21Z")
> **🏛 Archived Content from Web3Auth Community** > > This topic was originally posted by **ajagoe** on 7/10/2023. > This content has been migrated from our previous community forum to preserve valuable discussions. * * * I’m using MPC Core Kit with a JWT verifier on a Next.js 13 app under Next Auth using Google as my sign in provider. All works fine, except sometimes–especially if I haven’t used the tab for a while–I get an invalid signature when trying to sign a message or send a signed userop. Here’s an example of the error `sendUserOpToBundler failed Error: Invalid UserOp signature`. Usually, the issue resolves if I reload. And it always resolves if I sign out and sign in again. Any ideas what could be happening and how to correct? Is the timestamp of the token or nonce stale/old perhaps? Any ideas on how to check this? - SDK Version: @web3auth/mpc-core-kit@0.3.1 ```auto const coreKitInstance = new Web3AuthMPCCoreKit({ web3AuthClientId: WEB3AUTH_CLIENTID, web3AuthNetwork: WEB3AUTH_NETWORK.DEVNET, uxMode: "popup", }); await coreKitInstance.init(); ``` - Verifier Details: ```auto const web3authProvider = await coreKitInstance.connect({ subVerifierDetails: { verifier: "denim-mpc-devnet", typeOfLogin: 'jwt', clientId: WEB3AUTH_CLIENTID, jwtParams: { verifierIdField: "sub", id_token: session?.user?.id_token, domain: "http://localhost:3000", } } }) ``` - Verifier Name: denim-mpc-devnet - JWKS Endpoint: [https://www.googleapis.com/oauth2/v3/certs](https://www.googleapis.com/oauth2/v3/certs) - Sample idToken(JWT): Error Message: `client.js:1 sendUserOpToBundler failed Error: processing response error (body="{\"error\":{\"code\":-32507,\"data\":null,\"message\":\"Invalid UserOp signature or paymaster signature\"},\"id\":44,\"jsonrpc\":\"2.0\"}", error={"code":-32507,"data":null}, requestBody="{\"method\":\"eth_sendUserOperation\",\"params\":[{\"sender\":\"0x8ae89588b845Cd9392a545E8c9ba509D814Dfb79\",\"nonce\":\"0x11\",\"initCode\":\"0x\",\"callData\":\"0x940d3c6000000000000000000000000007865c6e87b9f70255377e024ace6630c1eaa37f0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044a9059cbb000000000000000000000000e6d24e69a35944fd15ef2948ca8e07067bd5d57a00000000000000000000000000000000000000000000000000000000005b8d8000000000000000000000000000000000000000000000000000000000\",\"callGasLimit\":\"0xf86e\",\"verificationGasLimit\":\"0x282d4\",\"maxFeePerGas\":\"0x1609a0\",\"maxPriorityFeePerGas\":\"0x4e83c\",\"paymasterAndData\":\"0x\",\"signature\":\"0xaa5e799546d4f8a47733e03e4dd2b33e16d353d354c601fcde115d9141f149b8005d9c49edc684ab66cdf375b496038c88004a5d5b384c986c97c4a0ef85540e1b\",\"preVerificationGas\":\"0xee21\"},\"0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789\"],\"id\":44,\"jsonrpc\":\"2.0\"}", requestMethod="POST", url="https://v0-6-meta-bundler.onrender.com", code=SERVER_ERROR, version=web/5.7.1) at Logger.makeError (index.js:224:1) at Logger.throwError (index.js:233:1) at eval (index.js:261:1) at Generator.next () at fulfilled (index.js:5:43)` ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [July 11, 2023, 1:11am UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/2 "2023-07-11T01:11:10Z")
@ajagoe Thanks for reaching out. Your issue has been forwarded to our team and we will get back with further updates once more information becomes available. ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [July 20, 2023, 6:54pm UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/3 "2023-07-20T18:54:13Z")
@ajagoe As discussed during the community call, please switch to Mainnet instead of Devnet ---
**Author:** ![ajagoe](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@ajagoe](https://builder.metamask.io/u/ajagoe)\ **Post date:** [July 25, 2023, 7:42pm UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/4 "2023-07-25T19:42:26Z")
I’m seeing the same intermittent invalid signature failures on Sapphire Mainnet as on Devnet. Any ideas? ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [July 25, 2023, 9:32pm UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/5 "2023-07-25T21:32:24Z")
@ajagoe Thanks for your feedback. I will forward this information to the team and keep you updated on the findings. ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [September 3, 2023, 12:28am UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/6 "2023-09-03T00:28:00Z")
Hi Andy, Are you still facing this issue on the latest SDK version? ---
**Author:** ![ajagoe](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@ajagoe](https://builder.metamask.io/u/ajagoe)\ **Post date:** [September 3, 2023, 2:01pm UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/7 "2023-09-03T14:01:28Z")
Vijay, this fix has not been merged into a release branch yet – it’s still in the add-third-share branch and release is unchanged at v0.3.1 since July. I have not tested the dev branch. ---
**Author:** ![ofiryieldchain](https://avatars.discourse-cdn.com/v4/letter/o/cc9497/32.png) [@ofiryieldchain](https://builder.metamask.io/u/ofiryieldchain)\ **Post date:** [September 27, 2023, 6:43pm UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/8 "2023-09-27T18:43:49Z")
hi man, hopefully you get this message - have you been able to fix it? we have a very similar setup to yours (custom google JWT, nextjs, web3mpccorekit@0.3.1) and are having the same issue of unstable signature correctness. Wondering if you’ve been able to fix it somehow ---
**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\ **Post date:** [October 6, 2023, 5:00am UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/9 "2023-10-06T05:00:12Z")
Please join our upcoming community call - [Web3Auth Community Call #4 · Zoom · Luma](https://w3a.link/community-call) ---
**Author:** ![maharshi](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/maharshi/32/1525_2.png) [@maharshi](https://builder.metamask.io/u/maharshi)\ **Post date:** [October 6, 2023, 5:32am UTC](https://builder.metamask.io/t/archive-invalid-signatures/1741/10 "2023-10-06T05:32:49Z")
@ofiryieldchain @ajagoe MPC core-kit v1.1.0 is released, check [here](https://github.com/Web3Auth/mpc-core-kit/releases). Please try it out and if it doesn’t fix your issues, chime into out community call where there will be engineers to resolve your doubts.