Skip to content

Pranav-Talwar/TapProof

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 

Repository files navigation

TapProof

Kill counterfeits with math, not opinions.


The Problem: Security Theater at Scale


The counterfeit economy is a $500B+ problem that runs almost unchecked.

Today, platforms that promise “authentication” (resale marketplaces, brand protection agencies, verification services) still rely heavily on human inspectors reading stitching patterns, materials, and other physical tells.

When technology is used, it often fails at basic security:

1) The “Green Tag” Gap

Major marketplaces often use plastic tags with QR codes.

A QR code is a static image. If someone can photograph it, they can reprint it.
It authenticates the link, not the object.

2) The Static NFC Limit

Many brands deploying NFC today use static chips

Static NFC emits the same data every scan, which means a counterfeiter can clone it quickly with a standard smartphone and a blank tag.

We are fighting a digital problem with analog tools.

The actual technology to make counterfeiting mathematically impossible at scale exists. It's been sitting there. What doesn't exist is a platform that makes it usable outside of six-figure enterprise contracts and 18-month integrations.

That's TapProof.


What This Is

TapProof is authentication infrastructure for physical products — built around NFC chips that produce a unique, non-repeating cryptographic signature on every single tap.

Not a static code. Not a serial number lookup. A rolling one-time proof generated by hardware-secured keys embedded in silicon rated against physical and digital extraction attacks. Every scan produces a different output. Replaying a previous scan fails. Cloning the chip's readable memory fails. Brute-forcing the underlying key would take longer than the sun has left.

A consumer taps a product. In under two seconds: authentic or counterfeit. No app install on Android. No training. No "in our expert opinion." Binary, cryptographic certainty.


Built for How Products Actually Move

Authentication solutions on the market today assume a product sells once, to one buyer, end of story. That's not how the world works anymore. Sneakers flip 4 times before someone wears them. Luxury bags circulate for decades. Bottles of whisky sit in collections and trade hands at auction.

TapProof is designed around the resale lifecycle:

Ownership Transfers — When a product changes hands, the transition is recorded against the tag's live cryptographic state. Not a database entry someone manually updates. A transfer that's anchored to the chip's rolling counter at that exact moment in time.

Chain of Custody — Every scan, every transfer, every verification builds a provenance trail. The tenth owner has the same confidence as the first. The trail is the product's history, not a brand's claim about it.

Cross-Platform — Doesn't matter where the product was originally purchased or which marketplace it's listed on. If it carries a TapProof tag, any phone verifies it anywhere. No walled gardens.

Anomaly Intelligence — Same tag scanned in Vancouver and Shenzhen an hour apart. Counter jumped backwards. Scan velocity that doesn't look human. The system catches the patterns that individual scans can't reveal.


Architecture (Conceptual)

┌────────────────┐         ┌─────────────────┐         ┌──────────────────┐
│   Secure NFC   │── tap ──│  Consumer Phone  │── api ──│   TapProof Core  │
│   Hardware     │         │  (browser-based) │         │                  │
│                │         │                  │         │  ▸ signature     │
│  ▸ hw-secured  │         │  ▸ no app needed │         │    validation    │
│    symmetric   │         │    on android    │         │  ▸ counter state │
│    keys        │         │  ▸ reads NFC URL │         │    tracking      │
│  ▸ rolling     │         │    natively      │         │  ▸ provenance    │
│    counter     │         │                  │         │    engine        │
│  ▸ per-tap     │         │                  │         │  ▸ anomaly       │
│    unique code │         │                  │         │    detection     │
└────────────────┘         └─────────────────┘         └──────────────────┘

The tag doesn't store proof. It generates it. Fresh. Every time. The backend holds the corresponding keys, validates the cryptographic output against the expected state, and makes the call. If anything is off — wrong signature, stale counter, impossible scan pattern — it flags it instantly.

The verification layer, the provisioning pipeline, and the ownership engine are architecturally separated. Compromise in one doesn't cascade to the others.


Why Now

The cost curve crossed. Cryptographic NFC silicon dropped below $0.25/unit at volume. On a $150 sneaker that's 0.17% of retail. On a $2,000 bag it's invisible. The economics stopped being a blocker for anything above ~$30 retail.

Regulatory tailwinds. The EU Digital Product Passport rolls out starting 2027. Every product sold in Europe will need a unique digital identity. The current compliance plan? QR codes. Which counterfeiters will clone on day one. There's a regulation-sized hole waiting for a cryptographic solution to fill it.

Tooling maturity. The open-source ecosystem for secure NFC verification hit production quality in 2024. The primitives are there. What's missing is the product layer — the thing that turns raw crypto libraries into something a brand can actually ship with.


Target Sectors

Phase Market Why It Fits
1 Streetwear, sneakers, resale Highest fake rates, tech-native consumers, culture that already obsesses over proof of authenticity
2 Premium spirits & collectibles High unit values, auction fraud is rampant, buyers willing to pay for certainty
3 Consumer goods under DPP mandate EU compliance deadline creates forced adoption window for textiles, electronics, furniture by 2028-2030

Design Principles

No security through obscurity. The system's strength comes from the cryptography, not from hoping nobody reverse-engineers it. Proven standards. Auditable architecture.

Verification, not identification. Plenty of solutions can tell you a tag's serial number. TapProof tells you whether the tag is real, right now, on this specific scan. Those are different questions.

Consumer-first UX. If it requires an app download, a login, or instructions longer than "tap your phone here," adoption dies. The entire verification flow is browser-based on Android and a lightweight companion on iOS.

Honest about limitations. No NFC system can verify that a product's physical contents match the tag. Tag-to-product binding, tamper evidence, and the "real tag on fake product" problem are addressed through hardware design and multi-factor correlation — not hand-waved away.


Status

🔨  Pre-Alpha  —  Active Development

Currently in pre-coding stage, focusing on architecture and resource dependencies. Targeting a working demo with live tap-to-verify by March 2026.


Contact

Interested in a pilot, a partnership, or just want to talk about why the authentication industry is stuck in 2015?

talwarpranav929@gmail.com


TapProof is an independent project. Not affiliated with NXP Semiconductors or any chip manufacturer. Product and company names referenced are trademarks of their respective owners.

About

Kill counterfeits with math, not opinions.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors