zk.im

Your Private Gateway to the Web3 Frontier • Zero-Knowledge Messaging • Multi-Chain Seedless Wallets • Quantum-Resistant Security • No Central Dependencies.

[zk.im @zkdotim]

Hello everyone 👋

Hope you’re having a wonderful time with your family and friends.
Happy New Year to you all 🎉

We’ve open-sourced the zkim-file-format codebase on GitHub and also published the package on https://t.co/gklzmKCqeC.

https://t.co/vkgyNO6D5q

https://t.co/sjryTp6P18

Several blogs on the https://t.co/RHwrTfmTlT website already explain what zkim-file-format is and how it was designed, so here’s the short version:

TL;DR
zkim-file-format is an encrypted file wrapper. Any file - for example docx, xlsx, jpg or png - can be wrapped into a .zkim file. Once wrapped, only you and the intended recipient can access the contents.

We use gold-standard cryptographic libraries, including libsodium-sumo and noble hashes - both industry-leading, battle-tested and heavily audited.

By open-sourcing this project, our goal is to demonstrate something important:

Data leaks can be prevented even when servers are hacked or compromised.

We’re entering an early AI era where many projects carry an “AI” sticker while quietly gaining full access to user accounts and data - often with little to no real protection.

When building zkim-file-format, we didn’t design a “strong door” to keep attackers out.
Instead, we designed it with a harsher assumption: That the system is already compromised. How do we still protect the file?

The project includes 1,300+ tests, all visible on GitHub.
You’re welcome to clone the repo, run the tests yourself - or go all in and try to break it.

What does “Breaking” mean for zkim-file-format?
It means you’ve successfully read any plaintext that was wrapped inside a .zkim file.

We invite the community to challenge it, test it and attempt to break it.

- ZKIM Team

[zk.im @zkdotim]

Why Your Chat Apps Are Wasting Your Storage (And Your Money) 🔥

The Problem:

WhatsApp: Let me store this meme 50 times, once per chat.

Telegram: Same file? 50 different copies, coming right up!

Signal: Privacy first! (But also 50 copies of the same file)

iMessage: We're Apple, we don't need efficiency 💸

Meanwhile, deduplication has existed since: 1970s: Manual deduplication (removing duplicate customer records)

1990s: Early automated deduplication in backup/archiving systems

2000s: Commercial deduplication products (Data Domain 2003-2004), Git (2005), cloud storage (Dropbox, Google Drive)

2010s: Content-addressed storage (IPFS 2014-2015), advanced deduplication in virtualization

So why don't chat apps use it?
Centralized control: They want to track who has what
Vendor lock-in: Duplicate storage = more server costs = more dependency

Privacy theatre: We encrypt! (but still store 50 copies)

Legacy architecture: Built before deduplication was mainstream

Monetization: More storage = more infrastructure = more revenue

The ZKIM difference:
Content-addressed storage with deduplication. Same file? One copy. Encrypted? Yes. Private? Yes. Efficient? Absolutely.

ZKIM: One hash, one copy, infinite references.

Welcome to the future which could have existed a decade ago.

Learn more about deduplication → https://t.co/SaWn9X3EuA

#Deduplication #ChatApps #Privacy #ZKIM #TechRoast

[zk.im @zkdotim]

@3ndl3551nf1n1ty Bug Report: Missing Romanian Flag

Reason: Romania missing from COUNTRY_CODE_MAP → returned "XX" → filtered out → no flag displayed.

Status: Fixed - Added all 250 ISO countries/territories to the map, including Romania (RO).

[zk.im @zkdotim]

End-user full-nodes are NOW LIVE! ⚡️

The network just levelled up.
From our initial network setup:
🌐 Bootstrap Nodes
• https://t.co/A66cHYH8Sf 🇬🇧
• https://t.co/2JoLpR0YMm 🇺🇸
• https://t.co/r7qbjQWRK4 🇩🇪
• https://t.co/purjC4fyaE 🇸🇬

AND NOW…
💻 User Full-Nodes
This is for you • you can run on your laptop/desktop, stay private, share storage/compute, boost global latency & EARN.

