<?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>Forem: Dodod Bobovo</title>
    <description>The latest articles on Forem by Dodod Bobovo (@dododbobovo).</description>
    <link>https://forem.com/dododbobovo</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3649470%2Fb6059de0-948b-48a5-a178-a0051868e2bd.jpg</url>
      <title>Forem: Dodod Bobovo</title>
      <link>https://forem.com/dododbobovo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/dododbobovo"/>
    <language>en</language>
    <item>
      <title>I built a "Paranoid" Data Protocol that runs away from server seizure or censorship (Python + Rust)</title>
      <dc:creator>Dodod Bobovo</dc:creator>
      <pubDate>Sat, 06 Dec 2025 17:33:30 +0000</pubDate>
      <link>https://forem.com/dododbobovo/i-built-a-paranoid-data-protocol-that-runs-away-from-server-seizure-or-censorship-python-rust-25on</link>
      <guid>https://forem.com/dododbobovo/i-built-a-paranoid-data-protocol-that-runs-away-from-server-seizure-or-censorship-python-rust-25on</guid>
      <description>&lt;h3&gt;
  
  
  The "Knock on the Door" Problem
&lt;/h3&gt;

&lt;p&gt;We tend to think of decentralized storage (like IPFS) as permanent. But physically, data always sits on someone's hard drive.&lt;br&gt;
If a node operator gets raided, or a data center gets seized, that data is gone (or worse, compromised). Encryption at rest helps, but it doesn't solve the physical availability problem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I asked myself a question:&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Can we make data behave like a living organism that runs away from danger?&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This weekend, I built a Proof-of-Concept to answer that. Meet &lt;strong&gt;WDP (Wanderer Data Preservation)&lt;/strong&gt;.&lt;/p&gt;
&lt;h3&gt;
  
  
  🧬 Biological Survival Strategies in Code
&lt;/h3&gt;

&lt;p&gt;Instead of static replication, WDP uses a "Moving Target Defense" strategy.&lt;br&gt;
Data in this network is ephemeral and acts based on survival instincts. It migrates based on two triggers:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; &lt;strong&gt;Time (TTL):&lt;/strong&gt; Data moves to a new peer automatically every "Epoch" (e.g., 10 minutes) to prevent static analysis.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Threat Detection:&lt;/strong&gt; If a node detects network anomalies, packet loss, or "seizure" patterns in the swarm, it triggers an immediate &lt;strong&gt;emergency migration&lt;/strong&gt; to a safe node and wipes itself.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;It’s like a digital game of "Hot Potato," but cryptographically signed.&lt;/p&gt;
&lt;h3&gt;
  
  
  Under the Hood (Python PoC)
&lt;/h3&gt;

&lt;p&gt;The current implementation uses &lt;strong&gt;Python&lt;/strong&gt; for logic and &lt;strong&gt;Ed25519&lt;/strong&gt; for signing every state transition.&lt;/p&gt;

&lt;p&gt;Here is how the migration logic looks (simplified):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;attempt_migration&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;trigger&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;TTL&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="c1"&gt;# 1. Find a candidate node (or Emergency Peer)
&lt;/span&gt;    &lt;span class="c1"&gt;# If under attack, find the furthest node by latency
&lt;/span&gt;    &lt;span class="n"&gt;target&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;self&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;swarm&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;find_peer&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;strategy&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;trigger&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="c1"&gt;# 2. Sign the payload
&lt;/span&gt;    &lt;span class="n"&gt;signature&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;self&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;signer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sign&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;self&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="c1"&gt;# 3. Transmit &amp;amp; Escape
&lt;/span&gt;    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;target&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;receive&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;self&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;signature&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="n"&gt;self&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;secure_wipe&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="c1"&gt;# &amp;lt;--- The critical part
&lt;/span&gt;        &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Migration success (&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;trigger&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;). I am now empty.&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I also built a "Swarm Simulation" to stress-test this. Even with 30% of nodes randomly dying (simulating active attacks/seizures), the data survived by constantly hopping to safe nodes.&lt;/p&gt;

&lt;h3&gt;
  
  
  🦀 Moving to Rust
&lt;/h3&gt;

&lt;p&gt;Python is great for prototyping, but for a p2p node, we need raw performance and memory safety.&lt;br&gt;
I've started porting the core protocol to &lt;strong&gt;Rust&lt;/strong&gt; (using &lt;code&gt;libp2p&lt;/code&gt; and &lt;code&gt;tokio&lt;/code&gt;).&lt;/p&gt;

&lt;p&gt;The goal is to compile this to WASM so WDP nodes can run directly in browsers, creating an unkillable, serverless storage layer.&lt;/p&gt;

&lt;h3&gt;
  
  
  🤝 I Need Your Roast
&lt;/h3&gt;

&lt;p&gt;This is an experimental concept. I know there are challenges (bandwidth usage, latency, malicious nodes).&lt;br&gt;
I released the code open-source under MIT, and I'm looking for feedback from the community.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is "Migration" a viable alternative to "Replication"?&lt;/li&gt;
&lt;li&gt;How would you handle the "Sybil Attack" in this dynamic topology?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Check out the repo here:&lt;/strong&gt;&lt;br&gt;
👉 &lt;strong&gt;&lt;a href="https://github.com/dododbobovo-commits/wdp" rel="noopener noreferrer"&gt;GitHub: WDP Protocol&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you think this concept is cool (or crazy), drop a star ⭐. It keeps me motivated to finish the Rust port!&lt;/p&gt;

</description>
      <category>python</category>
      <category>rust</category>
      <category>opensource</category>
      <category>security</category>
    </item>
  </channel>
</rss>
