These things (and the open backport PR) are the only things I'm perosnally tracking for 0.13.2 (I made a call in #bitcoin this morning for bugreports against 0.13.1 with an eye towards getting 0.13.2 ready).
[bitcoin] gmaxwell opened pull request #9293: [0.13 Backport] IBD using chainwork instead of height and not using header timestamp (#9053) (0.13...9053_backport) https://github.com/bitcoin/bitcoin/pull/9293
rm -rf ~/.bitcoin, git clean -xdf, ./autogen.sh, ./configure --disable-bench --disable-tests --disable-wallet --without-miniupnpc, make -j4, ./src/bitcoind -minrelaytxfee=0.00000001 ---- that was my previous steps, I'm retrying them now
(takes like 15 minutes to comile bitcoin on my laptop)
like, fresh compile, fresh .bitcoin, deadlocks on -minrelaytxfee=0.00000001
on *nix: ps aux | grep bitcoin to get the bitcoind pid then gdb -p <pid> to attach. then run thread apply all bt full to get backtraces from every thread, and 0bin that to me, and then you can type q<enter> to quit
essentially, i think we should first introduce clean abstractions between certain modules inside bitcoin core, in such a way that it's effectively bitcoind using a consensus library already, without it being exposed
even if we only expose the version with our implementation, I think it would be good to abstract consensus storage even for bitcoin core rewardless of libconsensus users
I just feel that the purpose of these changes is no longer clear. Expecting the user to implement complex interfaces with bitcoin specific and consensus critical behavior is at odds with what I understood to be the stated goal.
regarding the validation flags, I replaced #7779 with https://github.com/bitcoin/bitcoin/pull/9271 (although got errors in unittests because we're already relying on the consensus flags being coupled for testing it seems)
and the way I implemented it there, is also inneficient for bitcoin core
btw, I was serious about rewritting any part of https://github.com/bitcoin/bitcoin/pull/8328 that can be agreed on, just without any clear agreement, there's no point and keeping that open for long (since it's guaranteed to be arebase hell)