As for the methodology, I am evaluating libbitcoin's API in relation to a subset of the API usability heuristics and guidelines defined by Mosqueira-Rey et al. (see reference further down). To help with this, I have implemented some of the guidelines in a static code analysis tool built using Clang Libtooling. As my hypothesis was (or is) that supporting usable security in Bitcoin APIs would help to protect against potential vulnerabilities in SW that uses such APIs, I had initially planned to analyse client SW that uses libbitcoin. However, I have not found many open source applications suitable for analysis, so I am focusing on the API and its usability now. I still have to analyse its use, as this is what my proposal says I will do, but I'll have to do with what's available, which is basically what comes with libbitcoin, i.e. libbitcoin-explorer, libbitcoin-node and libbitcoin-server. I think I found one or two others.
Mosqueira-Rey, Eduardo, David Alonso-Ríos, Vicente Moret-Bonillo, Isaac Fernández-Varela, and Diego Álvarez-Estévez. “A Systematic Approach to API Usability: Taxonomy-Derived Criteria and a Case Study.” Information and Software Technology 97 (May 2018): 46–63.
https://doi.org/10.1016/j.infsof.2017.12.010.