Overview

TZ2AT is a Tezos-to-AT Protocol relay. It turns Tezos chain activity and selected marketplace context into ATProto records that appviews, feed generators, wallets, games, analytics tools, and community services can consume without running their own chain indexer.

TZ2AT stores facts, relationships, and projections. It does not decide what those facts mean socially. Downstream appviews are expected to query the PDS tree, subscribe to firehoses, and derive user-facing views from the records they care about.

Event Grammar And Repo Shape

Blockchain event records are statements. They are normally the raw material appviews use to extract context: who acted, what they acted on, what action happened, and which parameters make the action meaningful.

• Nouns: identity-centered subjects and objects such as wallets, contracts, tokens, marketplaces, currencies, platforms, and chains. These are the who and what of the statement.
• Verbs: actions such as transfers, sales, offers, listings, curation adds, swaps, bids, wallet claims, and hydrations. These become event records.
• Parameters: amounts, prices, token IDs, timestamps, operation hashes, source systems, block levels, and other details that qualify the noun-verb relationship.

TZ2AT is structured around that grammar. Nouns become repos categorized by type, or stable records inside the repo that owns them. Verbs are stored as event records in the repos for the nouns they describe. The structure itself carries context and helps downstream appviews recreate the semantic map without reverse-engineering every relationship from a flat feed.

Example: a marketplace sale is the verb. The buyer wallet, seller wallet, token, token contract, marketplace, currency, and chain are nouns. The price, amount, block, operation hash, and source provenance are parameters. TZ2AT stores the event where those noun repos can use it and links the nouns so appviews can traverse the statement.

Ingestion Model

The rolling Tezos indexer is priority one. It follows the Octez head and should not be slowed down by historical repair, wallet hydration, OBJKT enrichment, appview queries, or conversion backlogs.

• Rolling head path: live Octez RPC block ingestion, checkpointed as octez-main.
• Gap repair path: if the rolling checkpoint is behind by at least two blocks, TZ2AT skips to head and starts a detached skipped-block worker.
• Wallet hydration path: appviews or users can request historic wallet data from TzKT without disturbing live head ingestion.
• OBJKT enrichment path: a separate worker consumes only selected OBJKT streams and converts useful rows into token, marketplace, group, and graph artifacts.
• Entity repo path: missing repos are registered in a priority queue. More pending writes for the same repo raise its priority.

The default entity historian writes permanent lifecycle anchors for wallet and contract repos instead of replaying all old events into every entity repo. It records genesis and last-seen boundaries, adds lightweight OBJKT profile context when available, and leaves full event hydration to explicit appview/user requests or maintenance mode.

Operational rule: if a worker can fall behind, it must fall behind alone. The rolling indexer must remain concerned with current head, not with proving that every background job caught up first.

Available PDSs

Handle repos are deterministic. For example, a Tezos wallet becomes a slug under wallets.tz2at.store, while a FA2 contract becomes a slug under contracts.tz2at.store. Appviews should treat these repos as source-indexed public fact stores and semantic anchors for the nouns in Tezos statements.

Record Types

Canonical Chain And Marketplace Events

Semantic Profiles, Tokens, And Edges

Identity And Projections

OBJKT Enrichment

OBJKT is a second ingestion route, not a replacement for the rolling Tezos indexer. TZ2AT uses OBJKT streams to add marketplace and token context that is hard to derive from raw chain events alone.

Hot OBJKT streams

• token_stream for token identity and metadata context.
• event_stream for OBJKT event rows that can be paired to chain operations.
• Listing, active listing, sale, offer, auction, and open-edition streams for market state.
• fa_stream, marketplace_contract_stream, and currency_stream for contract, venue, and currency context.
• referral_stream for referral/gamification records with social value.
• Filtered project and curation virtual streams derived from OBJKT gallery streams.
• Filtered ACTZ exhibition streams for selected ACTZ gallery exhibitions.

Broad streams intentionally skipped

TZ2AT does not hot-subscribe to unrestricted holder, creator, attribute, royalty, rarity, generic gallery, operator, or TzD streams. Those are too broad for hot ingestion and belong behind scoped hydration or appview-specific requests.

Wallets And Hydration

Users connect to an appview with any AT Protocol identity, then prove control of Tezos wallets. TZ2AT creates or discovers wallet repos under wallets.tz2at.store and writes verifiable wallet-link records. Users choose whether matching records remain retrievable from TZ2AT, are copied to their personal PDS, or both.

When an appview needs historic wallet data, it should wake a background hydration worker. That worker polls TzKT and feeds the resulting records into the same converter/storage/firehose path as normal ingestion, without slowing the rolling indexer.

Lifecycle anchors are eviction-proof records. Wallet and contract repos can keep fixed genesis and last-seen lifecycle records plus a fixed objkt profile record even when ordinary hot event copies age out.

Public API

const ws = new WebSocket("wss://tz2at.xyz/firehose");

Operational Rules

• The rolling indexer must start from current head and stay at head.
• Backfill, hydration, OBJKT enrichment, entity repo provisioning, and archive movement are separate workers.
• The default entity historian is lifecycle-only. Full historic replay requires explicit maintenance mode or appview/user hydration.
• Hot storage should keep as much useful fresh data as disk permits. Retention should be tuned from observed growth, not guessed during an incident.
• OBJKT ingestion must be selective. Broad streams should fail closed unless a scoped worker is deliberately introduced.
• Records should be cross-indexed into the PDS tree by noun category so appviews can query the repo that matches the thing they are displaying.

Manual version: current live architecture as of 2026-05-28.