A 1-hour holistic deep dive into Project Tachyon: 🔸Decoupling of the shielded core and payment protocol. 🔸Evolving nullifiers and new double-spend prevention in consensus. 🔸Oblivious synchronization that preserves spend unlinkability. 🔸Two subprotocols: quadratic-residue filters for efficient non-membership checks and subsequence arguments without vector commitments. Watch the full technical breakdown! 🎬

@TachyonZcash @Zcash Could you please tell me who I can contact to freeze or cancel a transaction, or to flag a wallet as fraudulent? My cold wallet was hacked. The police aren't really taking much action so far.

@TachyonZcash Oblivious sync is the underrated line here — the wallet fetches what it needs without revealing which notes are yours. Unlinkability has to hold in how you query, not just in how you sign.

@TachyonZcash Wow everyone's using JubJub

@TachyonZcash Hey @Zcash, you said you would tell us what Jubjub is weeks ago?

@TachyonZcash Hey @Zcash what’s a JubJub??

@TachyonZcash Really lived it

@TachyonZcash tachyon splitting the shielded core from the payment layer is the part most people will skip past. that is the thing that lets the chain scale without giving up privacy

@TachyonZcash I love this... building something on Zcash too, will unveil soon🙂‍↔️

@TachyonZcash ZEC voting proposal is on the way:

@TachyonZcash Good to have the deep dive in one place. The oblivious sync part is what I am most curious about, since wallet syncing is where a lot of privacy quietly leaks today.

@TachyonZcash Wallet sync is where privacy usually leaks in practice, not in the cryptography. Good to see it treated as a first-class problem.

@TachyonZcash 🦓🛡

The oblivious sync piece is the one I'd want every wallet user to understand. Today a light wallet either scans everything itself or leaks hints to a server about which notes are yours. If sync can stay oblivious while spends stay unlinkable, fast mobile wallets stop costing you privacy. Curious how evolving nullifiers change what a node has to store long term.

@TachyonZcash Curious how oblivious sync affects wallet sync times

@TachyonZcash This is so true

@TachyonZcash 💛🛡️

@TachyonZcash awesome

@TachyonZcash A one-hour deep dive laying out nullifiers and PIR this clearly is designer-proof material. Most chains bury protocol changes of this size in a changelog; Zcash is teaching them.

@TachyonZcash does oblivious sync cover light wallets on phones too? that's usually where payments leak and the sync server learns which notes you ask about

Oblivious synchronization is the underrated headline here. Keeping spend unlinkability while a wallet syncs is exactly the gap that makes shielded money feel heavy on a phone. Pair that with evolving nullifiers in consensus and you get privacy that scales with usage instead of fighting it. Will the full talk walk through how subsequence arguments replace vector commitments for lighter proofs on mobile?

@TachyonZcash Question from the merchant side: with oblivious sync, what does a watch-only server need to detect an incoming payment? Today ours holds a viewing key and scans. Does Tachyon change that model, or just make the scan cheaper?

@TachyonZcash Private transactions mean little if wallet syncing exposes your activity.

@TachyonZcash Really solid overview of Tachyon. The oblivious sync + evolving nullifiers approach looks like the right way to finally scale shielded transactions without blowing up state or leaking linkability. Looking forward to the full deep dive. 🌊🏄‍♂️

@TachyonZcash CvbkFXitLDzP5S9XQEyztY2hrthe4XZbhPQQD2BApump ZTRASH