Dossier

Dhruv P

ZeroLend Team Member — Operations / Engineering


Photographs

LinkedIn profile photo — Dhruv P
LinkedIn profile photo — Dhruv P

Charges


What this defendant knew

As a ZeroLend team member identified via LinkedIn, Dhruv P possessed knowledge of: (1) his affiliation with the ZeroLend project during the fraud period, (2) depending on his specific role, the protocol's operational or technical status, (3) the team's coordinated silence during the 16-month concealment period. His exact role and activity period require further corroboration via GitHub commit history, Discord participation, or internal team communications.


Intent indicators


Public identity traces


Prosecution's theory

Dhruv P's culpability depends on the specificity of his role and activity period, both of which require further corroboration. The prosecution's theory: any team member who remained affiliated with ZeroLend during the concealment period — when the deposit UI stayed open, users kept losing funds, and the team publicly promised compensation it never delivered — participated in the conspiracy by maintaining the fiction of an operational, legitimate project. If Dhruv held an engineering role with knowledge of the vulnerability or the insolvent state, his culpability escalates to co-conspirator. If his role was operational or administrative, he remains an accessory for failing to disclose known fraud. His LinkedIn affiliation creates an estoppel — he cannot now claim ignorance while maintaining the ZeroLend association on his professional profile.


Incriminating exhibits


Proofs & Evidence Collection

The following evidentiary items are preserved in this repository. Each item is timestamped, verifiable on public block explorers or web archives, and subpoena-ready for law enforcement. File paths reference the local evidence archive; URLs link to live public sources.

LinkedIn profile — ZeroLend team affiliation

Dhruv P's LinkedIn profile (linkedin.com/in/dhruv-p-6665a5364) establishes his affiliation with the ZeroLend team. This creates insider status: as an identified team member, he was positioned to know the protocol's true operational and financial status during the fraud period. The specific role (engineering, operations, or other) and activity period require further corroboration via GitHub, Discord, or internal communications.

🔗 View source →

LinkedIn profile photo verification

LinkedIn profile photo of Dhruv P extracted via public LinkedIn profile. Confirms human identity behind the ZeroLend team affiliation. Preserved for law enforcement identification and cross-referencing with any GitHub commit authorship, Discord participation, or internal team communications.

📁 team/dhruv/linkedin-photo.jpg

GitHub address extraction and commit authorship

Extraction of commit authorship from ZeroLend GitHub repositories. Cross-referencing Dhruv's identity with commit metadata can establish his specific technical contributions, activity period, and whether he had access to the vulnerable code — determining whether his culpability is accessory or co-conspirator level.

📁 team/forensic-github-addresses.json

Discord — team participation during concealment

Analysis of ZeroLend Discord server activity. If Dhruv participated in official channels or team discussions during the 16-month concealment period, his messages would establish his knowledge of the exploit and the coordinated silence strategy.

📁 discord_analysis/01-official-channels-analysis.md

Identity matrix — team member correlation

Cross-platform identity correlation linking team members across LinkedIn, GitHub, Discord, and on-chain addresses. Dhruv's inclusion in this matrix establishes his position within the team hierarchy and his connections to other defendants.

📁 team/forensic-identity-matrix.json