vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
@horsefacts.eth, I'm trying to test a USDC approval tx on Base Sepolia, and I get: [Error] provider request error – Provider.UnsupportedMethodError: Farcaster Wallet does not support the requested method: eth_estimateGas Any ideas? What Am I doing wrong? (Using ethers)
1 reply
0 recast
3 reactions
horsefacts pfp
horsefacts
@horsefacts.eth
we don't expose access to read methods from the provider, you need to use your own RPC to call these. Viem makes a distinction between "public" and "wallet" clients, but Ethers doesn't. we only support the "wallet" methods (unfortunately otherwise there is too much abuse of our "free" RPCs). if you're using Ethers, you probably need another Provider, or perhaps to configure your existing Provider to fall back to a public RPC.
1 reply
0 recast
5 reactions
vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
Thank you. I'm once again lost in the living hell called miniapps+wagmi+viem+all_the_shit_that_comes_with_them_and_their_versions :-( I remember there used to be some sample miniapps, but I can't find any links. Are they still somewhere? Are they up to date?
1 reply
0 recast
0 reaction
horsefacts pfp
horsefacts
@horsefacts.eth
The "vanilla" example here is up to date: https://github.com/farcasterxyz/miniapps/blob/main/examples/vanilla/frame/index.ts @jc4p is the main person I know who does not use the viem/wagmi stack for mini apps. you might look at his repos for more examples.
1 reply
0 recast
1 reaction
Kasra Rahjerdi pfp
Kasra Rahjerdi
@jc4p
pure vanilla js (i also use vite) docs for doing this: https://github.com/jc4p/frames-llm-docs/blob/main/LLM_INSTRUCTIONS_vanilla_js.md#onchain-events checkout the calling a custom function and drop the ABI args for it into the ethProvider, then call the Transfer one above it. no viem no wagmi no nothing.
1 reply
0 recast
0 reaction
Kasra Rahjerdi pfp
Kasra Rahjerdi
@jc4p
to be super clear: - anything you want to do that isn't switch chain, sign tx, send tx, or get accounts needs to happen with a diff ethProvider than the mini app supplied one - wagmi etc abstract this out for you, if you do it by hand you need to ensure any calls you need to make happen via another provider (your own custom JSON-RPC, viem with mainnet, wagmi with mainnet, anything you want)
1 reply
0 recast
1 reaction
vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
Kind of late now here, but I'll look into it tomorrow first thing. > no viem, no wagmi [...] You are my man! This is where I were until a few hours ago, just using ethers, and things made sense. Now I know the secret: "Explain it like I'm an LLM"
2 replies
0 recast
2 reactions
jxom pfp
jxom
@jxom
how did things not make sense with viem and/or wagmi? or just more familiar with ethers, and less familiar with viem/wagmi?
1 reply
0 recast
0 reaction
vrypan |--o--| pfp
vrypan |--o--|
@vrypan.eth
They are like a cult. Wagmi is tooooo opinionated, and too abstract to understand what is going on, when something doesn't work, or if you want to do something slightly different. Wagmi has it's own world view, and it makes perfect sense for wagmi believers, but not much if you're not. You have to go all in, or things become hard. Wanna use javascript? Well, just core, and good luck finding your way around the docs. No react? Who writes code without react? No bundler? What do you mean, is there a world where people don't use bundlers? Viem is fine :-)
0 reply
0 recast
0 reaction