Skip to main content
The following tables are created in Postgres DB where data from the Hubs are stored:

chain_events

All onchain events received from the hub event stream are stored in this table. These events represent any onchain action including registrations, transfers, signer additions/removals, storage rents, etc. Events are never deleted (i.e. this table is append-only).

fids

Stores all registered FIDs on the Farcaster network.

signers

Stores all registered account keys (signers).

username_proofs

Stores all username proofs that have been seen. This includes proofs that are no longer valid, which are soft-deleted via the deleted_at column. When querying usernames, you probably want to query the fnames table directly, rather than this table.

fnames

Stores all usernames that are currently registered. Note that in the case a username is deregistered, the row is soft-deleted via the deleted_at column until a new username is registered for the given FID.

messages

All Farcaster messages retrieved from the hub are stored in this table. Messages are never deleted, only soft-deleted ( i.e. marked as deleted but not actually removed from the DB).

casts

Represents a cast authored by a user.

reactions

Represents a user reacting (liking or recasting) content. Represents a link between two FIDs (e.g. a follow, subscription, etc.)

verifications

Represents a user verifying something on the network. Currently, the only verification is proving ownership of an Ethereum wallet address.

user_data

Represents data associated with a user (e.g. profile photo, bio, username, etc.)

storage_allocations

Stores how many units of storage each FID has purchased, and when it expires.