Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> and have attracted tons of developer talent to crypto

And yet: "Both issues were caught after the code had been audited, merged, and slated for release"

I wonder who did those audits?



The answer to this question is out there, but the reports are not published yet.

I caution readers to not make rash judgements on their skill like this though. These bugs are really hard to find, and it was a minor miracle that I noticed these ones at all. I actually had a whole list of critical bugs in this codebase ready to report before the V2 upgrade was merged to master (which would put it in scope for a bounty). However the auditors managed to find every single bug on my list. I only noticed the ones that eventually made it here later, by a stroke of luck, and after I had already spent a ton of time looking at this codebase without noticing them.


congratulations ser

did you try other things like try to get employed by the team, or consider submitting an altruistic pull request? or was the bug bounty the adequate incentive from the getgo


Cool thing about the space — you can likely check the source yourself + find the audit reports!


were you being snarky about the word talent, got it, please see the forum guidelines about substantive discussion, believe it or not they apply to crypto discussion here too




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: