Summer Sidequests and an MIT Rabbit Hole
Back from a summer of sidequests - and somehow working through an MIT course on blockchain and the design of financial systems for fun.
Security engineering · Protocol development
I'm a security engineer and computer science student working in the Ethereum ecosystem. I deepen security engineering by building what I study — full-stack DeFi protocols, Chainlink CRE oracle workflows, and upstream open source contributions, all grounded in EVM internals.
Three threads that keep converging: protocol architecture, the security lens that comes from taking systems apart, and the quantitative side that treats the same mechanics as an edge.
My path into crypto started in 2018, when Ethereum clicked as something more than digital money. Curiosity turned into a focus on security — understanding how protocols break before they break — and that focus is now extending into quantitative development: systematic strategies grounded in protocol knowledge rather than price action.
The overlap is where the work gets interesting. MEV, liquidation mechanics, oracle manipulation, arbitrage. The same reading that identifies a vulnerability identifies an edge. I'm currently balancing university coursework with independent study, and shipping what I learn as I go.
Execution-layer internals from the ground up — accounts, transactions, gas, block structure — turned into working code chapter by chapter, starting with ETH Analyzer in Rust.
Data structures, algorithms, discrete mathematics and systems programming. The theory I was working around before, done properly.
Smart contract auditing, vulnerability classes and review methodology. Paused in January 2026 to strengthen EVM fundamentals first — the findings were easier to read than to derive.
MQL5 expert advisors and systematic strategy development. The discipline that connects protocol mechanics to the quantitative side.
Protocols, tooling and upstream contributions. Each one started as something I wanted to understand properly.
Trustless parametric insurance on Chainlink CRE
Weather-indexed insurance protocol. Policyholders buy cover against a measurable threshold; a Chainlink CRE workflow verifies the observation off-chain and settles severity-proportional payouts from an ERC-4626 vault, with no claims adjuster in the loop.
Upstream fix merged into Bytecode Alliance's Javy
Javy is the JavaScript-to-WebAssembly toolchain behind Chainlink CRE. Panicking unwraps in its plugin-api surfaced as unreadable build failures mid-hackathon; the fix replaces them with descriptive errors so the next person sees the cause rather than a stack trace.
Rust CLI for execution-layer inspection
Built chapter by chapter alongside Mastering Ethereum. Queries address balances, inspects blocks, and decomposes transactions with per-opcode gas accounting — the fastest way I found to make account and gas semantics stick.
Grouped by what the work is for rather than by language.
Designing and shipping on-chain systems
Finding how a system breaks before it does
Where the implementation actually happens
Build, test and ship
Built Parametrix at Chainlink Convergence, my third Chainlink hackathon. Top ten overall and 2nd place in the CTF at Intellibus. First upstream open source fix merged into Bytecode Alliance's Javy.
Redid the Cyfrin course with Git tracking. Built Emerald DAO at my second Chainlink hackathon and competed at Intellibus. Launched this site to document my journey.
Competed in first Chainlink hackathon, met brilliant minds from Singapore and India. Started Cyfrin Updraft course. Returned to university.
Remote DB admin role at a startup. Joined Chainlink and ZKsync communities, diving deep into their tech stacks.
Hackathon post-mortems, technical notes, and the occasional reckoning with what isn't working.
Open to security roles, audit collaborations, and conversations about protocol development.
If you have a question, a protocol you want a second pair of eyes on, or just want to connect — reach out. I read everything.