Summary: Frequency is worth cataloging not as just another social chain or DSNP-branded Layer 1, but as a data-and-authorship substrate that splits identity, delegated publishing, schema-governed data, and fee abstraction into unusually explicit layers. Its core mechanism stack is Message Source Accounts (MSAs) that persist authorship separately from rotating control keys, public delegations that let approved Providers act for coinless users, immutable on-chain schemas that define protocol data formats, and a Capacity system that lets Providers pre-fund recurring publishing through staked FRQCY rather than per-transaction token spend. Provider Boosting then adds a second stake path where users signal support for Providers and indirectly provision more Capacity. That makes Frequency a useful comparison point for decentralized social protocols, shared data registries, and app-sponsored walletless onboarding because the main control surfaces are not just social graph onchain claims. They are Provider admission, public delegation visibility, schema evolution through new IDs rather than mutation, off-chain batch publication formats, and the choice to meter high-volume application activity through renewable stake-derived Capacity instead of raw token fees.
What it does:
Runs a purpose-built Layer 1 for DSNP-style social and identity data with a split between ordered Messages and MSA-indexed Stateful Storage
Gives each user a Message Source Account (MSA) as the durable authorship object, separate from the control keys that may change over time
Lets users delegate specific schema-scoped publishing rights to Providers so applications can operate for coinless users without requiring every action to be token-funded or individually signed onchain
Uses immutable on-chain Schemas plus on-chain or IPFS-backed payload locations, with Parquet favored for batched off-chain Messages and Avro favored for more compact on-chain storage
Uses Capacity Staking so Providers can stake FRQCY for a renewable daily spending allowance on eligible transactions, plus Provider Boosting so users can stake behind Providers and earn FRQCY rewards while signaling support
Keeps delegation creation and removal public and unilaterally revocable, preserving verifiable authorship and making Provider behavior legible at the application layer
Key claims:
The most reusable analytical split is Frequency’s separation of authorship, application control, and fee payment. MSAs anchor authorship, Providers handle app-facing operations, and Capacity abstracts recurring fee spend away from end users.
Frequency’s delegation model is more specific than generic gas sponsorship. Delegations are mutual-consent, schema-scoped, public, and revocable, which makes application authority legible rather than fully opaque.
The schema system matters because Frequency treats protocol data as structured public infrastructure. Immutable schema IDs force versioning through new registrations instead of silent mutation, which is a real governance and compatibility boundary.
Message Batching is another important control surface. Frequency explicitly pushes high-volume social-style data toward off-chain Parquet files on IPFS with on-chain pointers, reducing block-space pressure while preserving verifiable authorship and ordering anchors.
Capacity is not just staking with a new name. It is a non-transferable, renewable, time-bounded fee budget for Providers, designed to lower publishing volatility while keeping spam tied to staked capital and thaw periods.
Provider Boosting adds a distinct reputation-and-capacity layer: users stake behind Providers, the chain mints user rewards, and Providers gain extra Capacity plus a public support signal without directly paying supporters themselves.
Governance and admission still matter materially in the current design. Mainnet Provider registration currently requires approval by the Frequency Council, so the low-friction user model still sits on top of a curated Provider set.
Frequency clears the corpus bar because it makes social-data infrastructure legible as durable authorship + delegated application authority + immutable schemas + stake-derived publishing capacity, rather than one generic decentralized social story.
Whitepaper: Frequency has an official docs-hosted whitepaper plus detailed mechanism pages. The main primary-source notes for this pass are in ../whitepapers/frequency-primary-sources-2026-05-15.md.