Tony D’Addeo on Farcaster

vrypan |--o--| pfp

@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.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

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.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

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

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

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

vrypan |--o--| pfp

Just o give some context (which btw, I think it could be a popular pattern). I have a subscription contract. I want the user to pay for a subscription (approve USDC, sign contract tx) through the miniapp, and also I want the miniapp to check if the user has an active subscription. I.e. a serverless setup. Sample functions bellow.

1 reply

0 recast

2 reactions

Kasra Rahjerdi pfp

ok so i am insane so i do the payment directly to my warplet then track the tx hash then do the onchain stuff, but again, i am insane

2 replies

0 recast

1 reaction

vrypan |--o--| pfp

Is it possible that some things may not work (or are blocked) on base sepolia? I have a very simple `const approveHash = await sdk.wallet.ethProvider.request(...)` It pops up the transaction approval modal, I click Confirm, I see the same modal again for a second time, but this time it's stuck, then if I leave it long enough, I get a `Provider.UserRejectedRequestError: The user rejected the request.` error. FML, maybe it's my fault, but why is everything so difficult with miniapps?

2 replies

0 recast

1 reaction

Tony D’Addeo pfp

can you share code so I can repro

1 reply

0 recast

1 reaction

vrypan |--o--| pfp

1. Thanks! No need, see #2. 2. A few minutes ago, after trying 100 variations, from js to ts, from ethers to viem and wagmi, etc, I decided to try on mainnet. And... wtf, wtf, wtf, the company that just IPOed and is worth $43B, has a problematic testnet smart contract (if you manage to find it). 3. As a developer, I hate web3 companies. There is this feeling that everything is duck taped or built by people just out of college with no experience. Maybe it's the real-time valuation, that makes everyone fixated with "the number". Maybe it's because devs are not "big, important clients", like in web2 and who cares if I spent 2 days debugging some shit I shouldn't. No attention to detail, no quality control, incomplete documentation.

2 replies

0 recast

2 reactions