Farcaster is ready. Robinhood Chain is now live in the Farcaster Wallet on mobile! (web coming by the end of the week)

18 replies

52 recasts

244 reactions

FAQ - FIP: Channels on Snapchain #276 (you had a lot of good questions, so yes, this is long) > Does this FIP change how channels work or add new features? No. This FIP simply moves channels onto the protocol. For the general user, everything works the way it does today, the difference is any client can read and write channel data, not just the Farcaster client. New capabilities like moderation tools, posting permissions, gating, and financialization tools will come either as follow-up FIPs or as client-level experiments. > I own a channel today. What would I need to do if this change is made? Nothing. Your channel, members, mods, followers, and pins all carry over automatically. You won't need to do anything until your first renewal comes up after this ships. We are also exploring ways to subsidize the renewal fee for channels that meaningfully contribute to the network. > Which chain will this live on, Base or ETH L1? Undecided. Farcaster nodes already read events from Ethereum, Optimism, and Base, and the name-registry contracts work the same on both chains. --Base ----For: it's the cheaper, already-proven path. Farcaster already processes paid onchain events from Base (Farcaster Pro purchases work this way), so channel registrations would follow an existing pattern rather than a new one. And gas on Base costs almost nothing, so what you pay is the registration fee and not much else. ----Against: Base is run by Coinbase. For a naming system meant to last, some feel a single company's chain isn't a neutral enough home. --ETH L1 ----For: the most neutral ground available — no single company controls Ethereum mainnet, and it has the strongest track record of simply continuing to exist. Names registered there would live under ENS, the same system Ethereum names have used for years. ----Against: gas costs more. Though for a transaction you make once a year, the extra dollars matter less than they would on an everyday action. > What is the fee for? Why $25? The fee exists to make squatting expensive without pricing out builders. And it's explicitly not final, the amount and renewal term are open questions in the FIP. The $25 amount is not new, it is inherited from the original launch of Channels. > Was the old $25/yr ever actually enforced? No. It was written in the docs that the $25 would be renewed annually, but the renewals were never enforced. > Can pricing change after launch? Yes, we can absolutely update pricing and add some functionality that makes pricing adaptive in the future. Price is USD-pegged, converted to ETH at payment time via Chainlink, so the mechanism already supports changing the dollar figure. > Do existing channels have to pay now? No. Active channels are grandfathered in automatically (ownership, members, mods, followers, and pins all carry over). Owners won't pay anything until their first grandfathered term ends. Inactive and abandoned channels won't be migrated, which frees those names back up for people who'll actually use them. Activity criteria TBD. > How often do I renew? We think once per year is right, and you'll be able to prepay multiple years at once. Renewal term length is an open question in the FIP. > Where do the registration/renewal fees go? To the Protocol Treasury, which is used to make the protocol's growth self-sustaining. > Are the channel NFTs (ownership) transferable? Yes. Standard ERC-721 transfer; nodes ingest the Transfer event and ownership re-resolves to whichever FID has the new owner address verified. > How long do migrated legacy channels get registered for? We think one year is right, but this is an open question in the FIP. > What happens when a channel expires? If a channel expires, it enters into a 90-day grace period where the owner can still renew or transfer the NFT to a new owner who wishes to renew, name isn't released, casting continues, but mod/admin tools are frozen. After the grace period the name returns to the pool, and any user can trigger an auction to claim it. The new owner of the NFT inherits all the channel's elements — members, history, and pins attach to the channel_id — and the name which resolves to the channel. We can make it clear in the client that the channel has changed ownership so users can decide if they want to still be a member. > What happens to moderation rights when ownership transfers? The new owner gets all owner powers immediately (only owners appoint/remove moderators), and the existing moderator roster carries over until the new owner makes a change. > How do moderation and posting permissions work on protocol generally? - owner appoints/removes moderators (max 10); owner can't be banned - owner + mods: add/remove members, ban/unban, pin (one pin per channel, new replaces old), hide/unhide casts - ban always supersedes a membership add - membership_mode OPEN (self-join valid) or APPROVAL (self-join rejected) - casting is never gated at the protocol level — casting_mode (EVERYONE / MEMBERS_ONLY / RECOMMENDED) is advisory metadata that clients enforce, deliberately, to avoid cross-shard reads - cast hiding (ChannelModerate) is also advisory to clients > How will channels generate value for owners instead of just costing money (rev share, tokens, monetization)? No change. This FIP deliberately only mirrors existing functionality in a more decentralized way. Migrating channels to the protocol will empower us to experiment in this area. > Can I rename a channel without losing its identity and members? No. Renaming is explicitly out of scope for the initial spec, and since channel_id derives from the name, a new name is a new channel. This is the same as the current channel system. > Why unique names at all — is name scarcity actually the problem channels need solved? Because names are how people actually use channels. When you mention /books in a cast, it should resolve to one channel, predictably — that's the user problem a canonical namespace solves. Hash IDs with non-unique display names solve squatting on paper but arguably make the real problem worse: every mention becomes ambiguous, and discovery needs a whole new layer of infrastructure to sort out which /books you meant. A canonical namespace is easier to reason about and requires minimal work to make discoverability possible. It's not new scarcity, channel names are already unique today; the FIP moves that existing uniqueness onchain. Display names will continue to exist alongside /names for flexibility. > Do channel display names stay alongside /names? Yes, and this is the answer to "can I rename my channel." The /name is immutable, same as today. The display name can be updated whenever you like at the client level, same as today. > Can multiple names point to one Channel? No, explicitly not included in the initial spec. > Why build an "ENS-style" system instead of using actual ENS, .farcaster.eth subdomains, or contract-address/DID identity? This is built on ENS. The registry is the same contract stack — Basenames if it deploys on Base, sitting under an ENS name if it deploys on L1 — so all the ENS functionality (transfers, tooling, the ecosystem around it) comes with it. As for .farcaster.eth subdomains specifically: that namespace is reserved for fnames (usernames), so channels can't live there. > Can a multisig or multiple FIDs own a channel? ----Contract-owned (a multisig): yes. A team can share control of the _wallet_ that owns a channel. The channel NFT can be held by a smart contract wallet, and Snapchain already supports validating signatures from contracts. ----Multi-FID owned: No. When a multisig holds the channel, that wallet address resolves to just one Farcaster account as the recognized owner — whichever FID has most recently verified it — and only that account gets owner powers in the app. Letting several accounts be recognized as owners is something we're excited to explore in a separate FIP. > Will there be FC-owned channels for important hubs? Kind of. Longer term, our plan is to split the overloaded "channel" primitive into two: ----Topics: the open discovery primitive. Hashtag-style cast tags anyone can use, no gating. Built for broad, shared spaces and finding what's happening. ----Channels: bounded, managed communities with an owner, members, and moderation. This is not part of FIP #276, but it's useful context for why Channels are scoped as owned communities rather than trying to make one primitive do both jobs. > Will narrowcasting come back? It’s not included in the FIP, but also not excluded. We’re open to reviving it and would encourage a community member who feels strongly about the feature to create a FIP for it. (Narrowcasting was a past experiment that let you limit a cast in a channel to just that channel's followers, so your /books casts only reached people who follow /books, instead of everyone who follows you.) > Why prioritize this now given current activity levels? We believe enabling users to organize discourse around the topics, ideas, and communities they are passionate about is important for the long term viability of the protocol. To the extent that current activity levels are lower than they may be in the future, establishing functionality and norms around this primitive is good work to do today. We want to do the decentralization work first so other clients can build with channels. > Is this already built and decided? Were the PRs staged before the FIP was posted? No. We do have PRs written, but that is typical for FIPs. Nothing has been deployed. Everything is still in development and planning. > How do I give input? Comment on GitHub discussion #276! https://github.com/farcasterxyz/protocol/discussions/276

