You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am building a library which is based on ethers.js extended with some functionalities for my needs. My plan would be to integrate a snap into my library and being able to call some new rpc methods what I introduced on my ethereum node. As far as I see for regular rpc calls this shouldn't be a problem if the snap is already installed in the users wallet, but I have an rpc call which accepts a signed raw transaction, very similarly to eth_sendRawTransaction. This is where my question lies:
1. is it possible to sign a transaction with snaps and send it to my custom rpc endpoint?
Based on my understanding with the keyring api this would be possible, but for that to work my snap needs to be tightly coupled to a dapp because of the allowedOrigins config and my goal would be to integrate it in a more generalized way since it would be part of my library.
2. Is my assumption correct, the dapps needs to be tightly coupled with the snap in this case?
3. Also the eth_signTransaction mentioned here, would still call the original eth_sendRawTransaction after the signing or it would return me the signed raw tx itself? The signer in this case would be a keyring account not the original EOA i am connected with through window.ethereum right?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team!
I am building a library which is based on ethers.js extended with some functionalities for my needs. My plan would be to integrate a snap into my library and being able to call some new rpc methods what I introduced on my ethereum node. As far as I see for regular rpc calls this shouldn't be a problem if the snap is already installed in the users wallet, but I have an rpc call which accepts a signed raw transaction, very similarly to
eth_sendRawTransaction. This is where my question lies:1. is it possible to sign a transaction with snaps and send it to my custom rpc endpoint?
Based on my understanding with the keyring api this would be possible, but for that to work my snap needs to be tightly coupled to a dapp because of the allowedOrigins config and my goal would be to integrate it in a more generalized way since it would be part of my library.
2. Is my assumption correct, the dapps needs to be tightly coupled with the snap in this case?
3. Also the eth_signTransaction mentioned here, would still call the original
eth_sendRawTransactionafter the signing or it would return me the signed raw tx itself? The signer in this case would be a keyring account not the original EOA i am connected with through window.ethereum right?Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions