[bitcoin] practicalswift opened pull request #13712: wallet: Add error handling. Check return value of ParseUInt32(...) in… (master...check-ParseUInt32-return-value) https://github.com/bitcoin/bitcoin/pull/13712
AHemlocksLie: start off reading all the docs you can find on github.com/bitcoin/bitcoin in particular the developer docs and contributor guidelines. Then look at pull requests people have made and get a feel for how the process works. To actually do something, I suggest actually using the software. You run into things you want to improve and then you work on that.
hi everyone, i am new to bitcoin core development. I have setup my bitcoin core project with Eclipse CDT on a Mac. I am able to compile, run and debug the build. However, I am not make my IDE to find the #include<util.h> and all the header source files.
[bitcoin] 251Labs opened pull request #13656: Remove the boost/algorithm/string/predicate.hpp dependency from netbase.cpp (master...patch/remove_boost_predicate_from_netbase) https://github.com/bitcoin/bitcoin/pull/13656
[bitcoin] afk11 opened pull request #13655: bitcoinconsensus: invalid flags should be set to bitcoinconsensus_err (master...bitcoinconsensus-invalid-flags-squashed) https://github.com/bitcoin/bitcoin/pull/13655
Empact: re #13632 sipa's C++ implementation of bech32 string operations in bitcoin is grossly slow in a dozen different ways, because it was made for simplicity and readability. The C implementation in the bech32 examples should be a lot faster (and also was not optimized for the highest speed). It seems weird to me to keep seeing PRs doing nibbling speed optimizations for code that just wasn
jnewbery: I also had a unicorn while at the building bitcoin conference, haven't seen any since yet, will take a look