Dr Fraudsworth
Metadata-only while remediation remains open.
View disclosureMetadata-only while remediation remains open.
View disclosureProjects with live Solana programs should keep response paths and audit ownership explicit.
View findingsSecurity engineering and research roles are open. Internal tools, API access, and knowledge transfer are part of onboarding.
View teamNeed audit
Intake starts through `@odachq`, moves into a scoped engagement, and closes with a human-written report.
Lab
Solana audits, narrow high-signal review work, and whitehat validation around live protocols.
Compute-unit reduction, instruction-path tightening, and practical performance work around live Solana programs.
Cloned-state reproduction, local validator harnesses, and report-ready proof instead of vague issue lists.
Intake starts through `@odachq`, then moves into a scoped engagement assigned to a responsible engineer.
Payable in SOL upfront, scheduled, delegated to an engineer, and concluded with a human-written report. Performance optimization and CU reduction can be scoped the same way.
Need AuditFindings
Active security finding under responsible disclosure. Public metadata only while remediation remains open.
View disclosure statusClosed writeups will appear here once remediation is complete and publication is technically safe.
Agents
Instruction flow, account binding, token semantics, state machines, deployment wiring, and likely failure paths.
Agents accelerate the work. Humans decide risk ratings, disclosure boundaries, and final technical claims.
`odac.app` is where these agents become a structured Codex-based security harness for Solana teams and whitehats.