Content
@
https://warpcast.com/~/channel/frames-devs
0 reply
0 recast
0 reaction
@undefined
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
25 replies
2 recasts
15 reactions
sebayaki.eth
@if
@awedjob I’ve transferred your lost funds caused by the bug, which occurred due to a delayed update on our frames. Thank you again for reporting the issue! https://basescan.org/tx/0xb64453072d743f810715753c3243031c2fccfc54a67f86f83047b1dc656e8998
1 reply
0 recast
2 reactions
AJ
@awedjob
Thank you so much. Happy to help.
0 reply
0 recast
1 reaction
