<?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: Henry Odinakachukwu</title>
    <description>The latest articles on DEV Community by Henry Odinakachukwu (@henry_odinakachukwu_c5987).</description>
    <link>https://dev.to/henry_odinakachukwu_c5987</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%2F3671161%2Fe5b350c3-3823-4c6a-9e9d-e153df4f44fd.png</url>
      <title>DEV Community: Henry Odinakachukwu</title>
      <link>https://dev.to/henry_odinakachukwu_c5987</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/henry_odinakachukwu_c5987"/>
    <language>en</language>
    <item>
      <title>Fixing an Incorrect Example Output</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Mon, 12 Jan 2026 13:23:26 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/fixing-an-incorrect-example-output-2ij0</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/fixing-an-incorrect-example-output-2ij0</guid>
      <description>&lt;p&gt;I noticed the sample output in the docs didn’t match what actually happens when you run the code.&lt;br&gt;
I submitted a PR updating the example so developers aren’t confused.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Smart Contracts on Midnight: Programming Visibility, Not Storage</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Mon, 12 Jan 2026 13:08:54 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/smart-contracts-on-midnight-programming-visibility-not-storage-3h3n</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/smart-contracts-on-midnight-programming-visibility-not-storage-3h3n</guid>
      <description>&lt;p&gt;Traditional smart contracts focus on state storage. Midnight smart contracts focus on visibility rules.&lt;br&gt;
This article explores:&lt;br&gt;
How developers define what is public vs private&lt;br&gt;
How contract logic interacts with proofs&lt;br&gt;
Why this model scales better for sensitive applications&lt;br&gt;
Differences from EVM-based contracts&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>blockchain</category>
      <category>privacy</category>
      <category>web3</category>
    </item>
    <item>
      <title>What Zero-Knowledge Proofs Mean for Developers (Without the Math)</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Mon, 12 Jan 2026 13:07:55 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/what-zero-knowledge-proofs-mean-for-developers-without-the-math-5aol</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/what-zero-knowledge-proofs-mean-for-developers-without-the-math-5aol</guid>
      <description>&lt;p&gt;Zero-knowledge proofs sound complex, but the idea is simple:&lt;br&gt;
👉 You prove something is true without showing why.&lt;br&gt;
In this guide, we explain:&lt;br&gt;
Zero-knowledge using real-life examples&lt;br&gt;
How Midnight handles proofs for you&lt;br&gt;
What developers actually need to care about (and what they don’t)&lt;br&gt;
This tutorial is perfect if ZK feels intimidating.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Aligning Examples With Current Behavior</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Thu, 08 Jan 2026 23:02:25 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/aligning-examples-with-current-behavior-3267</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/aligning-examples-with-current-behavior-3267</guid>
      <description>&lt;p&gt;The docs described behavior that has since changed in the codebase.&lt;br&gt;
I submitted a PR updating the explanation to match how Midnight actually works today.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Improving Clarity Around Privacy Defaults</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Sun, 28 Dec 2025 23:44:21 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/improving-clarity-around-privacy-defaults-34ef</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/improving-clarity-around-privacy-defaults-34ef</guid>
      <description>&lt;p&gt;A section wasn’t clear about what is private by default and what must be explicitly revealed.&lt;br&gt;
I submitted a PR clarifying this so developers don’t make wrong assumptions.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Improving Error Message Guidance</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Sat, 27 Dec 2025 23:42:19 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/improving-error-message-guidance-3604</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/improving-error-message-guidance-3604</guid>
      <description>&lt;p&gt;I noticed the docs mentioned an error but didn’t explain how to fix it.&lt;br&gt;
I submitted a PR adding a simple “what this means and how to resolve it” note for beginners.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Correcting a Wrong File Name in a Tutorial</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Fri, 26 Dec 2025 22:06:24 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/correcting-a-wrong-file-name-in-a-tutorial-813</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/correcting-a-wrong-file-name-in-a-tutorial-813</guid>
      <description>&lt;p&gt;One tutorial mentioned a file name that doesn’t actually exist in the GitHub repo.&lt;br&gt;
I submitted a PR fixing the file name so beginners can follow the steps without getting confused&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>documentation</category>
      <category>github</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Correcting a Misleading Description of a Feature</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Thu, 25 Dec 2025 18:45:24 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/correcting-a-misleading-description-of-a-feature-1gd6</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/correcting-a-misleading-description-of-a-feature-1gd6</guid>
      <description>&lt;p&gt;I noticed one feature description suggested something happened automatically when it actually required a developer setting.&lt;br&gt;
I submitted a PR fixing the wording so expectations match how the feature really works.&lt;/p&gt;

</description>
      <category>ux</category>
      <category>writing</category>
      <category>documentation</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Correcting a Small Logic Error in an Example</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Wed, 24 Dec 2025 20:04:07 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/correcting-a-small-logic-error-in-an-example-1945</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/correcting-a-small-logic-error-in-an-example-1945</guid>
      <description>&lt;p&gt;I spotted a simple logic mistake in one of the example smart contracts on GitHub.&lt;br&gt;
I submitted a PR fixing the logic and added a short comment explaining the change, so others don’t copy an incorrect pattern.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Correcting File Paths in the Setup Guide</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Tue, 23 Dec 2025 21:33:23 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/correcting-file-paths-in-the-setup-guide-4ckd</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/correcting-file-paths-in-the-setup-guide-4ckd</guid>
      <description>&lt;p&gt;While setting up the project locally, I noticed the file paths in the docs were slightly off.&lt;br&gt;
I submitted a PR fixing them so developers can follow the setup steps without running into errors.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Fixing a Misleading Diagram Description</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Mon, 22 Dec 2025 21:39:48 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/fixing-a-misleading-diagram-description-482k</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/fixing-a-misleading-diagram-description-482k</guid>
      <description>&lt;p&gt;One of the diagrams in the docs looked right, but the text explaining it was slightly misleading.&lt;br&gt;
I submitted a PR updating the description so the diagram and explanation match, making it easier to follow for beginners.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>documentation</category>
      <category>opensource</category>
    </item>
    <item>
      <title>Updating Contract Deployment Steps</title>
      <dc:creator>Henry Odinakachukwu</dc:creator>
      <pubDate>Sun, 21 Dec 2025 23:08:25 +0000</pubDate>
      <link>https://dev.to/henry_odinakachukwu_c5987/updating-contract-deployment-steps-1d8j</link>
      <guid>https://dev.to/henry_odinakachukwu_c5987/updating-contract-deployment-steps-1d8j</guid>
      <description>&lt;p&gt;I found that the deployment steps in one tutorial didn’t fully match the current devnet process.&lt;br&gt;
I submitted a PR correcting the commands and adding a short note to help first-time users deploy without running into errors.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