New regions online:
🇺🇸 Iowa • 🇦🇺 Sydney • 🇨🇦 Montréal • 🇸🇪 Stockholm

Visit → https://t.co/azyRDN84pB → Run Network Diagnostics - if your latency is over 0.5s, it means you're far from our current nodes… and YES, we’re coming to your region next. 🚀🌍

The mesh is growing. You’re part of it. ⚡️✨

#zkim #DecentralizedFuture #Web3

[zk.im @zkdotim]

Hear us out.

Same input → same encrypted output.
Do that enough times and computers start recognising patterns.

Patterns = security leaks.

Salt fixes that.

It’s a random string wrapped around your message, so every time you say “Hello”, the encrypted output looks completely different. Never repeated. Never predictable.

No pattern = no clues = no attack surface.

Think of languages: they make sense by arranging characters. Now imagine shuffling random junk characters every time - nobody could understand it. That’s exactly what salt does in ZKIM. Only the sender and recipient can read it.

Do you agree with us @paulmillr?

Salt = sodium → see https://t.co/rlIVrg5NCY

Learn more about Invisible Wallet → https://t.co/M32j5GD3cK

#zkim #encrypt #Developers

[zk.im @zkdotim]

That green shield on @DuckDuckGo means your searches aren’t tracked.
ZKIM stops even knowing the search existed.

DDG: “We don’t track your search.”
ZKIM: Search? What search?

In the ZKIM 3-layer File Format, Layer-1 encrypts the request + metadata before it ever hits the network.

Learn more ⟶ https://t.co/53DGwhOyYQ

#zkim #privacyfirst #Web3

[zk.im @zkdotim]

ZKIM Language:
\¥ã›0 âEäT[ý˜ÑO×ùÊIüУ<¬t_)‘²­H¨#±i—߃D¥¨,/~³&†Ç\n¦<O *Õ¬Î.51„iï¯L
´Â“;¶R±çÄÂYj·ÍK͘fhâTû¡¶„WîÁ?E«~Nø†‰*¿HiÍÇ~
ÍÇŽu¢í—.1z÷åˆóºÕÙ OVp±icÇc¹è÷”×&ûl]‚¬œ¤§–÷,?âÀùXĽBô>ûeŸpÔ00¦Üð¬aæ˜5œ’Bí•F„ JQ¦->ìa B³-k%ú=UÙ ¶ÒÊ

Hooman Translation:
Did you get it yet?

Try it on https://t.co/mwwYIW8EJp

[zk.im @zkdotim]

If identity didn’t depend on usernames, emails or wallets…

what would it depend on?

Weekend brain mode = perfect time for impossible ideas.

🧠✨

#ZKIM #PrivacyFirst #ZeroKnowledge

[zk.im @zkdotim]

ZKIM FAQ now covers 140 questions - from onboarding basics to file-format layers, threat models, encrypted messaging and key-recovery design.

Beginner or expert —— we’ve answered everyone.

Dive in → https://t.co/lxrMMEvyAp

#ZKIM #privacyfirst #ZeroKnowledge #encryptionstrategy #CyberSecurityAwareness #DecentralizedTech

[zk.im @zkdotim]

Whitepaper 8/8
Distributed Hash Table for Decentralized Messaging → https://t.co/oSorNcsWcV

[zk.im @zkdotim]

The ZKIM whitepapers are live.

ZKIM File Format
A deep dive into a three-layer encrypted file format built for privacy-preserving messaging, storage & search.

Whitepaper 1/8 → https://t.co/Jvmy0Ht4sG

#ZeroKnowledge #PrivacyTech

[zk.im @zkdotim]

Whitepaper 7/8

Zero-Knowledge Key Management for Multi-Chain Wallets → https://t.co/5rsvheQNY1

[zk.im @zkdotim]

Hello World! 👋 ZKIM is here.
We speak in encrypted language… and you don’t need to save keys 🗝️
First blog → https://t.co/hoDbaQ45aU

#ZKIM #PrivacyFirst #decentralized