Dossier

Pranshu Jain

aka pranshu0x

ZeroLend Team Member — Engineering / Operations


Photographs

LinkedIn profile photo — Pranshu Jain
LinkedIn profile photo — Pranshu Jain

Charges


What this defendant knew

As a ZeroLend team member identified via LinkedIn (handle pranshu0x), Jain 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. The "0x" handle suffix suggests a Web3/developer identity, raising the possibility of engineering-level access to the vulnerable code.


Intent indicators


Public identity traces


Prosecution's theory

Pranshu Jain's culpability depends on the specificity of his role and activity period. 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 Jain held an engineering role with knowledge of the PT-LBTC oracle vulnerability or the insolvent state, his culpability escalates to co-conspirator. The "0x" handle suggests developer-level involvement, which if confirmed via GitHub commit history would elevate his grade. 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

Pranshu Jain's LinkedIn profile (linkedin.com/in/pranshu0x) establishes his affiliation with the ZeroLend team. The "0x" handle convention is typical of Web3 developers, suggesting possible engineering-level access to the vulnerable smart contracts. 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.

🔗 View source →

LinkedIn profile photo verification

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

📁 team/pranshu/linkedin-photo.jpg

GitHub address extraction and commit authorship

Extraction of commit authorship from ZeroLend GitHub repositories. Cross-referencing the pranshu0x 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 Jain participated in official channels or developer 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. Jain's inclusion in this matrix establishes his position within the team hierarchy and his connections to other defendants.

📁 team/forensic-identity-matrix.json