Neynar

Celebrating the experimental launch of hubs.neynar.com

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

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

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

DO NOT modify the domain or the SignedKeyRequest constants!

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

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.

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.

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