
Nanivolt
The Trust Layer For Digital Files
Hey everyone, I’m Nana Agyei Mensah. I’m a solo developer, and today I am finally launching my project, Nanivolt (https://nanivolt.com), because of a devastating financial fraud that hit my own family.
My mother runs an independent small business. A few months ago, scammers intercepted a legitimate vendor PDF invoice she was waiting for, silently altered the bank account numbers, and forwarded it to her email inbox. Because digital document manipulation is completely invisible to the human eye, she had no idea she was walking into a trap. She paid the bill, and her hard-earned life savings vanished instantly.
That night broke me, but it also made me realize a massive security flaw in the tech world: traditional software like Adobe or DocuSign tracks signatures, but they do absolutely nothing to protect raw text data once a file leaves your device. Anyone with a basic PDF editor can alter your contract, invoice, or certificate in seconds.
So, I spent my nights building Nanivolt to create an airtight, cryptographic shield for files.
How it works under the hood:
When you drop a file into Nanivolt, our engine instantly computes a unique SHA-256 digital fingerprint. If an external party modifies even a single comma, digit, or character later on, the file verification fails immediately. The system runs a granular, word-level side-by-side text diff engine, highlighting deleted text in red and unauthorized additions in green so you instantly catch fraud.
I am live in the comments right now to answer any technical questions about our backend hashing layers, database structure, or text diff compilation. I would love your honest feedback, stress tests, and thoughts!
About
ey everyone, I'm Nana Agyei Mensah. I have spent my recent nights building Nanivolt (https://nanivolt.com) out of a deeply personal place. My mother runs an independent small business, and scammers intercepted a digital

5 Comments
The interesting part is that detecting a change and establishing trust aren't quite the same problem.
A hash can show that two files differ. But in a fraud scenario, the consequential question is which version the recipient had reason to trust in the first place.
That feels like an important distinction for what Nanivolt is ultimately promising.
That’s helpful context. I’d be interested in understanding more about how you’re thinking about this from the user side, rather than unpacking it further in the thread.
What’s the best email to reach you on?
you can reach me on nanivolt1@gmail
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.