practicalswift (Thomas J)

Nice catch @guidovranken! Very excited about your work: thanks for helping hardening various parts of the Bitcoin ecosystem by trying to break it! :) I saw the Trezor firmware bug...

Concept ACK on doing something about the vague/confusing security model ("trusted but also not trusted") of the REST API.

Bitcoin Core would be great to have fuzzed as part of oss-fuzz :) I contribute to Bitcoin Core and would be very glad to help any volunteer who wants to...

ACK 333a605d21c77002efb27aaf2fe352775f1bb3b0

@luke-jr I wasn't aware that only BIP authors were supposed to review typo fixes. Sorry about that! :-)

> Here are some assumptions that come to my mind immediately: > … > This is a shot in the dark but @roconnor-blockstream do you know some more? FWIW, these...

@elichai This is an excellent initiative! Thanks a lot for doing this! ❤️ Strongest possible concept ACK from a fellow fuzzing enthusiast :) Yesterday I setup a very basic fuzzing...

@elichai Have you checked what parts of the code your fuzzer is able to reach deeply in to, and what parts that are only shallowly fuzzed when starting from an...

> How do I check that? This is the type of output you would like to be looking at when searching for opportunities to tweak your fuzzer to reach deeper:...

@elichai I've now created a repo (https://github.com/practicalswift/libsecp256k1-fuzzing-seed-corpus) where we can share coverage increasing inputs :) I've added a first batch of the 2911 coverage increasing inputs I've found using a...