User guide

Your Tezos history, ready for apps.

TZ2AT helps you connect a Tezos wallet to an AT Protocol identity, claim a portable wallet repo, hydrate your wallet history, and use appviews that can understand your Tezos activity.

What it is How records work What you need Claim flow Hydration What apps can do Privacy Help

What TZ2AT is

TZ2AT is not a wallet and it does not custody funds. It is a Tezos data relay that turns wallet activity, token movement, marketplace events, and selected OBJKT context into portable AT Protocol records.

For a user, the main idea is simple: your wallet can have a repo. Apps can read that repo and build better experiences without forcing you to rebuild your wallet history in every new product.

How records work

A blockchain event is like a sentence. Someone did something to or with something else. TZ2AT keeps that shape instead of flattening everything into one pile.

Nouns are the who and what.

Wallets, contracts, tokens, marketplaces, currencies, platforms, and chains are durable subjects. TZ2AT gives those subjects repos or repo-local records.

Verbs are what happened.

Transfers, sales, offers, listings, curation adds, and wallet claims are actions. TZ2AT stores them as event records inside the relevant noun repos.

Parameters explain the action.

Amounts, token IDs, prices, timestamps, source systems, and operation hashes are the details that let apps recreate the context later.

This is why a wallet repo matters. It is not just storage; it is a semantic home for statements about that wallet, linked outward to the contracts, tokens, and marketplaces in the same map.

What you need

A Tezos wallet

Any wallet address you control. TZ2AT asks you to prove ownership, not hand over keys.

An AT Protocol identity

A Bluesky account works. It gives apps a social identity to attach to the wallet claim.

A reason to hydrate

Hydration pulls older wallet history so appviews can show timelines, analytics, token ownership, and social cards.

How claiming works

1Open the demo.

Start with Demo Appviews. The first demo walks through wallet repo ownership and history hydration.

2Sign in with ATProto.

Use your AT Protocol identity so TZ2AT knows which DID is asking to claim the wallet repo.

3Prove the wallet is yours.

Connect your Tezos wallet and complete the minimum ownership proof. TZ2AT does not ask for spending permission.

After the claim, TZ2AT can keep publishing core records about that wallet while your app ownership gives you a user-facing claim over the repo experience.

Hydrating history

Fresh events arrive through the rolling indexer. Older wallet activity is pulled by a background worker when a user or appview requests it. That worker uses historic sources such as TzKT and feeds the results into the same conversion path as live data.

This matters because your appview can ask for history without making the live indexer fall behind. Live chain capture stays priority one; your wallet history fills in beside it.

What apps can do after that

Show a wallet timeline with transfers, collects, sales, bids, and contract activity.
Show token analytics, recent activity around owned tokens, and collection or project context.
Create preformatted Bluesky posts for purchases, sales, listings, rare supply moments, and collection activity.
Use wallet history as game input, feed ranking context, profile badges, or community reputation signals.

Privacy and control

Tezos chain data is public, but your app experience should still be understandable. TZ2AT records provenance so apps can explain where a fact came from, and wallet claims are meant to be explicit user actions.

You should expect wallet-linked public facts to be readable by appviews. You should not expect TZ2AT to move funds, sign transactions, or become the owner of your wallet.

Help and next steps

Start with the demo, then read the FAQ if you want more plain-language background. Builders should use the Builder Manual and developer overview.

User guide version: current live user flow as of 2026-05-28.