05:51 < kallewoof> jeremyrubin: it bugs out occasionally. and it also sometimes bans your account.

06:53 < kallewoof> updated btcdeb to latest taproot. still need to update the 'tap' command, but making taproot/tapscript spending seems to work (tried against regtest and testmepoolaccept works for both types, generated using btcdeb).

06:53 < kallewoof> this is a pull request only, so you'd need to grab that, btw.

08:15 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/a2a250c7d07b...c6532fa6c14d

08:15 < bitcoin-git> bitcoin/master fa41810 MarcoFalke: ci: Run valgrind fuzzer on cirrus

08:15 < bitcoin-git> bitcoin/master fa0538e MarcoFalke: ci: Set cirrus RAM to 8GB

08:15 < bitcoin-git> bitcoin/master c6532fa MarcoFalke: Merge #19746: ci: Move valgrind fuzzer to cirrus

08:15 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #19746: ci: Move valgrind fuzzer to cirrus (master...2008-ciValgrind) https://github.com/bitcoin/bitcoin/pull/19746

08:44 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #19765: doc: Fix getmempoolancestor RPC result doc (master...2008-rpcDoc) https://github.com/bitcoin/bitcoin/pull/19765

11:41 < hebasto> #19710 review begging

11:41 < gribble> https://github.com/bitcoin/bitcoin/issues/19710 | bench: Prevent thread oversubscription and decreases the variance of result values by hebasto · Pull Request #19710 · bitcoin/bitcoin · GitHub

11:57 < jonatack> review beg also for #19628 needed for BIP155 addrv2

11:57 < gribble> https://github.com/bitcoin/bitcoin/issues/19628 | net: change CNetAddr::ip to have flexible size by vasild · Pull Request #19628 · bitcoin/bitcoin · GitHub

12:20 < bitcoin-git> [bitcoin] laanwj pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/c6532fa6c14d...44ddcd887ddf

12:20 < bitcoin-git> bitcoin/master f0fce06 Sebastian Falbesoner: util: make EncodeBase58 consume Spans

12:20 < bitcoin-git> bitcoin/master 356988e Sebastian Falbesoner: util: make EncodeBase58Check consume Spans

12:20 < bitcoin-git> bitcoin/master 44ddcd8 Wladimir J. van der Laan: Merge #19706: refactor: make EncodeBase58{Check} consume Spans

12:21 < bitcoin-git> [bitcoin] laanwj merged pull request #19706: refactor: make EncodeBase58{Check} consume Spans (master...20200810-util-make-base58encode-consume-spans) https://github.com/bitcoin/bitcoin/pull/19706

13:05 < bitcoin-git> [bitcoin] laanwj pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/44ddcd887ddf...e9b30126545d

13:05 < bitcoin-git> bitcoin/master 71e0f07 Sebastian Falbesoner: util: remove unused c-string variant of atoi64()

13:05 < bitcoin-git> bitcoin/master e9b3012 Wladimir J. van der Laan: Merge #19750: refactor: remove unused c-string variant of atoi64()

13:05 < bitcoin-git> [bitcoin] laanwj merged pull request #19750: refactor: remove unused c-string variant of atoi64() (master...20200817-util-remove-unused_cstr_atoi64) https://github.com/bitcoin/bitcoin/pull/19750

17:18 < shesek> is there an easy way to tell whether a node is accepting incoming connections via the rpc?

17:19 < shesek> one way to do this is to look for peers with inbound:true in getpeerinfo, which I guess is the most definitive way to check that connections are accepted in practice

19:34 < jonatack> shesek: i proposed adding inbound and outbound connection counts to RPC getnetworkinfo in #19405

19:34 < gribble> https://github.com/bitcoin/bitcoin/issues/19405 | rpc, cli: add network in/out connections to `getnetworkinfo` and `-getinfo` by jonatack · Pull Request #19405 · bitcoin/bitcoin · GitHub

19:35 < jonatack> shesek: ATM #19643 is open to add an easy way to see them as well, review welcome

19:35 < gribble> https://github.com/bitcoin/bitcoin/issues/19643 | Add `-netinfo` peer connections dashboard by jonatack · Pull Request #19643 · bitcoin/bitcoin · GitHub

19:36 < shesek> but that's for the bitcoin-cli client and not something provided by the rpc itself, right?

19:36 < shesek> fwiw I would find #19405 pretty useful for my purposes

19:36 < gribble> https://github.com/bitcoin/bitcoin/issues/19405 | rpc, cli: add network in/out connections to `getnetworkinfo` and `-getinfo` by jonatack · Pull Request #19405 · bitcoin/bitcoin · GitHub

19:36 < jonatack> so did i, but it died for lack of review and then the review was clobbered by another PR

19:37 < jonatack> could maybe re-open with just the RPC portion, the changeset is really minimal

19:38 < jonatack> will do tomorrow am and ping you

19:41 < jonatack> meanwhile, there's bitcoin-cli getpeerinfo | jq "group_by(.inbound) | map({Inbound: .[0].inbound, Count: length}) | .[]"

19:43 < jonatack> fwiw it's merged into bitcoin-knots

19:44 < bitcoin-git> [bitcoin] jonatack reopened pull request #19405: rpc, cli: add network in/out connections to `getnetworkinfo` and `-getinfo` (master...in-and-out-connections) https://github.com/bitcoin/bitcoin/pull/19405

19:53 < jonatack> shesek: runless you set -listen=0, inbound connections should be accepted by default unless -proxy or -connect is used

19:54 < jonatack> e.g. bitcoind -h | grep -A1 "\-listen"

19:56 < shesek> jonatack, right, but I'm trying to determine that in the context of an application that connects to the node over rpc, I can't tell how the user's node is going to be configured

19:58 < jonatack> 👍

20:22 < shesek> I think this may be the first time I saw an emoji on irc

20:26 < sipa> Ừńìċộđẹ ổñ ỊŔÇ îś łờţš ọƒ ƒûň ŧħóǔğħ

20:26 < sipa> uıds pɐǝɥ ɹnoʎ sǝʞɐɯ ʎʃʃɐǝɹ ʇı

20:31 < luke-jr> -.-

20:39 < shesek> sipa, lol, it did :)

20:48 < sipa> ₿

20:56 < sipa> [A

22:31 < bitcoin-git> [bitcoin] luke-jr closed pull request #19243: banman: Limit resources consumed by misbehaving node deprioitisation (master...misbehaving_limit) https://github.com/bitcoin/bitcoin/pull/19243

22:54 < luke-jr> I would if it would improve review, to have a single reviewer responsible for the initial churn with the author, and only have others review after the two of them are happy with it