-
Notifications
You must be signed in to change notification settings - Fork 34
Creating a UserOperation from scratch and then sending it to bundler for execution #48
Comments
Since you're not using a paymaster, this error means your From a quick scan of your code, this part seems off. Any reason why you are passing a const serializeObj = JSON.stringify(arraifiedHash); // **error suspect 1**
const signature = signer.signMessage(serializeObj); |
Hi @hazim-j , glad that you replied .
To get away with this error , I used web3js library , first I stringified the array version of userophash and then signed it using web3.eth.accounts.sign() . I was able to get the signature and when I passed it to send the UserOperation to bundler I get the error mentioned below : |
that is also an issue for me using infura. Infura also claims to have support for ERC 4337? should it be all a common protocol? |
apparently this works using alchemy.com. So apparently infura is not fully supporting it |
I wanted to create a UserOperation from scratch and then send it to bundler . I am using stackup's bundler URL .
Below is the test I wrote to send a UserOperation to the bundler for inclusion but I am getting an error related to signature .
The smart account ( 0x1e87a1Eca600313aE1388D04e71ea473AD468CAE ) was created by calling SimpleAccountFactory contract deployed at 0x9406Cc6185a346906296840746125a0E44976454 .
Error Logged :
{
error: {
code: -32507,
data: null,
message: 'Invalid UserOp signature or paymaster signature'
},
id: 1,
jsonrpc: '2.0'
}
The text was updated successfully, but these errors were encountered: