Selected work

Evidence you can open and inspect.

Contests / findings / CTFs / research

Public records do not replace diligence on a proposed engagement. They do make one thing easier: evaluating how Taichi finds, explains, and reasons about security failures before you share code.

Track record

Repeated signal, not a single logo wall.

Figures below are maintained from the public Taichi portfolio. Follow the linked contest and report records to verify the underlying evidence.

70+

Competitive audits

14

First places

24

Top 3 finishes

170+

H/M findings

ZKsync Era

1st place

Code4rena

L2 protocol

Maia DAO Ecosystem

1st place

Code4rena

DeFi system

Arbitrum BoLD

1st place

Code4rena

Dispute protocol

Arcade.xyz

1st place

Cantina

Protocol review

Coinbase SpendPermission

1st place

Cantina

Account abstraction

OneWorld

1st place

CodeHawks

Smart contracts

Public portfolio data · verified Jul 2026

Contest platforms may display the member handle used for a submission; the Taichi portfolio records the corresponding group result.

How to read the evidence

Different signals answer different questions.

01

Contest placements

Measure repeated performance under open competition, independent judging, and fixed review windows.

02

Public findings

Let engineering teams inspect issue framing, impact reasoning, affected paths, and technical specificity.

03

CTF performance

Keeps exploit construction, debugging, and adversarial execution active—not only vulnerability classification.

04

Source-level research

Shows how the team models unfamiliar systems before a commercial conversation begins.

Your system is the next evidence

Ask how this experience maps to your attack surface.