Create and Use Farcaster Signers
2 min read
I got nerdsniped on Farcaster today.
@keccers.eth was talking about the Sent from coinbasewallet tag. You usually only see these on third-party clients, which is why @artlu having his own stands out on the timeline.
My curiosity was piqued, I started poking around, and soon I had landed somewhere between
and
Nerdsniped. @stevedylandev.eth joined the conversation with the resources he'd already built.
- Cast Keys: https://github.com/stevedylandev/cast-keys
- Mast-cli: https://github.com/stevedylandev/mast-cli
He even posted a video on Youtube as a walkthrough for the process: https://www.youtube.com/watch?v=rPr8A9Ntp1E
How to post with your own "sent from …" tag
Clone Cast Keys and configure it
git clone https://github.com/stevedylandev/cast-keys cd cast-keys npm install # install deps for Cast Keys cp .env.v.sample .env.localEdit
.env.local:DEVELOPER_FID=<FID that should appear in "sent from …"> DEVELOPER_MNEMONIC=<that handle's 12-word phrase>Start Cast Keys and create a signer
npm run devOpen
http://localhost:3000, click Create Signer, scan the QR in Warpcast, pay the Warps, and copy the private key (omit the leading0x).Install the Mast CLI
Script (one-liner)
curl -fsSL https://stevedylan.dev/mast.sh | bashHomebrew
brew install stevedylandev/mast-cli/mast-cliAuthorise Mast with your signer
mast auth # 1 – enter your personal FID # 2 – paste the private keyPost from the terminal
mast new # type the message → Enter # optional: up to two URLs → Enter # optional: channel → EnterRevoke a signer when necessary Warpcast → Settings → Advanced → Manage Connected Apps → select the key → Delete (no cost).
Why run Cast Keys locally? The hosted tool at castkeys.xyz always uses @castkeys' credentials, so every post shows "sent from castkeys." Running it yourself puts your name on the marquee and keeps the keys in your own hands.
It works. I can cast with a custom signer. Next step: a vanity account.