Economic logic10.87 units
Loss shift reproduced between equal participants in a local state-transition test.
Private, evidence-first security research
Reproduce.
Prove. Patch.
Fixed-scope security analysis for smart contracts, cryptographic protocols, APIs, and backend code. A credible finding—or a defensible false-positive verdict—in three days.
No mainnet testingNo public disclosureNo production funds
Anonymized evidence
Cryptographic proof0 witnesses
Verifier acceptance reproduced without the secret witness, then closed by a tested fix.
Known-issue triage$10k sim.
High-impact router behavior reproduced, then responsibly discarded after prior disclosure was found.
Figures are sanitized from private local reproductions. No target, repository, or vulnerability detail is disclosed.
Method / 01
Evidence before adjectives.
Severity is the conclusion, not the starting point. Every engagement is built around an exact revision, a falsifiable claim, and a test a second reviewer can run.
Reproduce
Pin the exact revision, isolate the preconditions, and turn a suspicion into a deterministic local test.
Prove
Quantify the concrete impact, eliminate false positives, and preserve the evidence needed for review.
Patch
Deliver the smallest defensible remediation and exercise it with a regression test.
Scope / 02
Built for the finding that will not fit in a code-review comment.
Best for a narrow, high-consequence question: an invariant that may fail, a verifier that may accept too much, or a value flow that deserves a complete reproduction before disclosure.
01Smart-contract economics
02Cryptographic protocols
03API and backend security
04Exploit reproduction
05Known-issue and duplicate triage
Deliverable / 03
A review package, not a dramatic screenshot.
The output is private, compact, and designed to survive technical scrutiny—from first reproduction through the fixed regression test.
- Exact commit and scope
- Root-cause analysis
- Executable PoC when feasible
- Impact and severity rationale
- Minimal remediation patch
- Regression-test evidence
- SHA-256 delivery checksums
- One revision round
Private brief / 04
Bring one precise security question.
Describe the suspected behavior and the repository surface. Do not paste secrets, credentials, private keys, or live exploit material. A reference number is issued immediately.