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

Memo

The memo database lets a wallet privately fetch follow-up payment memos (tag => ciphertext) for an established sender–recipient pair, scoped per Tachyon epoch.

PropertyValue
ScopeOne Tachyon epoch (scope_id = epoch)
SourceOn-chain vMemoTachyon envelopes, kind 0x01 (spec §5)
Entry layoutkey16 (16) || ciphertext (128) = 144 bytes
Slots per row56 (floor(8192 / 144)), target load 34 (~139,264 entries per tachyon-4k8 table)
Protocol stringtachyon-memo-pir-v1
Query magicTMQ1
Mount/memo/v1 (legacy alias /v1/memo)
Default retention64 epochs

On-chain envelope (TPM1)

Each Tachyon bundle carries an opaque vMemoTachyon blob. The provisional payment-protocol envelope (spec §5.1) packs 1 to 16 entries:

envelope    = "TPM1" || entry_count (u8, 1..=16) || entry*
entry       = kind (u8) || tag (32) || body
  • kind = 0x01 (follow-up memo): ciphertext (128 bytes) — indexed in memo.
  • kind = 0x02 (first-contact): kem_ciphertext (1088) || ciphertext (128) — indexed in first-contact.
  • kind = 0x03 (wallet state): len (u16 LE) || ciphertext (len <= 1024) — counted and ignored.

Invalid or truncated envelopes are skipped whole and counted (tachyon_memo_envelopes_invalid_total); they never halt ingestion.

Placement & duplicate tags

Entries are keyed by key16 = tag[0..16] (all-zero key16 is rejected):

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

Because tags are visible in the mempool, anyone can publish a colliding entry for the same tag. The publisher keeps every entry for a tag in deterministic ordinal order (height, tx_index, entry_index) (spec §5.3), and the wallet authenticates candidates by AEAD decryption.

Wire protocol & operations