Content
@
https://opensea.io/collection/neynar-1
0 reply
0 recast
0 reaction
Manan
@manan
The most dreaded screen for Farcaster developers trying to use signers for the first time :) This thread is going to list down the gotchas that I've seen developers run into while trying to set up signer approvals for their apps
1 reply
3 recasts
8 reactions
Manan
@manan
Developer FID & Developer Mnemonic - Ensure that fid is an integer - Ensure that the mnemonic corresponds to the same farcaster account as the fid. - Good-to-have > Ask @dwr.eth for a developer account if needed https://warpcast.com/dwr.eth/0xef6e56
1 reply
0 recast
0 reaction
Manan
@manan
DO NOT modify the domain or the SignedKeyRequest constants!
1 reply
0 recast
0 reaction
Manan
@manan
deadline - Ensure you're using the same exact value for signature generation as well as the POST API's parameter. - Ensure it's an integer, not a string
1 reply
0 recast
0 reaction
Manan
@manan
key - Ensure that key is a hex string with a 0x prefix in the signature generation (despite the fact that it's listed as type bytes) - Ensure that this is the public key of the signer, not the public key of your developer account.
1 reply
0 recast
0 reaction
Manan
@manan
Big thanks to @kevinoconnell @slokh @pixel @notdevin.eth and a lot of other devs for their patience while discovering these gotchas. We'll be able to add detections for most of these in upcoming SDK and Neynar APIs to make the errors explicit and more readable.
1 reply
0 recast
0 reaction
