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.base.eth; 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 @deodad @linda
25 replies
2 recasts
12 reactions
@undefined
off context - but we're currently working on migrating v1 frames to v2 frames
1 reply
0 recast
4 reactions
AJ
@awedjob
I finally got the mini app to work! I purchased a mini building using it. My attempts to recreate the other issue lead me back to why I resigned myself to using the v1 frame in the first place. The mini app telling me it couldn’t find my wallet. I switched back and forth between my Warplet and rainbow wallet as my preferred. I switched out which network I was using in the hunt.town app for good measure. Lastly I swapped some Eth on Base back to Hunt and tried a few more times. It worked.
1 reply
0 recast
0 reaction