2 replies

3 recasts

24 reactions

What the devs are working on this week: -Wallet: adding Robinhood Chain to the wallet -Spaces: recording + playback in final review, plus fixes for speaker-invite drops and rooms ending early -Protocol: iterating on the Channels FIP based on community feedback -Feed quality: rolling the Neynar score out across replies, notifications + profiles to replace the old spam labels -Trading: refining limit orders + smarter trade routing for better prices -Translations: now working on the notifications page -Clanker: building the v5 SDK, working through security-audit follow-ups -Snaps: more feed visibility + design improvements Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Sign-in -Some users still getting signed out repeatedly on mobile (top priority, actively working on) Wallet -Scattered token issues: wrong balance, swaps failing on BSC -Limit orders failing at certain buy/sell percentages Mobile -App freezing / force-closing when opening a DM on iOS + Android (fix in review) -Some videos upload but won't play on web (quote-cast video layout bug fixed) -Android: dragging inside a snap scrolls the feed behind it (fix in review) + first-tap side-menu bug fixed Feed -Replies sometimes not showing on a thread, with no "show more replies" option Mini apps -Firefox sometimes needs a page refresh before mini apps load Current mobile version: v2.1.11 (558) What did I miss? 👇

11 replies

42 recasts

161 reactions

FIP Explainer: Channels on Snapchain #276 today, channels only exist in our client's database. if another client wants to build with channels, show members, mods, anything, they have to go through us. why does it matter? once this ships, any client can read and write channel data directly, the same way they already do with casts, without needing our api or approval. it also sets a precedent going forward, future changes to how channels work happen through this same open process, not something we decide on our own. who does this affect? mostly builders, they're the ones who gain something new. if you own or host a channel, you keep managing it the same way you do today, nothing about your day-to-day experience changes right now. what about channels that already exist? nothing breaks and nothing needs to be recreated. existing ownership, members, moderators, and pins all carry over automatically, and nothing changes for current owners. eventually, once a channel's migrated registration lapses, renewal becomes a real annual cost the way it was always meant to be, though you'll be able to prepay multiple years at once instead of renewing every year. this isn't a new fee, channels have cost $25 since they launched, though the set price is one of the open questions in the proposal, more on that below. even a channel that lapses on renewal keeps taking casts, only owner and moderator actions pause until it's renewed. some specifics: 1. ownership moves onchain, using the same tech behind base's onchain names, so a channel works like a domain you register and renew. 2. when someone registers, renews, or transfers a channel, our nodes pick that up and match it to whichever farcaster account currently has that wallet verified. 3. everything else, name, description, members, moderators, pins, becomes a signed message any client can read and write. 4. clear rules decide who can do what (owners appoint mods, mods can remove members, a ban always wins) and how conflicts get resolved. 5. ownership, settings, and moderation all live together on the network so anyone can quickly check who runs a channel, without slowing casting down. 6. existing channels get imported automatically, no recreation needed. open questions: -which chain does this live on? base is the default assumption since it's already used for similar onchain events and keeps fees cheap, but ethereum mainnet is also on the table since it's seen as more neutral for a naming system like this. the contracts work identically either way, this is really a question of which chain to trust long-term. -how much will it cost, and how often? $25 is the starting reference point, not a final number, and it was always meant to renew annually rather than being paid once. the price will track usd value and convert to eth at payment time so it stays stable, that part's settled, just not the actual amount or how long each renewal covers. -what happens the moment a channel lapses? nothing dramatic. there's a 90-day grace period first, same as ens uses. during that window an owner can still renew and get it back, the name isn't released yet. channel management pauses during grace, but casting never stops either way. github.com/farcasterxyz/protocol/discussions/276

