<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: id-close</title>
    <description>The latest articles on DEV Community by id-close (@id-close).</description>
    <link>https://dev.to/id-close</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4043866%2F86227e10-e1c2-442c-8f6d-89eb96091431.png</url>
      <title>DEV Community: id-close</title>
      <link>https://dev.to/id-close</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/id-close"/>
    <language>en</language>
    <item>
      <title>Building a Zero-Knowledge &amp; Zero-Trust Encrypted Chat with Rust &amp; WebAssembly</title>
      <dc:creator>id-close</dc:creator>
      <pubDate>Thu, 23 Jul 2026 13:08:54 +0000</pubDate>
      <link>https://dev.to/id-close/building-a-zero-knowledge-zero-trust-encrypted-chat-with-rust-webassembly-1lej</link>
      <guid>https://dev.to/id-close/building-a-zero-knowledge-zero-trust-encrypted-chat-with-rust-webassembly-1lej</guid>
      <description>&lt;p&gt;Hi everyone,&lt;/p&gt;

&lt;p&gt;I’ve been working on a privacy-first web application called &lt;strong&gt;ID-CLOSE&lt;/strong&gt; (v2.0.0). The goal is to provide a fully secure, zero-knowledge communication channel without requiring phone numbers, emails, or personal identification.&lt;/p&gt;

&lt;h3&gt;
  
  
  🛡️ How it Works &amp;amp; Security Architecture:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Client-Side Encryption:&lt;/strong&gt; All encryption/decryption happens directly in the browser using Rust compiled to WebAssembly (WASM) with AES-256-GCM.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Zero-Knowledge Server:&lt;/strong&gt; The server acts purely as a blind relay pipe (&lt;code&gt;/dev/null&lt;/code&gt; logging, no history retention). It only sees encrypted ciphertexts and never holds the private keys.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tor Network Native:&lt;/strong&gt; Deployed directly on the Tor network to ensure server identity obfuscation and end-to-end anonymity.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I’m sharing this with the community to get feedback on the cryptographic approach, architecture, and overall user experience.&lt;/p&gt;

&lt;p&gt;🔗 &lt;strong&gt;Try it on Tor (Onion Service):&lt;/strong&gt;&lt;br&gt;
&lt;a href="http://idcloseng647yjjnijaxhjlgn7vtthvucmqluknln7g2h76ezd72x2ad.onion/" rel="noopener noreferrer"&gt;http://idcloseng647yjjnijaxhjlgn7vtthvucmqluknln7g2h76ezd72x2ad.onion/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Note: You need Tor Browser to access the link above).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Feedback and technical insights are highly appreciated!&lt;/p&gt;

</description>
      <category>security</category>
      <category>rust</category>
      <category>webassembly</category>
      <category>privacy</category>
    </item>
  </channel>
</rss>
