Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Tachygram

The tachygram database lets a wallet privately verify two things per epoch: inclusion of a note commitment (returning the block height and stamp ordinal needed to fetch its creation stamp) and exclusion of a nullifier (proving a note remains unspent over the covered heights).

PropertyValue
ScopeOne Tachyon epoch (scope_id = epoch)
Sourcetachygrams[] of every on-chain proof stamp; pointer stamps contribute nothing (spec §8.2)
Entry layouttg (32) || blk_height (u32 LE) || stamp_ordinal (u32 LE) = 40 bytes
Slots per row204 (floor(8192 / 40)), target load 124 (~507,904 entries per tachyon-4k8 table)
Protocol stringtachyon-tachygram-pir-v1
Query magicTGQ1
Mount/tachygram/v1 (legacy alias /v1/tachygram)
Default retention64 epochs

Placement & uniqueness

Keys are full 32-byte tachygrams (not truncated):

h      = SHA-256("tachyon-pir/tachygram/v1/place\0" || genesis_hash(32) || epoch(u64 LE) || seed(u32 LE) || tg(32))
bucket = u32_le(h[4..8]) mod n_buckets
row    = u32_le(h[0..4]) mod rows

Consensus requires tachygrams to be unique within a block and across the current and preceding epoch. Within a row, tachygrams are sorted in strictly ascending byte order. An all-zero or duplicate tachygram within an epoch is treated as an integrity fault (spec §8.3).

Lookup semantics

  • Hit: returns (blk_height, stamp_ordinal), where stamp_ordinal is the zero-based index of the proof stamp among proof stamps in blk_height.
  • Miss: returns a canonical row that does not contain tg, proving absence across the epoch heights covered by the map's verified anchor (spec §8.4).

Tachygram lookups are private hints; spendability is ultimately enforced by the wallet's proof and consensus.

Wire protocol & operations