5 replies

36 recasts

182 reactions

FIP to move channels onto the protocol is up! take a look and tell us what you think.

3 replies

10 recasts

143 reactions

some of you have been getting logged out and having to dig up your recovery phrase. sorry for the hassle, this wasn't intentional. if you have your recovery phrase, use it to sign back in. no recovery phrase? email recovery normally takes 72 hours, but for bugs like this we push it through faster, usually within 12. still digging into the cause. in the meantime, save your recovery phrase somewhere safe, and set up a passkey if you haven't. thanks for bearing with us.

13 replies

28 recasts

184 reactions

What the devs are working on this week: -Protocol: channels + blocks moving onto the protocol + Degen validator onboarded -Account security: automating account recovery + fixing passkey edge cases + smoother seed-phrase sign-in on mobile -Clanker: working through v5 security-audit follow-ups + ecosystem integrations -Feed quality: a round of Neynar score improvements to better catch coordinated rings + richer data for feed experiments + groundwork for translated posts across languages -Spaces: working on adding recording in Spaces + a fail-safe against accidentally closing your room -Wallet: limit orders are live, now expanding to more tokens + networks, with fill notifications coming ---smarter trade routing for better prices + improved token search + letting verified tokens bypass an overly aggressive spam filter -In-App payments: monthly plan option for Farcaster Pro + paying for storage with your in-app wallet instead of the app store -Rish is heads down working on shipping something, so might not be as responsive as usual for a bit Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Sign-in -iOS: passkey sign-in failing for some users, with the recovery-phrase fallback stalling (one recovery blocker already fixed) -Duplicate passkeys showing after account recovery (fix in review) Wallet -Scattered token issues: a token missing from holdings, a user unable to sell a token they hold, swaps failing on BSC -Secondary wallet seed phrase loading forever (fix shipped) Mobile -App freezing / force-closing when opening a DM on iOS + Android -iOS: posts saving as drafts without being saved (fix shipped) -Quote casting with a video attached failing -Android: back button intermittently not working (again) + first tap on side-menu items not registering Mini apps -Brief pop-up flashing when opening mini apps (fixed) Neynar Developer -Free tier wrongly telling some devs to upgrade to a paid plan (fixed) Current mobile version: v2.1.10 (556) What did I miss? 👇

