Building C8DOC: A decentralized way to verify invoices and document authenticity
Hi everyone
I've been building C8DOC, an open-source decentralized document format focused on proving document authenticity.
One use case I'm exploring is invoice verification.
Instead of trusting a PDF alone, C8DOC lets anyone verify:
✅ The invoice hasn't been modified
✅ The original creator
✅ Cryptographic proof of authenticity
✅ Public verification without relying on a single database
The goal is to help reduce invoice fraud, forged documents, and ownership disputes while keeping verification transparent.
I'm still improving the project and would love feedback from founders, accountants, finance teams, and developers.
My questions:
Would your company use decentralized invoice verification?
What would stop you from adopting it?
Which feature would make it valuable for your workflow?
I'd really appreciate your honest feedback.
Comments (6)
c8doc.com
make you first decentralized invoices,word document,code file,image,audio,video,audio.
"Nothings is exposed but still hold your ownership"
Good to see you exploring specific use cases, Hari! To answer your questions: invoice fraud is a real problem, especially for small businesses that don't have the resources to verify everything manually. What would stop me from adopting it? Honestly, if it adds steps to my current workflow. If I have to do something extra every time I send or receive an invoice, it would need to be really seamless. The verification part is valuable, but the adoption barrier for most small teams is convenience. If you can make it invisible, like it just happens in the background, that would be great.
Thanks, Olga! That's really valuable feedback.
I completely agree—if verification creates extra work, most small businesses won't adopt it. My goal with C8DOC is to make verification happen in the background, with little to no change to existing workflows. Users shouldn't have to think about security every time they send or receive an invoice.
Your point about convenience is something I'll keep at the center as I continue building. Thanks again for taking the time to share your thoughts!
This is interesting. I don't issue invoices but if I had to I would want it to work with just one click of a button, or even be automatically applied by the invoicing software that I use. If I receive one, I would want my software to just automatically detect that this invoice is legit without me doing anything... So I see it as part of the accounting or invoicing software that I use.
C8DOC makes invoice verification just **one click away**.
Simply create your invoice in the C8DOC format on our website. You can also add your **decentralized company stamp** by clicking the **"Add Stamp"** option.
Once you're done, download the invoice as a PDF. Anyone can verify it instantly using the **Verifier** section.
No matter who checks your C8DOC invoice, they can confirm that it is authentic and belongs to your company. If even a single detail in the invoice is modified, C8DOC will detect it and mark the document as **tampered**.
Olga's point about invisibility is the one I keep relearning building FounderFlow too. The feature people ask for first is never the one that gets used daily, it is whichever one asks the least of them. For invoice verification specifically, I would guess the trust moment is not when you build it, it is the first time someone gets burned by a forged invoice and remembers your tool existed. Founders rarely adopt a safety net before they have felt the fall.
Sign in to comment or upvote.