CSO: Kim Hyungchul (김형철)
Kim Hyungchul (김형철) was the Chief Security Officer (CSO) and Co-Founder of Mound Inc. He holds 20% of Krypton PTE. LTD. As CSO, he bore direct responsibility for the security posture of Qubit Finance — including the fatal decision to deploy unaudited bridge code to production.
Professional Background
Section titled “Professional Background”| Field | Detail |
|---|---|
| linkedin.com/in/artify | |
| facebook.com/ucu072 | |
| Connections | 141 · 144 followers |
| Mutual Group | Google Android |
Self-Description (LinkedIn About)
Section titled “Self-Description (LinkedIn About)”“Software Engineer / Developer / DeFi / Solidity / iOS / Swift /“
Career History
Section titled “Career History”| Period | Company | Role |
|---|---|---|
| Jun 2020 – Present | Mound, Inc. | Co-Founder, CSO |
| Sep 2016 – Present | Artify Inc. | Founder / Developer, Seoul |
| Apr 2014 – May 2015 | Frankly Chat | Software Engineer, San Francisco |
| Jun 2013 – Apr 2014 | SK planet | Manager of iOS Development team, Seoul |
| Mar 2011 – May 2013 | Madsmart | Co-founder Engineer, Seoul — iOS development |
Education
Section titled “Education”| Institution | Credential |
|---|---|
| KAIST (Korea Advanced Institute of Science and Technology) | Computer Science |
Facebook Activity
Section titled “Facebook Activity”Kim Hyungchul posted on Facebook on April 21, 2021 recruiting developers for Mound:
“DeFi 개발사 마운드에서 개발자를 찾습니다. 마운드는 글로벌 No. 1 이자농사 플랫폼을 개발하고 있는 회사입니다…”
(Translation: “Mound, a DeFi development company, is looking for developers. Mound is a company developing the global No. 1 yield farming platform…”)
The post received 56 likes and 34 comments.
Registered Address
Section titled “Registered Address”Per Krypton PTE. LTD. corporate filings:
105-dong 2001-ho, 84, Geobukgol-ro, Seodaemun-gu, Seoul, Korea
Security Responsibility
Section titled “Security Responsibility”As CSO, Kim Hyungchul was directly responsible for:
- Ensuring code was audited before production deployment
- Reviewing bridge architecture for known vulnerability patterns (the EOA zero-address issue had been publicly documented since 2019)
- Establishing processes for timelocks and announcements on contract parameter changes
- Coordinating rapid security response with exchanges after the incident — which did not happen
The title “Chief Security Officer” represents a direct accountability for the security failure that led to the $80M loss.