7 replies

7 recasts

64 reactions

limit orders are rolling out the Warplet (FC wallet)! set a target price to buy when it dips or sell when it rips. the order fills on its own, so you can stop watching charts all day. how to set one: -open a token and tap trade -choose limit buy or limit sell -enter your target price and amount -review and place it you can add an expiry or leave it open, and track or cancel orders anytime from the orders tab. about half of you have it now, and everyone will soon. if you've got it, go set your first order and tell us how it goes!

20 replies

44 recasts

264 reactions

the hat stays on! 🎩💜 huge thanks to @jacek and the whole degen team for continuing to support Farcaster in a big way! want in? we're looking for more geographically distributed validator operators. reply if you're interested in running a snapchain validator, or check out the FIP if you want to help validate without running snapchain: https://github.com/farcasterxyz/protocol/discussions/272

10 replies

27 recasts

145 reactions

What the devs are working on this week: -Clanker: auditing v5, rolling out Clanker Droids, refreshing website / improving docs -Protocol: putting blocks on the protocol, finishing plan to put channels on the protocol + onboarding a new validator -Wallet: reliability fixes + better token search + richer transaction feedback + new feature coming soon -Snaps: smart contract transactions + more feed visibility (distribution experiment going live) -Feed quality: smarter spam filtering + tweaking implementation of Neynar score / ring detection tools -Performance & stability across iOS + Android Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Mini apps -Some mini apps not loading or stuck on a loading screen Wallet -Wallet not loading on iOS (fix pushed) -Duplicate tokens appearing in Explore Mobile -iOS: posts/replies saving as drafts without being saved (fix shipping today) -iOS: DMs sometimes opening straight into a group chat and hiding the DM list Notifications -iOS: notification badge not clearing after you've viewed the notification Neynar Developer -A few small bugs with the new free tier expansion (e.g. over-limit emails firing early) Current mobile version: v2.1.9 (555) What did I miss? 👇

14 replies

24 recasts

