TxnProof: Privacy-Preserving Financial Transaction verification platform.

[ronykris]

Summary:
Studies show that around 61% of consumers are concerned about their financial data being shared without their consent​ (RestorePrivacy). Additionally, email-based transactions are particularly vulnerable, with 92% of malware delivered via email and phishing attacks accounting for more than 80% of reported security incidents​ (GitHub)​ (GitHub).
TxnProof is a platform designed to address critical privacy concerns in financial transactions. Using zkEmail and zero-knowledge proofs (ZKPs) built on Aztec's Noir, the platform will enable users to securely prove their financial activities without disclosing sensitive information. The platform ensures financial data remains private, secure, and verifiable on the blockchain, making it a powerful tool for modern financial systems.

Methodology:
We are looking at building not just an integration but an entire mvp that demonstrates this concept end to end. While our primary focus is to integrate zkemail, but we will also have other pieces of software work in tandem to build the entire system.

The basic premise of this product is to ensure the humongous data generated by financial instruments and institutions typically gets unnoticed and on the contrary could get reused with malicious intent. The platform therefore intends to put this data to use and validate txns. Thereby, bridging a huge gap in the ecosystem between traditional and web3 ecosystem.

Below is a sample user flow we have been thinking about :

1. Users sign up via zkemail and authenticate securely.
2. User receives an email notification about a txn. The txn can be any of the following:
   a. Amount transfer between two or more parties
   b. Notification of funds received or sent
3. User can either upload this email to the platform or fwd it to the platforms service ID.
4. Upon receiving the email content, zkEmail generates a zero-knowledge proof of it.
5. The proof is submitted to the contract. The contract verifies the proof and records the txn on chain and mints an erc721 token.

Outlined below is the high level design of the solution:

Login and sign up: implement a sign up and login mechanism via zkemail where user supplies only his/her email Id. Details of the implementation are here

Inbox monitoring service: this will be a service that will monitor the platform's inbox for emails received. Upon receiving an email it will trigger the Regex service.

ZK Regex: this module will parse the email content, extract the relevant details and send it to the proof generation module.

Proover: as the name suggests, this module will generate the proof of the email using zkEmail and submit it for processing to the contract.

Contract: Aztec is our chosen chain and the contract will be deployed there. It will verify / validate the proof and store it on chain along with a record of the txn. This will also trigger a mint functionality on the chain.

Mint: the mint contract will burn a token (erc721 preferably) for every record (comprising of txn and proof) written on chain. The token will be an indication of the financial txn going fwd.

Indexing service: We intend to integrate the graph indexing service to enable faster querying of records and transactions.

We are looking at building this dapp using the tech stack as outlined below on a microservices based architecture. Below is the proposed stack and tools:

Frontend : Nextjs / vite
Backend : nodejs, express js
Blockchain : Aztec
ZK proofs : Noir to create zk circuits
Indexer : The graph
Containers: docker
Cloud compute : gcloud

Timeline and Deliverables:
Month 1:
Wk1: finalise the architecture, user stories and tasks
Wk2: user registration and authentication system including frontend + smart contract to record user registration and login
Wk3: frontend to upload email + inbox monitoring service + use zk-regex to write email parser and field extracter
Wk4: generate secure, private zkp of email to create call data

Month 2:
Wk5: write smart contract to record proof + txn details on chain and mint erc721 token
Wk6 : integrate contract interaction with frontend + build the indexing service
Wk7: create a profile view of user with integration with the indexer to list tokens and records
Wk8, 9 : test, fix bugs and create documentation

Team

Ayush: a full stack developer with several wins. He has been working in web3 ecosystem from last two years. He has won filecoin track prizes in ethIndia. Worked in Mina ecosystem also. He takes pride in the role of a Core Member of the UniDAO program led by the Devfolio Team. (Github: https://github.com/ayush4345)

Ritvik: Experienced smart contract developer with skills in Solidity, Noir, Cairo and Dojo framework for writing safe and secure smart contracts. (Github: https://github.com/raghav-rama)

Nikhil: Ace designer and frontend developer with expertise in scaling protocols and product management. He has 4+ years of web3 industry experience on chains like Ethereum, Solana, and various L2s. He is an ambassador at Arbitrum and several crypto exchanges. GitHub.

Saurabh: Web3 and blockchain developer relations professional with 5+ years of experience. Skilled in developer outreach, technical writing, and community management. GitHub.

Krish: Full stack, smart contract and zkp developer with 5+ years of experience on EVM chains, Mina, and Aztec. Built zk proof dapps on evm chains using solidity and zokrates and noir on Aztec. Currently lead developer of Ottp, an open collaboration protocol on Base mainnet with 1k+ SDK downloads. GitHub.

[ronykris]

This is a duplicate of 5766. Hence, closing.