Mr. Watson, come here — I want to see you

hmm, I sent this using my signer created via https://www.castkeys.xyz

🚾 shows the signer as belonging(?) or created by(?) someone other than me...

picosub.artlu.xyz

SassyHash.artlu.xyz

See pinned cast frame for more.

PFP is my Native.fun Print, genart unique hash of wallet txns -> Faces of Farcaster

and this reply uses Neynar managed signers in the picosub application, but it most likely shows up in Warpcast as coming from neynar

Neynar

If using Neynar for signers, simply pick our managed signers solution (#2 in the linked doc) to get your app name to show up on Warpcast.

You can both get your own brand name to show up while delegating signer management to neynar. Most clients with their own brand use this already (e.g. supercast, buttrfly, bondes, etc. - I'm missing many).

Also works well with embedded wallet providers like privy. This option was actually the very first signer solution we built and over time have expanded to offer a full range.

PS - #3 in the doc will achieve the same effect but is a lot more work. Larger clients like Base use that. 

https://docs.neynar.com/docs/which-signer-should-you-use-and-why

you’re prob using SIWN. Neynar managed signers would show your brand 

https://warpcast.com/rish/0xb3e7f7c5

example screenshot included

building farcaster infra @ /neynar 🪐 | casting @ /rish

1/ Yes likely post Snapchain making signers free 

2/ unfortunately not retroactive but if signers are free, it’s easy to just make a new one 

3/ yeah here’s the doc, you don’t need deal with private secrets at all. Still dealing with signer UUIDs. Just need to make the frontend on your end:

1/ Yes likely post Snapchain making signers free 

2/ unfortunately not retroactive but if signers are free, it’s easy to just make a new one 

3/ yeah here’s the doc, you don’t need deal with private secrets at all. Still dealing with signer UUIDs. Just need to make the frontend on your end: https://docs.neynar.com/docs/integrate-managed-signers

cool.

1/ is there a path to migrate from 1 to 2

2/ would it be retroactive as far as Warpcast displaying the source, or would it involve different signers (I believe this is how it would work?)

3/ are there detailed steps documented for how to follow step 2, e.g., an endpoint to submit private secrets?

tbh I last looked into SIWN about a year ago, and was super happy that the process Just Worked letting me move onto the next step of devving a product 