Content
@
0 reply
1 recast
1 reaction
TMO ↑ 🍄 ↑
@tmo.eth
@privy wen 1271 /tokenbound @walletconnect support @zora ????
2 replies
0 recast
0 reaction
Max
@segall
Hi! DMing you to better understand this one!
2 replies
0 recast
0 reaction
Max
@segall
(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.
1 reply
0 recast
1 reaction