TZTZ2AT
Tezos wallet history, portable and social

TZ2AT

TZ2AT gives your Tezos wallet a public, portable history that apps can understand. Claim your wallet repo, hydrate your past activity, and let appviews turn your Tezos life into profiles, feeds, analytics, games, and posts.

No custodyClaim your wallet repoHydrate wallet historyUse appviews
Your wallet activity becomes reusable app datawallet -> history -> repo -> appviews
TZ2AT simple data flow A Tezos wallet has history, TZ2AT converts it into portable records, and appviews use those records. WalletTezos history TZ2ATconnects it Portablerecords Wallet repoowned by you Appsviews + games LIVE ACTIVITYnew wallet events PAST HISTORYhydration worker
For Tezos users

TZ2AT makes your wallet history useful outside block explorers.

You already have a history on Tezos: collects, transfers, sales, bids, contracts, and token ownership. TZ2AT gives that history a portable home so apps can show it, remix it, and help you share it.

1Connect your identity.

Use an AT Protocol identity, such as a Bluesky account, and prove which Tezos wallet is yours. TZ2AT does not custody funds or sign Tezos operations.

2Claim your wallet repo.

Your wallet gets a repo that can hold durable profile, lifecycle, token, and activity records. Your past history can be hydrated in the background.

3Use better appviews.

Apps can show your wallet history, recent token activity, collection context, social post templates, feeds, games, and analytics without making you start over.

Why care?

Your wallet should be more than an address you paste into websites.

Block explorers are great for lookup, but they are not personal spaces. TZ2AT lets Tezos activity become app data attached to a portable identity and wallet repo.

That means a wallet history app, a collector profile, a sale celebration card, or a game can all start from the same trusted record of what happened.

Identity

Use an AT Protocol identity to say "this wallet is mine" without making TZ2AT a wallet.

Wallet repo

A public record space for durable wallet facts, ownership context, and history that apps can read.

Appview

The actual product experience: wallet timelines, collector profiles, market alerts, feeds, games, or social cards.

Tezos indexing

The indexer stays boring on purpose.

The hot path keeps up with the chain. Enrichment and routing happen downstream, so an API hiccup or a busy repo provisioner does not block head capture.

TZ2AT pipeline The indexer feeds an intake tank, then converters, hot storage, PDS repos, warm archive, and appviews. Indexerhead capture Intake tankpressure buffer ConverterAT records PDS treeentity repos S3 archivewarm storage
For builders

One stream, many products.

TZ2AT owns replay, provenance, graph anchors, and deterministic Tezos-to-record conversion. Your AppView owns ranking, user experience, culture, and product logic.

Use the firehose.

Subscribe to wss://tz2at.xyz/firehose for live JSON records or to the ATProto sync firehose for native repo events your own PDS/AppView can retain.

Follow the grammar.

Events are verbs. Wallets, contracts, tokens, marketplaces, currencies, platforms, and chains are nouns. TZ2AT stores verbs in the repos for the nouns they describe.

Preserve provenance.

Raw chain observations stay separate from OBJKT enrichment and other semantic context, so apps know what kind of truth they are reading.

Record families

Neutral records first. Interpretation later.

store.tz2at.block · store.tz2at.xtz.flow · store.tz2at.fa2.transfer · store.tz2at.contract.call · store.tz2at.account.activity · store.tz2at.marketplace.collect · store.tz2at.bigmap.update · store.tz2at.raw.observation · store.tz2at.contract.objktProfile

Next steps

Start with your wallet.

The quickest way to understand TZ2AT is to try the wallet appview: connect an AT Protocol identity, claim a Tezos wallet repo, hydrate history, then see what apps can do with it.