deadshotryker

Identity confirmation — Enamakel = Deadshotryker

User-provided dox and cross-platform correlation confirming that deadshotryker and Steven Enamakel are the same person. The "two founders" narrative was a fabrication — Enamakel created the deadshotryker persona to give the appearance of a team while retaining sole control. Evidence includes commit timestamp correlation, writing style analysis, and operational overlap demonstrating both identities were managed by the same person.

📁 team/forensic-identity-matrix.json

Discord server ownership

Deadshotryker held Discord server ownership (ID 1130285489379880990) with full administrative privileges including role management, channel creation/deletion, message pinning, and member banning. As server owner, deadshotryker controlled the narrative environment — every moderation action, every deleted message, every banned user traces back to his permissions.

📁 discord_analysis/04-server-governance-audit.md

Discord — Master prosecution synthesis

Comprehensive analysis of all Discord activity during the 16-month concealment period. Deadshotryker's role as server owner made him directly responsible for the coordinated narrative management, systematic deflection of user complaints, and suppression of exploit-related discussions documented in this report.

📁 discord_analysis/00-MASTER-PROSECUTION-SYNTHESIS.md

Discord — Official channels analysis

Every public statement, announcement, and team communication made in official Discord channels while deadshotryker was server owner. Documents the complete absence of any acknowledgment of the Feb 2025 exploit — a deliberate omission that could only occur with the server owner's knowledge and approval.

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

Discord — Community channels discourse

User-facing channel analysis showing how deadshotryker's moderation team deflected victim inquiries. When users asked about missing funds, they were directed to "contact moderators privately" — a gatekeeping strategy that prevented public discussion and maintained the fiction of operational status.

📁 discord_analysis/02-community-channels-discourse.md

GitHub commit cessation timeline

Deadshotryker's GitHub activity ceased in September 2025 — five months before the Feb 2026 shutdown announcement. This timeline demonstrates that development work stopped while the deposit UI remained open and users continued depositing funds into an insolvent protocol. The cessation was not publicly announced — users were kept in the dark.

📁 team/forensic-github-addresses.json

Deployer wallet tracing

Shared evidence with Steven Enamakel: the deployer wallet hierarchy that deadshotryker controlled, demonstrating complete technical dominion over all protocol deployments. The same wallets that deployed contracts also held admin keys that deadshotryker used to manage the protocol.

📁 team/forensic-deployer-tracing.json

Admin role and ACL control

Complete ACLManager role assignment log across all chains. Deadshotryker's control of DEFAULT_ADMIN_ROLE meant every security parameter — pause, freeze, borrow cap, collateral factor — was under his direct control. The absence of any protective action after the exploit was a choice made by deadshotryker.

📁 team/forensic-admin-role-events.json

97% token concentration

Shared evidence with Steven Enamakel: deadshotryker's wallet 0x9FA7...429e held 97% of ZERO supply. The public Discord statements about "community governance" and "decentralization" were knowingly false — deadshotryker held and controlled nearly the entire token supply.

📁 team/forensic-zero-price-team-dumps.json

Discord — Server governance audit

Detailed audit of Discord role hierarchy, permission structures, moderation logs, and audit trail. All moderation actions during the concealment period trace back to deadshotryker's owner account or moderators operating under his authority. Documents systematic evidence suppression.

📁 discord_analysis/04-server-governance-audit.md

June 2026 wind-down admissions (Discord transcript)

After 16 months of silence, Deadshot Ryker returned to the ZeroLend Discord (Jun 24-25, 2026) under sustained victim pressure and made a series of legally significant admissions: (1) "Most funds have been withdrawn. We're now going to start force liquidating borrowers" — confirming control over protocol funds; (2) "We have been genuinely delayed. We've moved onto other things hence couldn't get time to sort this out" — admitting the team prioritized TinyHumans over returning victim funds; (3) Base LBTC "partial refund 1-2 weeks from now... 30% roughly (estimated), 30-40%" — re-using the same "1-2 weeks" timeline promised since Feb 2026; (4) confirming victims must self-recover illiquid mstETH+ZRC across the Zircuit bridge and EigenPie withdrawal queue with no on-site balance shown. These statements establish ongoing control, consciousness of the obligation, and willful prioritization of the next scheme over victim restitution.

