Skip to content

Executing Public Actions from a WalletClient #439

Discussion options

You must be logged in to vote

The reason why we designed it to be separate is because wallet providers (Injected window.ethereum, WalletConnect v2, etc) may not provide a large majority of "node"/"public" RPC methods like eth_call, eth_newFilter, eth_getLogs, etc... So it is separate to guard the consumer from invoking the wrong methods.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@devsquaaa
Comment options

@tmm
Comment options

Answer selected by devsquaaa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants