Building a Health Data Platform on ZkSync

General
1

Hey zkSync community,

My name is Dave, founder of Amach Health - a protocol that lets people actually own their health data instead of just having “access” to it. We’re live on zkSync Era testnet, and I wanted to introduce what we’re doing and get some feedback from folks who understand the tech.

The Problem I’m Solving

Here’s the situation: I’ve got years of health data - Apple Health, bloodwork, DEXA scans. Months of continuous tracking, all kinds of metrics. Then I go to a doctor and they ask: “So… any health changes?”

They can’t see any of it. Not my sleep trends, not my recovery patterns, not even my bloodwork from three months ago at a different lab. They have a blood pressure cuff and my word.

The data exists. It’s just fragmented across platforms that don’t talk to each other and locked in systems I don’t actually control. When I switch insurance or move cities, I start from zero.

What I’m Building

Amach Health is a patient-owned health data protocol where:

  • You encrypt your data locally (we never see it in plaintext)

  • You store it decentralized (Storj, with zkSync for access control)

  • You grant temporary access to providers (revocable, time-limited)

  • You contribute anonymously to scientific insights (earn tokens for helping others with similar biology)

Why zkSync Era specifically matters:

  1. Privacy by default - ZK proofs let us verify data ownership/authenticity without exposing the actual health data

  2. Access control on-chain - Patient controls who sees what, when, for how long

  3. Cost efficiency - Health data uploads need to be cheap enough for real usage

  4. EVM compatibility - Healthcare systems are conservative; we need familiar tooling

Current Progress

Built:

  • MVP dashboard (Next.js/React)

  • Apple Health XML parser (More devices/platforms to be added)

  • Client-side encryption (wallet-derived keys)

  • Storj integration for decentralized storage

  • Multi-agent AI analysis (Venice.AI integration)

  • zkSync Era testnet deployment

Funded:

  • Venice.AI grant recipient

  • Solo founder (all dev myself so far)

  • Building toward mainnet in ~6 months

Early traction:

  • 10-20 early adpoters/testers (quality over scale)

  • Working MVP with real health data

  • Building in public on Twitter

Why I’m Posting Here

1. Technical validation

Is anyone else building healthcare/medical data on zkSync? I haven’t seen much in this vertical and wondering if there are technical considerations I’m missing specific to health data privacy on L2s.

2. Potential collaboration

Healthcare data + zero-knowledge proofs feels like an underexplored use case. If zkSync Foundation is interested in healthcare as a strategic vertical (similar to how you’re going after RWAs and enterprise), I’d love to explore that.

3. Learning from the community

I’m using:

  • zkSync Era for access control contracts

  • Client-side encryption (wallet-derived keys)

  • Storj for storage (considering IPFS/Arweave)

  • Planning ZK proofs for anonymous data contribution verification

What am I missing? What would you do differently?

The Bigger Vision

Right now, healthcare is fragmented by design because nobody profits from your complete picture except you.

If we can prove that patient-owned + cryptographically verified + zero-knowledge contributions works for 10-20 people first, then 100, then 1000… we change how healthcare data works fundamentally.

Not trying to “disrupt healthcare” with vaporware. Just trying to make it so your doctor can actually see your health data when you want them to.

Questions for This Community

  1. For builders: Anyone working on similar privacy-preserving data protocols on zkSync?

  2. For Foundation: Is healthcare data a vertical zkSync is interested in strategically? Happy to share more about architecture.

  3. For everyone: What would you want from a patient-owned health data protocol if you were using it?

Not asking for funding in this post - genuinely here to learn, share progress, and see if there’s alignment between what I’m building and zkSync’s roadmap.

Technical Details (For the Devs)

Current stack:

  • Frontend: Next.js/React/TypeScript

  • Blockchain: zkSync Era (testnet)

  • Storage: Storj (decentralized, S3-compatible)

  • Encryption: AES-256, wallet-derived keys

  • AI: Venice.AI multi-agent framework

  • Parsing: Streaming XML (handles 1.8GB files)

Considering:

  • zkSNARKs for anonymous data verification

  • Account abstraction for better healthcare UX

  • Potential ZK Stack deployment for private health data chain

Happy to discuss technical implementation details in the replies.

Thanks for reading. Happy to answer questions about the implementation or healthcare data challenges in general.

Dave