📁 discord_archive/zerolend_export/

Real-owner correction — Enamakel (Discord, Jun 2026)

During the June 2026 wind-down, a community member publicly corrected another user who tagged Deadshot Ryker: "you tagging the wrong acc, real owner is @enamakel but he won't reply anymore here." This is contemporaneous, third-party corroboration — from inside the victim community — of the deadshotryker = Enamakel identity link, reinforcing that the operational persona and the true owner are the same controlling individual.

📁 team/forensic-identity-matrix.json

Concurrent suppression on TinyHumans Discord

While managing the ZeroLend wind-down, the team is actively banning users on the new TinyHumans/OpenHuman Discord who mention ZeroLend or ask about their stuck withdrawals. This demonstrates a continuing pattern of narrative control and evidence suppression carried directly from the old project into the new one — the same playbook, the same operator.

📁 discord_analysis/04-server-governance-audit.md

Illiquid partial-refund mechanism (June 2026)

The "refunds" are not the promised compensation. Victims received airdropped mstETH + ZRC (the collateral the debt was concentrated in) with no balance shown on the ZeroLend site, and were instructed to bridge it via the official Zircuit bridge and unstake through EigenPie/Magpie — a multi-step, multi-day process on a chain whose liquidity has "gone to almost 0." One depositor's 17 ETH stated balance returned as ~8 ETH, dismissed as "overinflated because of the interest rates." This documents that the recovery is partial, illiquid, and engineered to minimize actual restitution.

📁 forensics/linea-zero-compensation-investigation.json

Threat in response to good-faith off-ramp (June 2026)

After a public, good-faith off-ramp was offered — make the victims as whole as possible and the matter would be closed — Deadshot Ryker made direct contact and responded with a threat rather than a commitment to refund. This conduct is itself evidence: a party acting in good faith negotiates a timeline; a party intent on stalling intimidates. The threat, combined with the recycled "1-2 weeks" promises, establishes that the refund representations are a delay tactic. The threat has been preserved and is included in the formal report to the Dubai eCrime unit.

📁 discord_archive/zerolend_export/

Formal Dubai eCrime unit report (in preparation)

Following the threat and continued stalling, counsel is drafting a formal report to the Dubai eCrime unit (UAE) with the complete evidentiary record: on-chain trails, identity attribution (Enamakel = Deadshotryker, Dubai-based), the Binance KYC lead to capstack.eth, the documented June 2026 wind-down admissions, the illiquid partial-refund mechanism, and the threat itself. Parallel notice is being prepared for law enforcement in the United States, Canada, and India. The matter has moved from publication to prosecution.

📁 team/forensic-money-trail-priority-summary.json

June 27 2026 official announcement — two-faced posture

One day after privately threatening a complainant who had offered a good-faith refund off-ramp, Deadshot Ryker posted a polished, lawyer-flavoured wind-down announcement in the ZeroLend Discord #announcements channel: "majority of assets have now been withdrawn," oracle issues "resolved" on Ethereum/zkSync/Zircuit, and a tidy Jun 27 / Jul 2 / Jul 10 schedule. The announcement carries the same escape hatch as every prior promise ("these dates are our current target timeline and may be adjusted") and pre-assigns blame to "factors outside of the protocol's direct control" (oracle infra, RPC degradation, "chain instability... Zircuit especially"). Threatening a complainant in private while publishing a blameless schedule in public is one strategy with two faces — the announcement is evidence of presentation, not good faith. Preserved verbatim with delivery-tracking schedule.

📁 discord_archive/zerolend_export/announcement-2026-06-27.md