frames-devs

He/Him | Reparations Now | /aj | /dcl | /wac |

The $24.48 transaction on L1 ETH mainnet - uniswapper occurred 20 minutes ago

Reporting a potential V1 frame bug that could result to losing funds. 

Problem: 
@awedjob submitted a transaction via our v1 frame, which should have been submitted on @base; however the user was prompted to sign a transaction on the mainnet, which resulted in funds getting locked up in the contract. 

Context: 
https://warpcast.com/awedjob/0x7429d31d

Potential Issue:
I believe `switchNetwork` is not being properly called after initial wallet connection.

To Reproduce:
I was able to reproduce it, which shows in the screen recording below. You can see three different attempts in chronological order:

1. The wallet was already connected - tx works as expected ✅
2. The wallet was already connected & was on a different network - switches network and tx works as expected ✅
3. I disconnect the wallet, and connect the wallet when requested - tx attempts to be processed on mainnet, which is not expected ❌

cc: @v @dwr.eth @horsefacts.eth @woj.eth @deodad @linda

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

Developer ecosystem @farcaster, co-founder @bountycaster. Previously: co-founder of Scalar Capital, product at Coinbase, co-producer @ethereumfilm

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

full sack developer intern at /farcards /mintclub warpcast.tools 🔫 my code breaks things :( 


thanks for the great bug report with repro steps and video, looking into this