Rainbow

Zora

OK, I think the problem may be on Zora's side. Had the same issue today with the Farcaster Iguana NFT mint. Zora isn't checking that Rainbow on the other side is on the right network before sending the transaction request: https://warpcast.com/dfern.eth/0x7e6402

This is still happening, I connect to Zora over Walletconnect, hit mint, and I nearly submit an Ethereum Transaction going to nowhere when it was supposed to be on base. I always check the txn simulator, which is awesome! But there has to be some method to send all wallet requests with an associated chainID, so that both ends of the DApp-Wallet interface aren't out-of-sync on what chain they are supposed to be on. Maybe this is a WalletConnect problem and MWP would solve this?

Aspiring mad scientist,
support team @ /rainbow

Software Engineer @ Cadence Design Systems. B4: Stanford EE / Illinois ECE

What I do is switch to another network in Zora and then switch back to Base, this seems to send the right packets over to the wallet, but yeah good call, I do use the in-wallet browser a lot now

we have been working with zora on identifying the root cause of this issue

rainbow only gets reports of this particular issue specifically with the zora dapp, but it’s been quite difficult for both zora and rainbow to pin point the exact problem

in the meantime, can you try minting it using Rainbow’s in-app web browser? (middle tab in the app)

cc @grunt.eth

Chainid handling is a nightmare between wallets. Viem can give you a false sense of security that a tx will be initiated on the right chain since it’s dependent on wallet behavior.

To handle this, we have some logic before every transaction to asset the wallet is on the expected chain before the transaction prompt. 

For some wallets, automatic chain switching doesn’t work well, so then we have to toast the user to manually switch.