Beta reference · October 2026Capabilities
Capabilities
and limitations.
Separate supported workflows from optional features and future infrastructure. The current build is under active testing, and providers can supply different subsets of the Farcaster experience.
Implementation matrix
| Feature | State | Notes |
|---|---|---|
| Canonical domain and gateway contracts | Implemented | Protocol identity and capabilities independent of any presentation stack. |
| Canonical profile, cast and social graph reads | Implemented | Available capabilities depend on the selected read adapter. |
| Read-provider registration and selection | Implemented | A restart/refresh is required to bind a new runtime route. |
| Compatible indexed-read fallback | Opt-in | No unapproved cross-provider reads in strict mode. |
| Local cached views and saved profile search | Supported subset | Only previously discovered and locally available data. |
| Signed write routing and durable outbox | Core implemented | Writer selection and endpoint binding are distinct from reading. |
| Node health checks | Implemented | On-demand API checks, not global uptime or synchronized height guarantees. |
| One-click setup on a personal server | In development | Informational preview; not remote installation or credential collection. |
| Verified independent node + validator setup | Needs integration validation | Operational verification differs from unit and contract tests. |
| Client-origin provenance filtering | Planned | Requires a trustworthy signer-to-application identity mapping. |
Project invariants
Provider-neutral: No single vendor is the canonical data model. Local-first: known cached state can render without waiting for HTTP. Consent-aware: an extra service is not contacted without policy admission. Signer security: private signing material stays outside provider requests. Write correctness: pending writes remain attached to their original selected destination.
Implementation and test references
See the source project's engineering notes and automated tests. Backend contracts and documentation publishing are independent of the application runtime.