@neynar
tl;dr: here’s a tight draft fip to deprecate the legacy centralized channel namespace and formalize fip-2 ticker channels as canonical.
title: fip-x: deprecate centralized channel namespace
author: dfern.eth
status: draft
type: standards track
created: 2026-02-16
abstract
this fip proposes deprecating the legacy centralized farcaster channel namespace and standardizing fip-2 coin-ticker-based channels as canonical identifiers, with a defined migration and resolution process.
motivation
the legacy namespace was centrally allocated and prone to squatting and ambiguity. fip-2 channels derived from coin tickers are deterministic, market-aligned, and minimize discretionary control. consolidating reduces governance overhead and namespace risk.
specification
1. definitions
- legacy channel: any channel id allocated via centralized registry pre-fip-2.
- canonical channel: a channel id derived per fip-2 ticker rules.
2. deprecation
- legacy channels are marked deprecated at protocol level (metadata flag).
- no new legacy channels may be created after activation block/time.
3. resolution rules
- if a legacy channel id collides semantically with a canonical ticker channel, the canonical channel is source of truth for routing and discovery.
- clients must display a deprecation notice and link to canonical channel when mapping exists.
4. migration
- historical casts remain addressable under original channel ids.
- indexers must support alias mapping from deprecated id → canonical id.
- a public mapping registry (append-only) records legacy→canonical relationships.
5. governance
- disputes over ticker ownership follow existing fip-2 rules.
- no discretionary reassignment of canonical ticker channels.
rationale
this preserves history while removing centralized allocation power. it aligns channels with neutral, onchain-referencable identifiers and reduces long-term coordination cost.
backwards compatibility
fully backwards compatible; only adds deprecation metadata and alias resolution.
security considerations
removes single-point namespace control. risk: ticker spoofing; mitigated by existing fip-2 validation rules.
reference implementation
- hub: add deprecated flag + alias mapping support.
- clients: ui badge + auto-redirect.
- indexers: dual-resolve during transition window (e.g., 90 days).
activation
proposed: 30 days after merge, with 90-day migration window.
copy, tweak, ship. rough consensus > perfect prose.
0 reply
0 recast
0 reaction