A few days ago, a user got downvoted because he was reposting the same photos in different posts. He was reusing photos, in other words. He tried to justify himself, but my intention isn’t to judge the situation. Rather, I want to share with you that this set off major red flags for me.
I’ve already admitted that I’m a bit disorganized when it comes to organizing my photo folders. If they’re recent, that’s fine. But if I have to dig through my archives (across multiple PCs, external drives, and iCloud), there could be disasters down the road. I don’t practice what I preach. I’m a mess 🤐
It’s happened several times that I’ve had to check past posts to confirm whether I’d already published “that” photo. Especially when I post in communities like Street-Art, Black & White, or Analog (Film) Photog. The time I wasted checking things—and the anxiety of thinking that it would only get worse in the future—was the starting point for me to design this app.
I’m scaling and building it using AI, through Abacus.Ai, according to my needs. That’s how it went with Hive: The Beginner’s Guide, [My] Hive Monitor, and Hive Communities.
💡Snap.Proof — Born from a Simple Question
“Is there a way to tell if a photo has already been published on HIVE?”
HIVE compensates creators for the content they publish. Photos, text, videos—each post can generate rewards. But this dynamic creates a silent problem: posting the same photo twice—whether due to an oversight in the archive, a folder error, or careless reuse of old content—damages the author’s reputation and violates the spirit of the network.
I’m not aware of any simple tool that allows you to check, before posting, whether a photo has already been published. I always had to manually review my history—which is frustrating because it becomes impractical as I post more and more content.
It was from this reality that the idea was born. Problems exist to be solved.
⚙️ How the Tool Works
Snap.Proof doesn't record anything on the blockchain, doesn't write anything, and doesn't require a login. It's purely a reading tool.
The user does three things:
- Uploads the photo they want to verify.
- Enters the @username of the HIVE account to be verified.
- Clicks “Verify Originality.”
From there, the tool takes care of the rest.
🧬 The “fingerprint” of the Image
Comparing two images pixel by pixel would be impractical on a large scale. The solution is to generate a mathematical fingerprint of each image and compare the fingerprints.
Snap.Proof uses two complementary types: SHA-256 (cryptographic hash) — Generates a unique signature based on the exact bytes of the file. Any change to a single bit completely changes the hash. It detects exact copies of the same file.
pHash (Perceptual Hash) — Analyzes the visual content of the image. The algorithm resizes the image to 32×32 pixels, applies a mathematical transform (DCT) to extract the dominant visual frequencies, and generates a 64-bit hash. Two visually similar images produce hashes with a small Hamming distance, even if the file is different (resized, recompressed, or slightly cropped).
Combining the two methods eliminates false negatives: recoded images would pass SHA-256 but would be caught by pHash.
Inside the Process Photo uploaded ↓ Calculate the SHA-256 and pHash of the photo ↓ Query all posts by @username via HIVE’s public API ↓ For each post: extract image URLs → download → calculate hashes ↓ Compare the hashes: SHA-256 matches → Exact Copy pHash distance ≤ 10 → Visually Identical Otherwise → Different image ↓ Result: Original ✅ or Duplicate ⚠️
🎯 Design Decisions
The process wasn't a straight line. There were important decisions along the way.
No “Register / Stamp” tab The original version included the ability to timestamp—to record the photo on the blockchain as proof of authorship. This feature was deliberately removed.
Snap.Proof is a verification tool, not a registration tool. Keeping the focus on a single function makes it simpler, faster, and more accessible.
No login, no wallets No authentication is required. You don’t need to launch Hive Keychain, HiveSigner, or any other wallet. The tool is 100% read-only—it only reads what is already public on the blockchain.
Verification by blocks, not by SSE A technical challenge arose early on: the platform’s reverse proxy would cut off long connections when the account being verified had many posts and images. The solution was to replace continuous streaming (SSE—Server-Sent Events) with batch requests: the client sends a request for one page of posts, receives the result, and moves on to the next page. Each request takes less than 12 seconds—well within the proxy’s limits. The user sees the progress in real time without the connection being cut off.
Fingerprint Always Visible Even when the result is “Original Photo,” Snap.Proof displays the fingerprint (SHA-256) of the uploaded image.
This value is the unique fingerprint of the photo itself—independent of HIVE. It can be saved as personal proof of authorship, compared in the future, or shared as a reference.
💠 The Interface
The design followed the “elegant utilitarian” philosophy: clean, free of visual clutter, with immediate feedback. The app's background features a subtle hexagonal pattern—a visual reference to HIVE and the bees that symbolize the network.
The result clearly distinguishes between two statuses: ✅ Original Photo — No copies found in the verified posts. The SHA-256 fingerprint is displayed.
⚠️ Duplicate Found — The image has already been published. A direct link to the original post on PeakD is displayed.
⏱ Analysis - Wait Time
The wait time depends on the number of posts and photos the user has that we’re analyzing. In my case, with just over 3,000 photos and 375 posts, the wait time is less than 20 seconds.
For a longer-time user—I’ll use as an example someone who’s been on the platform since 2021—sorry @xrayman for using you as a guinea pig—it took about 90 seconds.
But while you wait, you can learn some interesting facts about the history of photography. That way, the analysis becomes less tedious.
🌐 The Impact on HIVE
Snap.Proof solves a real problem with a simple tool. But its impact goes beyond its immediate usefulness.
👉 For creators — It eliminates the anxiety of wondering, “Have I already posted this?” before sharing a photo. (For me, it’s a relief). It protects the reputation of those who create original content and prevents embarrassing situations caused by accidental duplication.
👉 For curators — It provides a quick verification tool when evaluating content. A curator who comes across a suspicious photo can check in seconds whether it has already been published by the same author.
👉 For the network — HIVE rewards original content. Tools that encourage and facilitate the publication of genuinely new content contribute to the overall quality of the network and to trust between creators and curators.
👉 For the ecosystem — Snap.Proof demonstrates that it is possible to build useful tools on top of HIVE without writing to the blockchain, without fees, and without authentication. HIVE, as a public reading infrastructure, is an immense resource that remains largely untapped by tools of this type.
🚀 Prospects for Future Development
Snap.Proof is currently a solid tool for its primary use case: “Have I already posted this photo?” But it has considerable potential for future development.
Phase 2️⃣ — Global Coverage The current version only checks the history of a specified account. A natural next step would be an indexer running in the background 24 hours a day, processing all posts across the entire HIVE and building a database of image fingerprints.
With this indexer, it would be possible to check whether a photograph has been posted by anyone on HIVE—not just on a specific account.
The question would shift from “Have I posted this before?” to “Does this image exist anywhere on HIVE?”, with much greater implications for protecting authorship and detecting plagiarism across different accounts.
Phase 3️⃣ — Cross-Account Verification An extension of Phase 2 would allow for the simultaneous comparison of the histories of multiple accounts—useful for curators who manage portfolios of various creators, or for detecting the reuse of images across different accounts belonging to the same user.
Phase 4️⃣ — Exportable Report A PDF report listing all verified images, along with dates, posts, and status (original / duplicate), would be valuable for authors with a long history who want to conduct a thorough audit of their photo archive on HIVE.
Phase 5️⃣ — Public API A documented public API would allow other applications in the HIVE ecosystem to integrate originality checks directly into their publishing workflows. Imagine @PeakD, @Ecency, or another front-end automatically notifying the author before publishing if the image has already been used.
The verification would become part of the publishing process, rather than a separate tool.
Phase 6️⃣ — Video Support Extending perceptual hash technology to short videos (by comparing representative frames) would make it possible to detect the reuse of audiovisual content, an increasingly common type of duplicate in HIVE.
🤝 An Open Project
Snap.Proof was born from a question and was designed in collaboration with AI, built in an afternoon, and refined over days of real-world testing. It’s not a corporate product—it’s a tool by the community, for the community.
If you have suggestions, find bugs, or want to discuss future developments, the comments section is open.
And if you find the tool useful—use it, share it, and keep publishing original content. That’s what HIVE is all about.
👉 The tool is available at: 🔗 https://hive-snapproof-cryptoreforma.abacusai.app



