In celebration of the one-year anniversary of the Zora protocol and the initial release of zorb, we invite you to mint a commemorative NFT for your collection. Minting is open for 20+22 hours on New Years Day and cements your status as an early supporter of Zora.


[zorb.dev](https://zorb.dev/) by [zora.co](https://zora.co).

ZORBS by ZORA

tokenbound-accounts

The onchain UX ecosystem. WalletConnect Inc., previously walletconnect(dot)com, is now 
@reown, and discoverable at reown(dot)com

The easiest way to bring all your users onchain, regardless of whether they already have wallets | Customer love at privy.io/love

@privy wen 1271 /tokenbound  @walletconnect support @zora ????

nature finance onchain /basin @basin
 |  place-based /situs  |  🦇🔊

(1/2) The issue here is the wallet not firing a chainChanged event with the chain ID of the wallet after it's been connected - WC needs this in order to update its internal chain ID state. With an incorrect chain ID from WC, Privy requests an EIP1271 signature on the wrong chain ID which will fail in this context.

(2/2) The solution here is to ensure that the wallet fires a chainChanged event with its chain ID after the proposal to WC. This is the updated recommendation from the WC team and Safe is implementing the same change on their end:

(2/2) The solution here is to ensure that the wallet fires a chainChanged event with its chain ID after the proposal to WC. This is the updated recommendation from the WC team and Safe is implementing the same change on their end: https://github.com/safe-global/safe-wallet-web/pull/3725

Tried this (immediately firing a chainChanged event after approving the session), but Privy still requests a signature for the first chain in the optionalChains list (arbitrum). Is there a way to signal support for all optionalChains but have Privy choose the correct one for signing?