Memo Pruning as HNDL Mitigation — Application-Layer Perspective from ZChat
The recent quantum HNDL discussion and ongoing ZIP-231 memo bundle review raised something worth exploring: memo pruning isn’t just about compliance and storage - it’s an additional layer of protection against mass harvesting before post-quantum note encryption ships.
The reality today:
- Memo encryption uses ECC-based key agreement - not quantum-resistant
- Every memo ciphertext persists on-chain indefinitely - harvestable for future decryption
- This applies to financial metadata and application-layer data like messages
Tachyon / post-quantum note encryption is the long-term answer. But it’s in research, not deployment. Until then, every day that encrypted memos accumulate is another day of harvestable ciphertext.
Pruning as HNDL mitigation:
The HNDL angle strengthens the motivation for age-based pruning beyond compliance and storage efficiency. Data that no longer exists on the network can’t be decrypted regardless of future compute capability. This doesn’t stop adversaries already archiving full blocks - state-level actors are likely doing this. But it reduces the network-wide harvest surface over time, making bulk collection from live nodes progressively harder.
The principle: pruning is an additional layer of protection against mass harvesting.
How ZChat is adapting (research direction, not shipped):
Our job as a messaging app is to work within whatever pruning mechanisms the protocol provides, not dictate them. We’re researching a design that treats pruning as a feature:
-
On-device persistence - message history remains on the user’s device regardless of on-chain pruning. The device is the primary store; blockchain serves as transport.
-
Self-destruct timer per chat - a visible indicator showing when on-chain memo data will be pruned, so users have clear expectations about the on-chain lifecycle of their messages. Similar to ephemeral messaging in Signal/Telegram, but driven by protocol-level data removal rather than app-level deletion.
-
Re-broadcast before device migration - if users need history available for wallet restore on a new device, they can re-broadcast their local archive as self-addressed shielded notes. The new device restores the wallet, syncs, and recovers full conversation history via normal chain scan. After sync, those fresh memos follow their own pruning schedule.
This depends entirely on ZIP-231 memo bundles being accepted and pruning mechanisms being implemented by node developers. We’re researching the direction so ZChat is ready to adapt when the protocol supports it.