Paul Dowman 🔴✨
@pauldowman.eth
@clanker There seems to be a bug where @rainbow executes the transaction on Arbitrum instead of Base. Not sure if it affects other wallets. The same contract address on Arbitrum (which doesn't have a contract deployed) is receiving random transactions.
4 replies
0 recast
0 reaction
grunt.eth
@grunt
Which site are you using? A frame?
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨
@pauldowman.eth
No, just connect wallet from Safari on iOS
1 reply
0 recast
0 reaction
grunt.eth
@grunt
on which site? clanker.world?
1 reply
0 recast
0 reaction
Paul Dowman 🔴✨
@pauldowman.eth
Yes. Also private mode safari in case that matters
1 reply
0 recast
0 reaction
grunt.eth
@grunt
Ok, I’m seeing the same thing on my side on mobile Safari @dish that should be easy to replicate, idk if there’s no network change event? AFAIK the site chooses all the network settings for the WC transaction?
1 reply
0 recast
0 reaction
Jack Dishman
@dish
thanks for the tag, I'll make sure we're switching networks!
1 reply
0 recast
1 reaction
grunt.eth
@grunt
np! i don't a network switch on desktop when I use a browser extension so it might not have that in the flow. we appreciate it! for WC, i think you can also restrict connections solely to base, i see it defaulting to using a bunch of networks at the start
1 reply
0 recast
0 reaction
grunt.eth
@grunt
When testing with mm I see it making the tx on mainnet So I think this is an issue in the dapp where it needs to specify the network for the tx/switch networks before submitting a tx 🫡
2 replies
0 recast
1 reaction
Jack Dishman
@dish
is this for a claim or swap? thank you both!
1 reply
0 recast
0 reaction
grunt.eth
@grunt
I only tested for swaps Using the buy 0.01 eth button on the token pages
1 reply
0 recast
0 reaction