Zero-knowledge proofs (ZK proofs) are cryptographic tools that allow one party to prove a statement is true without revealing the underlying information. Jupiter Meta Labs, a Web3 data company founded in 2021 and headquartered in Hyderabad, India, is using this technology to solve a fundamental problem in market research: enterprises need authentic consumer data, but traditional methods force users to surrender personal information to dozens of databases, each one a potential security breach.

What Problem Are Zero-Knowledge Proofs Solving in Data Collection?

The infrastructure that powers consumer data collection today is broken in three critical ways. First, data is centralized into honeypots controlled by a handful of platforms, making them attractive targets for breaches and resale. Second, privacy and verification are treated as opposites; proving who you are typically means handing over who you are. Third, authentic consumer insight remains inaccessible in emerging markets like India, where bot-farmed survey panels corrupt the data enterprises pay for.

Jupiter Meta Labs built an integrated technology stack to address all three problems simultaneously. The company operates four core products: Hercules (an AI-powered market research platform), Poseidon (an advanced analytics engine), SuperJ (a zero-knowledge-verified consumer network with over 20 million users), and the JMDT blockchain (the settlement and verification layer). Enterprises including Unilever, Kantar, ICICI Prudential, and SBI Mutual Fund already use this ecosystem for consumer research.

How Does the JMDT Blockchain Use Zero-Knowledge Technology?

The JMDT (Jupiter Meta Data Token) blockchain takes a different architectural approach than most Layer 2 (L2) networks. While general-purpose L2 solutions like Polygon, Arbitrum, Optimism, and zkSync focus on scaling financial transactions, JMDT treats identity and privacy as native protocol features.

The blockchain combines several technical choices that are rarely found together in a single system:

• Full EVM Compatibility: Any Solidity smart contract deploys on JMDT without code changes, meaning existing Ethereum developers can build on the network immediately using familiar tools like MetaMask, Hardhat, and Foundry.
• STARK-Based Zero-Knowledge Proofs: JMDT's proof system uses zk-STARKs (Scalable Transparent Arguments of Knowledge), which rely on hash-based cryptography rather than elliptic-curve assumptions. This design eliminates the need for a trusted setup ceremony and provides post-quantum-resistant security guarantees.
• DAG-Based Layer 3 Architecture: Rather than processing transactions sequentially, JMDT's Layer 3 uses a Directed Acyclic Graph that processes transactions in parallel, delivering 5,000 or more transactions per second with near-instant finality and ultra-low fees.
• Native Decentralized Identity: Identity is a first-class protocol primitive, not an application-layer add-on. Users can prove they are over 18, KYC-verified, or within an income bracket cryptographically, on-chain, without revealing their name, document numbers, or underlying personal data.
• On-Device AI Attestation: Small language models run locally on a user's device, and only a zero-knowledge proof of the computation result is committed on-chain. Raw personal data never leaves the phone, inverting the standard cloud-AI model where user data must be uploaded to be processed.

The architecture operates across three distinct planes. At the top, Layer 3 applications connect through the JMDT Gateway, which exposes an Ethereum-compatible JSON-RPC interface alongside the JMDT API and decentralized identity (DID) resolution. Beneath it, the JMDN node network maintains a verifiable append-only ledger over a peer-to-peer gossip network, with DID-based node identity and Merkle-verified FastSync for new nodes. At the base, the JMDT ZK Prover batches state commitments into zero-knowledge proofs and posts them to a rollup contract on Ethereum Layer 1, which acts as the final settlement anchor.

How Are Enterprises Using Zero-Knowledge Proofs for Market Research?

Hercules, the enterprise-facing product built on JMDT's infrastructure, is an AI-powered consumer intelligence platform that lets businesses design surveys in minutes, deploy them to verified respondents, and analyze results through Poseidon, its multilingual AI analytics engine. Poseidon supports 8 or more Indian languages with cultural context, addressing a gap in global research tools that have historically treated emerging markets as an afterthought.

What distinguishes Hercules from conventional survey tools is the panel underneath it. Every respondent is a verified human on the SuperJ network, not an anonymous email address or a click-farm account. In an industry where fraudulent and bot responses are a persistent, expensive problem, cryptographic proof-of-personhood changes the economics: enterprises pay for verified insight, not raw response volume.

Poseidon automates the full analyst workflow. From a single natural-language query, it can produce a 20 to 50 page research-grade report structured around the research brief and exportable in PDF, Excel, and PowerPoint. Under the hood, the engine runs automated cross-tabulations by demographic segment, statistical significance testing, AI-assisted thematic coding of open-ended responses, and AI-generated executive narrative summaries. For tracking studies, it delivers wave-over-wave comparisons with automatic anomaly detection.

Why Is Privacy-Preserving Computation Becoming Critical Infrastructure?

The broader blockchain industry is recognizing that privacy and verification no longer need to be opposites. Zama, a cryptography project focused on fully homomorphic encryption (FHE), recently became available through Revolut, a fintech platform with over 70 million customers, including 15 million who already trade digital assets. This marks a significant moment: privacy technology is moving from crypto-native venues into mainstream financial applications.

FHE allows computation to be performed on encrypted information without first exposing the underlying data. The output remains encrypted until an authorized party decrypts it. In blockchain finance, this could permit a network to validate balances, apply transaction logic, or run risk rules while amounts and positions remain concealed from the public.

The timing is favorable for several reasons. Institutions want the auditability and programmability of tokenized assets, yet few corporate treasurers, funds, or banks want their trading intentions and account-level exposures broadcast in real time. Consumers likewise may accept transparent settlement rules without accepting transparent personal finances. Research into privacy-preserving computation shows why the industry increasingly treats cryptography as product infrastructure rather than academic ornamentation.

However, a listing or availability should not be mistaken for validation of the full technology stack. Retail availability proves that distribution and compliance teams are prepared to support an asset, but it does not prove that FHE applications have achieved high throughput, intuitive key management, or durable demand. Homomorphic operations have historically been computationally expensive, and developers must still decide which operations belong inside encrypted environments and which should remain conventional.

There is also a delicate regulatory question. Privacy that is absolute can conflict with financial-crime controls; transparency that is absolute undermines the point of privacy. The viable middle ground is programmable confidentiality: participants reveal only what a transaction or regulator legitimately requires. A bank might verify that a user passed know-your-customer checks without publishing the identity. A lending protocol might establish that collateral exceeds a threshold without revealing the exact portfolio. An auditor could receive selective access while competitors receive none.

As artificial intelligence becomes more prevalent in financial systems, the case for privacy-preserving computation strengthens. AI agents handling payments, procurement, or portfolio rebalancing will require access to sensitive information. Feeding plaintext account data into autonomous systems creates privacy and cybersecurity exposure. Encrypted computation could allow machine-learning systems to evaluate protected inputs or enforce policies without seeing every underlying field. Yet the combination of AI and privacy must not become a magic phrase that obscures real risks. Model outputs can leak information, permissions can be misconfigured, and compromised endpoints can expose data before encryption or after decryption.

The industry's next phase will be won by teams that can hold competing truths at once: blockchain technology is becoming useful, and therefore more complicated. Modularity redistributes risk rather than eliminating it. A rollup depends on proofs, sequencers, bridges, and data availability. A privacy protocol must reconcile confidentiality with sanctions screening and auditability. Every new abstraction creates another place where trust, governance, and operational discipline matter.