165 reactions

meet the team working on farcaster, clanker, and neynar. here's who does what, and how to reach them. for absolutely anything, tag @farcaster. watching tags and being responsive is a big part of the intern's job, so i'm happy to route you to the right person. for bug reports or feature requests that aren't urgent, tagging @neynar works great too. @rish — all things farcaster, clanker, and neynar; tag him for anything. @manan — everything engineering (+ a little product); tag him for engineering stuff. @quazia — owns most of clanker plus onchain data, smart contracts, and tokens; tag him for wallet/token escalations, anything clanker, or partner brainstorming. @vrose.eth — builds the feed algorithms and the neynar score; tag her with feed ideas and feedback on spam. @topocount.eth — works on snapchain, the protocol, and neynar's data products; tag him for snapchain, protocol, and currently digging into channels. @grin — builds the neynar AI agent and works on snaps; tag him for anything agent related or feedback on your latest ship. @ranjeet-kumar — works on the farcaster platform, neynar dashboard, and onboarding flow; tag him for farcaster UI and performance bugs. @obringer.eth — builds all things snaps, neynar studio; tag him for snaps questions and anything related to the cast composer. @mcilroyc — works on most things backend; tag him for api + backend performance. @antimofm.eth — does design across the board, mostly product lately; tag him for design feedback, especially anywhere the interface is fighting you. @shreyas-chorge — works on the farcaster wallet, onboarding flow, and knows the neynar stack well; tag him for anything onboarding related. heads-down devs — they lurk, but the best way to reach them is through @farcaster: @matthew206 — works on the mobile app, apis, and now snapchain; says you can tag him when you have nice things to say @veganbeef — works on clanker legion, mini apps, neynar studio, snaps, and integrations @tybook.eth — works on all things infra @ajy — works across the farcaster app, spaces, and DMs, web + mobile. @vasu-rangpariya (new to the team!) — works on wallet, trading, mini apps, and the in-app browser

11 replies

17 recasts

63 reactions

heads up for anyone on mobile. we just shipped a fix that removes "Sign in with email" on mobile. a recent bug logged some people out, and signing back in with email is a session-only login. it doesn't put your recovery phrase back on your device, so you can't transact with your Farcaster wallet or connect the wallet to mini apps. if you're in that group, you'll see an in-app prompt asking you to restore your wallet or start account recovery. that's expected. what to do: -have your recovery phrase? sign back in with it -don't have it? tap "Start account recovery" this only affects a small number of users and your account and funds are safe. reply here if you're stuck and we'll help!

7 replies

16 recasts

90 reactions

reminder: Farcaster Community Call is this week!

1 reply

9 recasts

81 reactions

What the devs are working on this week: -Wallet: transaction bug + reliability + stronger filtering -Performance & stability across iOS + Android -Clanker: readying v5, rolling out Clanker Legion, refreshing clanker website -Protocol: exploring channels on the protocol + stability testing a new validator -Snaps: adding support for smart contract transactions -Broadening the Neynar API free tier -Spaces: spam protection in rooms + reliability fixes -Feed quality: smarter spam filtering + following feed experiments Known issues we're working on (not an exhaustive list, just what the intern has seen the most of): Wallet -Swap / send / transaction issues (fix shipped, chasing a few edge cases) -"Confirm it's you" prompts resurfacing in mini apps Android -Some sign-ups failing (can't complete, or asked to pay after connecting X) -App crashing for some users (fix shipped) -Duplicate notifications Sign-in -Some users getting logged out -Login flow / passkey bug Spaces -Spaces ending if the host doesn't speak for ~10 min -Spam filtering (comments and listeners) Current mobile version: v2.1.7 (553) Going to be casting updates like this more frequently, so let me know what else would be helpful to include! What did I miss? 👇

10 replies

40 recasts

167 reactions

heads up: quick maintenance window today, 4:30–5pm UTC. anything running on Neynar APIs may lag for a bit

9 replies

12 recasts

79 reactions