Singapore-Lion

Security researcher focused on protocol logic, adversarial edge cases, and reproducible findings.

Research Style

I prefer technically grounded findings over broad claims, and reproducible behavior over speculation.

1. Confirmed behavior over assumption
   I try to validate what the system actually does before arguing why it happens.

2. Reproducibility over noise
   I value findings that can be reproduced clearly and judged with minimal ambiguity.

3. Invariants over surface symptoms
   I focus on the deeper protocol assumptions that make a failure meaningful.

4. Root cause over vague impact language
   A strong finding should explain both what breaks and why it breaks.

5. Precision over overclaiming
   I would rather defend a well-supported Medium than force a weak High.

6. State transitions over isolated code lines
   Many important bugs emerge from how components interact over time, not from a single line in isolation.

7. Execution reality over intended design
   I look for places where real behavior diverges from the protocol’s supported or documented flow.

8. High-signal submissions over volume
   The goal is not to submit more, but to submit clearer, stronger, and more defensible findings.

Focus

• Smart contract and protocol security
• Execution correctness and failure paths
• Cross-component logic issues
• Reproducible proof-of-concept testing
• High-signal security reports

Approach

I focus on understanding how systems behave under real execution conditions, tracing invariants through code paths, and validating findings with concrete reproductions whenever possible.

Current Interests

• Smart contract security
• Protocol invariants
• Rust and EVM security research
• zkVM / proving-system correctness
• Cross-chain and message-validation logic

Goal

Build a strong body of public, technically grounded research through clear writeups, PoCs, and contest participation.