Dossier

deadshotryker

aka Deadshot Ryker, confirmed alias of Steven Enamakel per user-provided dox

Operational Lead, Discord Administrator, Public Face During Concealment


Photographs

Deadshotryker / Steven Enamakel
Deadshotryker / Steven Enamakel
Deadshotryker / Steven Enamakel
Deadshotryker / Steven Enamakel
Deadshotryker / Steven Enamakel
Deadshotryker / Steven Enamakel

Charges


What this defendant knew

Deadshotryker operated as the primary Discord administrator during the entire 16-month concealment period. He possessed direct knowledge of: (1) the February 2025 exploit (confirmed by on-chain evidence + silence), (2) user inquiries received in support tickets demanding answers, (3) the decision to keep the deposit UI operational while insolvent, (4) the team's coordinated silence strategy.


Intent indicators


Public identity traces


Prosecution's theory

Deadshotryker was the public face of the conspiracy. While Enamakel operated technically, deadshotryker managed the deception narrative. The prosecution will show he coordinated Discord moderators to: (1) deflect user inquiries about missing funds, (2) blame "UI issues" and "maintenance" rather than disclose the exploit, (3) actively suppress community investigations. His role was essential — without narrative control, users would have withdrawn before the team could complete extraction. His identity (confirmed by user-provided dox as Steven Enamakel) makes him the single most culpable individual: he was both the technical architect AND the deception manager.


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.

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