Verify the founder
Cross-check the same founder identity on LinkedIn and GitHub.
Open LinkedIn ↗Founder, product, and public proof
About Proof of Audits
Proof of Audits is a founder-led Web3 security product. This page connects the person building it, the public organization, the working product, and the evidence records visitors can inspect.
Why Proof of Audits exists
A smart contract audit proves what was reviewed at a point in time. It does not automatically prove that the same code is live now, that later upgrades were covered, or that control and exit paths remain unchanged.
Proof of Audits connects audit scope, deployed bytecode, implementation addresses, control roles, user exit paths, and later changes inside one inspectable record. Each public result separates observed evidence from unresolved gaps. It is proof of a review process, not a guarantee that a protocol is safe.
Founder and current core team
MK
MK Veerendra Vamshi
Founder and product builder
Veerendra founded Proof of Audits and leads its product and engineering work. His public GitHub profile identifies his work in DApp development, blockchain development, and smart contract auditing. His LinkedIn profile provides a separate public professional identity that visitors can verify directly.
Public team disclosure
MK Veerendra Vamshi is the current publicly listed core team member. Proof of Audits does not display invented employees, advisors, customer logos, or credentials.
Follow the public verification chain
Inspect the organization
Review the public Proof of Audits organization and its source activity.
Open GitHub organization ↗Use the live product
Submit a chain and contract address to the public contract proof checker.
Check a contract →Inspect a real record
See exact Aave V4 addresses, bytecode hashes, sources, and open gaps.
Open evidence record →What we stand behind
- Proof over promises. Public claims trace to addresses, hashes, reports, records, or named public sources.
- Evidence and limits together. A record states what was observed, what was not proven, and what evidence is still needed.
- No custody. Proof of Audits never needs a seed phrase, private key, or token approval to inspect public evidence.
- No safety guarantees. Verification can reduce uncertainty within a defined scope. It cannot certify that a protocol is safe or free from vulnerabilities.
Operating identity and contact
Proof of Audits is the public operating name used across this website, product, communications, and public organization profiles. Formal contracting and billing details are provided directly during an engagement or institutional review.
Check the methodology, safety statement, and terms, then test the product yourself. Every important claim should remain open to inspection.