--- Log opened Fri Mar 01 00:00:03 2019
00:03 -!- Cory [Cory@unaffiliated/cory] has quit [Ping timeout: 245 seconds]
00:09 -!- Pasha [Cory@unaffiliated/cory] has joined #bitcoin-core-dev
00:12 -!- Pasha is now known as Cory
00:13 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev
00:25 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 250 seconds]
00:30 -!- aqquadro [~name@net-37-159-134-26.cust.vodafonedsl.it] has joined #bitcoin-core-dev
00:30 -!- aqquadro [~name@net-37-159-134-26.cust.vodafonedsl.it] has quit [Changing host]
00:30 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev
00:30 -!- name [~name@net-37-159-134-26.cust.vodafonedsl.it] has joined #bitcoin-core-dev
00:30 -!- name [~name@net-37-159-134-26.cust.vodafonedsl.it] has quit [Remote host closed the connection]
00:32 -!- promag_ [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection]
00:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
00:35 < bitcoin-git> [bitcoin] gwillen opened pull request #15508: Refactor analyzepsbt for use outside RPC code (master...feature-separate-analyzepsbt) https://github.com/bitcoin/bitcoin/pull/15508
00:35 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
00:40 -!- jungly [~quassel@host97-200-static.8-79-b.business.telecomitalia.it] has joined #bitcoin-core-dev
00:42 -!- justinmoon [~manjaro-i@cpe-70-113-80-71.austin.res.rr.com] has quit [Ping timeout: 259 seconds]
00:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds]
00:45 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
00:48 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
00:50 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 255 seconds]
01:09 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev
01:13 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Ping timeout: 255 seconds]
01:32 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
01:41 < meshcollider> remember the wallet meeting is tomorrow/today
01:47 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
01:57 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
02:01 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
02:04 -!- kexkey [~kexkey@139.28.218.30] has quit [Ping timeout: 250 seconds]
02:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
02:14 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
02:14 -!- rex4539 [~rex4539@ppp-2-84-160-62.home.otenet.gr] has quit [Quit: rex4539]
02:15 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has joined #bitcoin-core-dev
02:23 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 245 seconds]
02:23 -!- whb [~user@210.12.6.246] has joined #bitcoin-core-dev
02:26 -!- whb [~user@210.12.6.246] has quit [Client Quit]
02:27 -!- hyperwang [~user@210.12.6.246] has joined #bitcoin-core-dev
02:28 < hyperwang> f
02:35 -!- hyperwang [~user@210.12.6.246] has quit [Ping timeout: 245 seconds]
02:36 -!- Jackielove4u [uid43977@gateway/web/irccloud.com/x-umkgfwtzpszxkcdr] has joined #bitcoin-core-dev
02:40 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #bitcoin-core-dev
02:46 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
02:51 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev
02:51 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 240 seconds]
02:55 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev
02:58 < provoostenator> meshcollider: awesome
02:58 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
02:59 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has quit [Ping timeout: 240 seconds]
03:01 < fanquake> meshcollider how long until that?
03:17 < provoostenator> fanquake: 19:00 GMT / Iceland time
03:18 < provoostenator> I like how this is almost an ad for GMT: https://time.is/nl/GMT
03:18 < provoostenator> "No daylight saving time, same UTC offset all year"
03:23 < tryphe> provoostenator, Iceland has darkness saving time =p
03:25 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
03:25 < fanquake> provoostenator right, so same as usual meeting time? 3am
03:26 < fanquake> I played around with the deterministic builds for HWI today, got stuck with wine and page faults.
03:53 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev
03:55 -!- Deinogalerix21 [~Deinogale@89.238.176.150] has joined #bitcoin-core-dev
03:55 < jonasschnelli> hmm... "bitcoin-addcon invoked oom-killer"
03:56 < jonasschnelli> Ran current master on a 4GB ARM with -dbache=2000
04:04 -!- zhangzf [~zhangzf@106.38.157.147] has quit [Remote host closed the connection]
04:15 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
04:19 -!- rex4539 [~rex4539@boo--1.static.otenet.gr] has joined #bitcoin-core-dev
04:27 -!- rex4539 [~rex4539@boo--1.static.otenet.gr] has quit [Quit: rex4539]
04:30 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 258 seconds]
04:32 -!- queip [~queip@unaffiliated/rezurus] has joined #bitcoin-core-dev
04:43 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has joined #bitcoin-core-dev
04:49 < fanquake> promag is 15478 part of, or the fix for 15453 ?
05:08 -!- promag_ [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection]
05:17 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
05:21 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 250 seconds]
05:29 -!- darosior [~darosior@37.168.77.166] has joined #bitcoin-core-dev
05:32 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]
05:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev
05:44 < jonasschnelli> What could be the reason why bitcoind uses 3GB of ram (RES) when running with -dbcache=2000?
05:44 < instagibbs> gwillen, TIL we wrapped boost optional in core :) 
05:44 < jonasschnelli> I'm aware that the maxmempool gets added to the cache during IBD
05:45 < jonasschnelli> 3GB - 300MB mempool - 2GB dbcache makes still 700MB for core without the mempool...
05:47 < jonasschnelli> OMG... ignore me. I should sleep more, I set the dbcache to 20GB
05:48  * jonasschnelli blames the stupid and broken MacBookPro keyboard
05:56 < provoostenator> Why buy a reliable keyboard if you can buy more RAM?
06:01 < jonasschnelli> heh
06:02 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Quit: Leaving]
06:04 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
06:06 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:06 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/29c24b05fb71...e8612adc5d07
06:06 < bitcoin-git> bitcoin/master fa852f0 MarcoFalke: test: Bump timeout on tests that timeout on windows
06:06 < bitcoin-git> bitcoin/master e8612ad MarcoFalke: Merge #15507: test: Bump timeout on tests that timeout on windows
06:06 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:06 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:06 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15507: test: Bump timeout on tests that timeout on windows (master...1903-testTimeoutWindows) https://github.com/bitcoin/bitcoin/pull/15507
06:07 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:09 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 255 seconds]
06:11 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
06:14 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:14 < bitcoin-git> [bitcoin] MarcoFalke pushed 6 commits to master: https://github.com/bitcoin/bitcoin/compare/e8612adc5d07...a6d7026a45c9
06:14 < bitcoin-git> bitcoin/master 7aa6a8a Pieter Wuille: Add ParseRange function to parse args of the form int/[int,int]
06:14 < bitcoin-git> bitcoin/master 6b9f45e Pieter Wuille: Support ranges arguments in RPC help
06:14 < bitcoin-git> bitcoin/master 4566011 Pieter Wuille: Add support for stop/[start,stop] ranges to scantxoutset
06:14 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:15 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:15 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15497: rpc: Consistent range arguments in scantxoutset/importmulti/deriveaddresses (master...201902_rpcconsistentrange) https://github.com/bitcoin/bitcoin/pull/15497
06:15 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:15 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 258 seconds]
06:19 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
06:20 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 255 seconds]
06:21 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
06:24 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:24 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #15509: [rpc] deriveaddresses: add range to CRPCConvertParam (master...1903-rpcDeriveAddress) https://github.com/bitcoin/bitcoin/pull/15509
06:24 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:24 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:24 < bitcoin-git> [bitcoin] Sjors opened pull request #15510: [rpc] deriveaddresses: add range to CRPCConvertParam (master...2019/02/rpcconsistentrange) https://github.com/bitcoin/bitcoin/pull/15510
06:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:25 < MarcoFalke> lol
06:25 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev
06:25 < provoostenator> Oops
06:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:25 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #15509: [rpc] deriveaddresses: add range to CRPCConvertParam (master...1903-rpcDeriveAddress) https://github.com/bitcoin/bitcoin/pull/15509
06:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:26 < promag> wat!
06:27 < instagibbs> awkward 
06:27 < promag> provoostenator: MarcoFalke: well played, you don't fool us X)
06:28 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev
06:29 < MarcoFalke> eh? My pull was opened earlier! xD
06:30 < fanquake> race
06:30  * MarcoFalke fixes race in deriveaddress
06:31 < promag> MarcoFalke: true! then provoostenator commits fast
06:31 < MarcoFalke> promag: ERROR: deriveaddresses argument 1 is named range in vRPCConvertParams but ['begin'] in dispatch table
06:32 < MarcoFalke> I guess named args don't work then
06:32 < promag> where do you get that?
06:33 < fanquake> promag https://travis-ci.org/bitcoin/bitcoin/jobs/500366793
06:33 < promag> fanquake: thanks, just saw it too
06:34 < fanquake> promag you might have missed my question above^. Is 15478 part of, or the fix for 15453 ?
06:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
06:36 < promag> yes the goal of that should fix 15453
06:39 < fanquake> ok
06:40 -!- whb [~user@221.216.231.200] has joined #bitcoin-core-dev
06:40 -!- whb [~user@221.216.231.200] has left #bitcoin-core-dev ["ERC (IRC client for Emacs 26.1)"]
06:41 -!- hyperwang [~user@221.216.231.200] has joined #bitcoin-core-dev
06:41 -!- hyperwang [~user@221.216.231.200] has quit [Client Quit]
06:42 -!- hyperwang [~user@221.216.231.200] has joined #bitcoin-core-dev
06:44 -!- Deinogalerix21 [~Deinogale@89.238.176.150] has quit [Quit: WeeChat 2.4]
06:45 -!- hyperwang [~user@221.216.231.200] has left #bitcoin-core-dev []
06:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:49 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/a6d7026a45c9...dc251de6a5c4
06:49 < bitcoin-git> bitcoin/master aeb7fbf Chun Kuan Lee: appveyor: Don't build debug libraries instead of "build and delete"
06:49 < bitcoin-git> bitcoin/master dc251de MarcoFalke: Merge #15506: appveyor: fix cache issue and reduce dependencies build time...
06:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
06:49 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15506: appveyor: fix cache issue and reduce dependencies build time (master...appveyor-release-only) https://github.com/bitcoin/bitcoin/pull/15506
06:49 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
06:52 -!- kabaum [~kabaum@2001:9b1:efd:9b00:36e6:d7ff:fe35:5aa] has quit [Ping timeout: 264 seconds]
07:00 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has quit [Quit: ZNC - http://znc.in]
07:02 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has joined #bitcoin-core-dev
07:03 < darosior> Hi, I saw that in init.cpp the service NODE_NETWORK_LIMITED is set with NODE_NETWORK at the begining, but I wonder why it is not reset if we did not pruned the block chain ? (https://github.com/bitcoin/bitcoin/blob/b4fc5257b7dc106ff210d170397d4ce0e024f2c0/src/init.cpp#L1652)
07:04 < provoostenator> Surprising how many testnet peers are still stuck at the CVE-2018-17144 exploit block. https://bitcoin.stackexchange.com/questions/79662/solving-bitcoin-cores-activatebestchain-failed
07:04 < gmaxwell> darosior: limited means the node can ALSO serve recent blocks, services are additive.
07:05 < provoostenator> My node shows lots of "Disconnecting outbound peer 5 for old chain, best known block = 00000000210004840364b52bc5e455d888f164e4264a4fec06a514b67e9d5722"
07:05 < darosior> gmaxwell : Thank you.
07:05 < gmaxwell> provoostenator: most testnet nodes are just forgotten old software, this has more or less always been true. :)
07:06 < darosior> gmaxwell : It is indicated "only" instead of "also" in the comment https://github.com/bitcoin/bitcoin/blob/a6d7026a45c915794338c178b7f95d5c1f8e977f/src/protocol.h#L267
07:07 < gmaxwell> darosior: you're misunderstanding the comment.
07:07 < provoostenator> getchaintips shows this particular block as  "headers-only", which I guess is why it doesn't immediately disconnect from nodes with this block?
07:07 < gmaxwell> darosior: limited = NETWORK-old_blocks    so NETWORK + LIMITED = NETWORK
07:09 < darosior> gmaxwell : Ok, thank you.
07:11 < provoostenator> (it took 22 minutes from connecting to disconnecting)
07:12 < gmaxwell> provoostenator: it won't attempt to fetch it because its clearly a losing chaintip.
07:12 < gmaxwell> provoostenator: it also wouldn't be good to disconnect immediately because that would prevent the peer getting blocks from you and reorging to your chain (if it could)
07:13 < provoostenator> Ah ok, so it's altruistic intended behavior then. That also applies even if we did know it was invalid?
07:15 < gmaxwell> provoostenator: it's incorrect to call that altruistic, as getting the rest of the network on to your chain is very much in your interest... but the getting other people part is mostly accomplished by not doing that kind of strict behavior on inbound.
07:16 < gmaxwell> if they actually send something invalid, we'll punt right away.
07:20 -!- DougieBot5000_ [~DougieBot@unaffiliated/dougiebot5000] has joined #bitcoin-core-dev
07:23 -!- DougieBot5000 [~DougieBot@unaffiliated/dougiebot5000] has quit [Ping timeout: 250 seconds]
07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:25 < bitcoin-git> [bitcoin] darosior opened pull request #15511: RPC : More user-friendly services field in getnetworkinfo and getpeerinfo (master...services_for_humans) https://github.com/bitcoin/bitcoin/pull/15511
07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:52 -!- zivl [~zivl@unaffiliated/zivl] has quit [Read error: Connection reset by peer]
07:52 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
07:53 < MarcoFalke> I got the "lists.linuxfoundation.org mailing list memberships reminder", so at least it is not all-down
07:53 -!- zivl [~zivl@unaffiliated/zivl] has joined #bitcoin-core-dev
07:57 < gmaxwell> lol
07:57 < gmaxwell> I suspect the list itself works, but it's all moderated and the moderation interface is down...
08:08 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
08:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
08:13 < bitcoin-git> [bitcoin] jonasschnelli opened pull request #15512: Add ChaCha20 encryption option (XOR) (master...2019/03/chacha) https://github.com/bitcoin/bitcoin/pull/15512
08:13 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
08:17 -!- darosior [~darosior@37.168.77.166] has quit [Remote host closed the connection]
08:18 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
08:33 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
08:37 -!- justinmoon [~manjaro-i@cpe-70-113-80-71.austin.res.rr.com] has joined #bitcoin-core-dev
08:44 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
08:46 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
08:50 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
08:50 -!- schmidty_ [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev
08:52 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
08:56 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev
09:17 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Ping timeout: 256 seconds]
09:17 -!- morcos [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev
09:40 -!- jungly [~quassel@host97-200-static.8-79-b.business.telecomitalia.it] has quit [Remote host closed the connection]
09:40 < gwillen> instagibbs: yeah, I assume we wrap boost::optional so we can replace it with the std one when the time comes
09:40 < sipa> indeed
09:40 < instagibbs> roger that
09:41 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/]
09:42 < sipa> the source code says "
09:42 < sipa> //! Substitute for C++17 std::optional"
09:49 < gwillen> although I noticed when I was messing around in psbt.h that PartiallySignedTransaction has a boost::optional in it
09:49 < gwillen> I left it alone but I'll change it if someone complains
10:03 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 268 seconds]
10:08 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
10:27 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds]
10:35 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds]
10:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
10:54 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
10:55 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
10:55 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/dc251de6a5c4...f9dbb319d26f
10:55 < bitcoin-git> bitcoin/master 2fa85eb Adam Jonas: add rpc_misc.py, mv test getmemoryinfo, add test mallocinfo
10:55 < bitcoin-git> bitcoin/master f13ad1c Adam Jonas: modify test for memory locked in case locking pages failed at some point
10:55 < bitcoin-git> bitcoin/master f9dbb31 MarcoFalke: Merge #15485: add rpc_misc.py, mv test getmemoryinfo, add test mallocinfo
10:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
10:56 < bitcoin-git> [bitcoin] MarcoFalke merged pull request #15485: add rpc_misc.py, mv test getmemoryinfo, add test mallocinfo (master...test_rpc_misc) https://github.com/bitcoin/bitcoin/pull/15485
10:56 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
11:00 < meshcollider> wallet meeting time :)
11:00 < meshcollider> #startmeeting
11:00 < lightningbot> Meeting started Fri Mar  1 19:00:45 2019 UTC.  The chair is meshcollider. Information about MeetBot at http://wiki.debian.org/MeetBot.
11:00 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
11:00 < provoostenator> hi
11:00 < sipa> present
11:00 < meshcollider> #bitcoin-core-dev Wallet Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator aj Chris_Stewart_5 dongcarl gwillen jamesob ken281221 ryanofsky gleb
11:00 < instagibbs> hi
11:01 < meshcollider> Topics for this week?
11:01 < achow101> Hi
11:01 < sipa> i guess there isn't anything wallet-related for 0.18
11:02 < provoostenator> #15453
11:02 < gribble> https://github.com/bitcoin/bitcoin/issues/15453 | Starting bitcoin-qt with -nowallet and then opening a wallet does not show the wallet · Issue #15453 · bitcoin/bitcoin · GitHub
11:02 < provoostenator> Is tagged with 0.18 anyway
11:03 < provoostenator> With a cliff-hanger from promag 
11:03 < meshcollider> That's a Qt issue though right
11:03 < achow101> It only effects people who self compile
11:04 < achow101> As the issue is with qt versions
11:06 < provoostenator> It seems so, in which case it should be OK as long as we backport the fix onto the 0.18 branch.
11:07 < meshcollider> Mhm
11:07 < meshcollider> Other than that, yeah, we managed to get all the wallet PRs for 0.18 reviewed and merged pretty efficiently so nice work
11:09 < provoostenator> Proposed topic: descriptor based wallets
11:09 < provoostenator> (briefly anyway, since everyone is focussed on 0.18)
11:11 < provoostenator> sipa: one thing we talked about before that would be useful for my HWW PR is away to compose descriptors in code 
11:12 < provoostenator> If you're able to whip up an example for e.g. sh(wpkh(xpub)) I can probably figure out the rest
11:12 < provoostenator> It's just my C++ is a bit rusty when it comes to unique_ptr and abstract classes.
11:12 < sipa> provoostenator: it's not that trivial anymore in the current code
11:12 < sipa> i briefly had a look, but it would need some restructuring
11:13 < provoostenator> Ok, glad to know it's not just me :-)
11:13 -!- rex4539 [~rex4539@2a02:587:3504:8500:1172:aa23:8232:6e62] has joined #bitcoin-core-dev
11:14 < provoostenator> The use case here is that we fetch an xpub from a hardware wallet and then construct a descriptor with that.
11:14 < sipa> with the 0.18 things out of the way, i'll try to find time to do the ismine/keypool abstraction i've talked about before
11:15 < provoostenator> ismine/keypool stuff also very useful.
11:16 < provoostenator> An alternative approach would be to be require the hardware wallet (driver) to give a full descriptor, or a set of potential desrciptors from which we pick one or more.
11:16 < meshcollider> #topic descriptor based wallets
11:16 < provoostenator> But that choice shouldn't be determined by implementation details such as this I think.
11:17 < sipa> provoostenator: you can always construct the descriptor in string form
11:17 < sipa> i agree that's suboptimal, but it means having an API to construct descriptors shouldn't be a blocker
11:17 < provoostenator> That's what I'm doing in the prototype.
11:18 < instagibbs> I've done this previously as well, constructing manually
11:18 < provoostenator> There's not really any blockers left in that PR, so I'm mostly focussing on getting it merge-worthy.
11:18 -!- _Sam-- [greybits@gateway/vpn/privateinternetaccess/sam--/x-37783179] has quit [Read error: Connection reset by peer]
11:19 < provoostenator> Although it would be safer when combined with native-descriptor wallets, because the behavior of getnewaddress doesn't jive well with BIP44/49/84 that wallets use.
11:19 < provoostenator> (that hardware wallets tend to use)
11:19 < instagibbs> provoostenator, you're safe as long as you don't use getnewaddress with a watchonly wallet :D 
11:20 < meshcollider> are hardware wallets working on implementing things like returning descriptors?
11:20 < provoostenator> instagibbs: so you use deriveaddresses? 
11:20 < instagibbs> provoostenator, no I just assume people aren't going to dust my cold wallet :P
11:20 < provoostenator> meshcollider: not that I know, but HWI python coud easiliy do that.
11:20 < instagibbs> meshcollider, unlikely to get that standardized, no
11:21 < meshcollider> Mhm
11:21 < instagibbs> ledger has basically said they won't bother supporting PSBT like ever 
11:21 < meshcollider> Oh, thats a shame
11:21 < instagibbs> I can't imagine they'd do descriptors
11:21 < sipa> well they don't need to
11:21 < instagibbs> sipa, right, it's fine
11:21 < instagibbs> just giving context
11:22 < sipa> i mean: i wouldn't even recommend that hw wallets directly implement psbt
11:22 < sipa> all you need is a software driver that supports it
11:22 < sipa> same with descriptors
11:22 < sipa> they're a software (and bitcoin core specifically...) kinda thing
11:22 < provoostenator> Basically Bitcoin Core could give an account number and then HWI would, if the device supports SegWit return three descriptors: "pkh([44'/0'/account]xpub/0/*])", "sh(wpkh([49'/0'/account]xpub/0/*]))" and "wpkh([84'/0'/account]xpub/0/*])" (plus change), and then our wallet imports one or all
11:23 < achow101> hwi already uses descriptors
11:24 < provoostenator> But the current importmulti logic doesn't handle the above correctly, native descriptor wallets would.
11:24 < provoostenator> So then you can get a bech32 address and it will grab it from the wpkh(84' tree, or fail if that's absent.
11:25 < provoostenator> We probably only need two address types: default and wrapped-segwit. Default is either legacy pkh() or native segwith (wpkh or script hash).
11:25 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has quit [Quit: pinheadmz]
11:26 < sipa> you'd mark certain records as the provider for certain types of addresses
11:27 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
11:27 < sipa> if you don't have one for native segwit addresses, then requesting a native segwit address will fail
11:28 < provoostenator> Right, I guess it's fine to hold on to the current address_type concept then. 
11:28 < provoostenator> legacy, p2sh_segwit and bech32
11:28 < provoostenator> But simply fail if the right descriptor isn't available.
11:28 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has quit [Client Quit]
11:29 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
11:29 < provoostenator> Do descriptors needs to "marked" for that? Or can you just infer it?
11:29 < meshcollider> The default ones would need to be marked in case you have others too
11:29 < sipa> well i'm imagining you can have multiple records
11:30 < provoostenator> One default record in case there's multiple records of the same address type.
11:30 < sipa> (especially if you have a wallet that at some point switched over to a new key/descriptor/hwwallet for whatever reason, but still want to keep access to old transaction history with the previous ones)
11:31 < provoostenator> I was thinking of adding a purpose enum: receive, change, other
11:32 < sipa> yes
11:32 < provoostenator> For each address type there can only be one descriptor with receive/change
11:32 -!- jarthur [~jarthur@207.114.244.5] has quit [Quit: BRB]
11:32 < sipa> why?
11:32 < provoostenator> Because that indicates the default
11:32 < sipa> what a descriptor is used for should be independent of whether it's the default imo
11:32 < provoostenator> That makes sense
11:33 < provoostenator> So then in addition to purpose, we also need to track the default descriptors.
11:33 < sipa> if you transition to a new one, the one you used for change before doesn't stop being change
11:33 < sipa> i think that's all in https://gist.github.com/sipa/125cfa1615946d0c3f3eec2ad7f250a2 already
11:34 < provoostenator> How do we identify descriptors if there's more than one? Just an increasing int as we add them, or by their checksum (seems brittle) or something else?
11:34 < sipa> seems like an implementation detail
11:35 < provoostenator> Well, it matters for RPC arguments, but for now I'm avoiding that problem by not allowing more than one of each purpose :-)
11:36 < sipa> do you need to expose internal identifiers?
11:36 < sipa> (i haven't thought much about this)
11:36 < meshcollider> Identify them by checksum :p
11:37 < sipa> if so, it seems best that records have a unique user-provided name, and you use that name in rpc to refer to them
11:37 < provoostenator> sipa: getnewaddress "Buy new cow" bech32 [how do I tell which non-default descriptor to use]
11:37 < instagibbs> why not force them to switch first, then call getnewaddress
11:37 < sipa> provoostenator: is that necessary?
11:38 < provoostenator> Name makes sense
11:38 < sipa> provoostenator: you can't getnewaddress from an old keypool now either
11:38 < meshcollider> Other records are more for things like watch-only, etc 
11:38 < meshcollider> Internal stuff
11:38 < provoostenator> True, if non-default descriptors can only be used for archival purposes then there's no need to support them in getnewaddress
11:39 < sipa> that's what i was thinking yes; they're just there to not lose old transaction history
11:39 < sipa> or to watch
11:39 < provoostenator> It also depends on how much we want to push for 1-wallet-1-goal 
11:39 < provoostenator> Rather than put-whatever-you-want-in-a-single-walllet
11:40 < sipa> right; but in a pure watch-only wallet (where "watch only" truly means you're watching someone else's wallet, not just "i don't have the private key right here"), you probably don't want to have any "default newaddress provider"
11:40 < provoostenator> I also prefer keeping wallets simple in that sense, especially to keep the GUI sane.
11:40 < sipa> because there shouldn't be a way to create new addresses
11:41 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has quit [Quit: pinheadmz]
11:41 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
11:41 < provoostenator> Agree that getnewaddress should require >= IsSolveable
11:41 < sipa> descriptors are always solvable
11:41 < sipa> (except the "raw" and "script" ones, but those can't be used to derive anything anyway)
11:42 < provoostenator> Ah yes
11:42 < sipa> solvability is not the point
11:42 < meshcollider> thats the difference between is "mine" and is "spendable" 
11:43 < sipa> so right now "watchonly" means "i don't happen to have the private key in my wallet.dat file"
11:43 < sipa> i think that's a mistake
11:43 < meshcollider> Agree, this rework is the perfect time to tighten up definition of things like that too
11:43 < sipa> the distinction between "my money" and "watched money" is useful, but it's somewhat independent from where the private keys live
11:44 < sipa> especially in a hwwallet/offline storage/... kinda world... the case where the private key is actually in your wallet.dat file (even for your own coins) should be the exception
11:45 < sipa> oh, i guess i should bring this up here, i did a talk at SBC19 about miniscript, and i'll work on getting support for it in core
11:45 < sipa> so that our signer (including psbt, etc) can deal with more complicated scripts than just single key and multisig
11:46 < provoostenator> So we can do things like GreenAddress style multisig or timeout & single sig?
11:46 < sipa> yeah
11:47 < meshcollider> Was the talk recorded
11:47 < sipa> https://www.youtube.com/watch?v=XM1lzN4Zfks
11:47 < meshcollider> Thanks
11:47 < provoostenator> I wonder what the setup UX would look like if e.g. you had two hardware wallets and wanted such a 2-of-2 or timeout & 1-of-2. 
11:47 < sipa> provoostenator: that's a question for you :)
11:48 < sipa> i'm perfectly fine with psbt rpcs :P
11:48 < instagibbs> gui coin control tho
11:48 < achow101> sipa: replacing the signer with miniscript would probably be a good time to also distinguish between signing and finalizing
11:48 < sipa> achow101: hmm?
11:48 < provoostenator> Right, I guess there would be an RPC where you give it a meta-descriptor or miniscript, then it goes and fetches xpubs from both devices in sequence and imports the right descriptors 
11:49 < provoostenator> Plus asking some sanity check questions to the driver like "can you sign stuff with nlocktime"
11:49 < achow101> ProduceSignature makes both the signature and scriptSig/witness
11:49 < instagibbs> provoostenator, the descriptor will be parsed into miniscript, afaik
11:49 < sipa> provoostenator: the workflow is that you'd use the miniscript compiler to convert a policy to a descriptor
11:49 < instagibbs> ^
11:49 < sipa> and then import the descriptor
11:49 < instagibbs> yeah
11:49 < sipa> the compiler could be built-in, but doesn't need to be
11:49 < provoostenator> Do you put xpubs in the miniscript or does that happen later?
11:50 < achow101> But under the psbt model, those should be distinct.
11:50 < sipa> provoostenator: yeah
11:50 < sipa> the compiler just passes those though, i imagine
11:50 < sipa> (miniscript is just the name of the subset of script; i use "policy" language to refer to the input of the compiler)
11:51 < sipa> i know, i suck at naming things
11:51 < sipa> and this is genuinely confusing because there are several things that look kinda similar
11:51 < provoostenator> signerfetchkeys "miniscript with rules $device_fingerprint_1  $device_fingerprint_1"
11:51 < sipa> achow101: yeah, i guess it can simplify things if we split up the signer and finalizer in the code too
11:51 < provoostenator> Piece of cake
11:54 < meshcollider> Is there anything else anyone wants to talk about in the last few minutes
11:58 < meshcollider> #endmeeting
11:58 < lightningbot> Meeting ended Fri Mar  1 19:58:53 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
11:58 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-03-01-19.00.html
11:58 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-03-01-19.00.txt
11:58 < lightningbot> Log:            http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-03-01-19.00.log.html
12:01 -!- ExtraCrispy [~ExtraCris@gateway/tor-sasl/extracrispy] has quit [Remote host closed the connection]
12:02 -!- ExtraCrispy [~ExtraCris@gateway/tor-sasl/extracrispy] has joined #bitcoin-core-dev
12:12 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 244 seconds]
12:13 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev
12:21 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has quit [Quit: (https://github.com/mmgen) leaving]
12:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
12:55 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
12:59 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev
12:59 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds]
13:11 -!- ccxp [32c810d2@gateway/web/freenode/ip.50.200.16.210] has joined #bitcoin-core-dev
13:11 -!- ccxp [32c810d2@gateway/web/freenode/ip.50.200.16.210] has quit [Client Quit]
13:11 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 250 seconds]
13:13 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev
13:34 -!- schmidty_ [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Remote host closed the connection]
13:37 -!- baldur [~baldur@pool-108-30-43-45.nycmny.fios.verizon.net] has quit [Remote host closed the connection]
13:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
13:38 -!- baldur [~baldur@pool-108-30-43-45.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
13:41 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev
13:41 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host]
13:41 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
13:45 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 244 seconds]
13:50 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
13:56 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
13:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 268 seconds]
13:58 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
14:12 -!- kexkey [~kexkey@139.28.218.30] has joined #bitcoin-core-dev
14:12 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
14:16 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 250 seconds]
14:19 -!- DougieBot5000_ is now known as DougieBot5000
14:19 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #bitcoin-core-dev
14:30 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
14:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 245 seconds]
14:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
14:36 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
14:37 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 268 seconds]
14:44 -!- mariorz_ [sid490@gateway/web/irccloud.com/x-wrryyyxngcdrrfdk] has joined #bitcoin-core-dev
14:44 -!- noganoo_ [sid146237@gateway/web/irccloud.com/x-cnnxynbvgxpepuwq] has joined #bitcoin-core-dev
14:44 -!- gleb_ [sid306870@gateway/web/irccloud.com/x-ndymmarbzfcghhgg] has joined #bitcoin-core-dev
14:45 -!- bosma_ [sid103570@gateway/web/irccloud.com/x-qtxdmslhsxkwbdph] has joined #bitcoin-core-dev
14:45 -!- nejon_ [sid38993@gateway/web/irccloud.com/x-vorysjzfdukpjbuh] has joined #bitcoin-core-dev
14:46 -!- pierre_rochard_ [sid299882@gateway/web/irccloud.com/x-njqrvvzbfnfanpgg] has joined #bitcoin-core-dev
14:46 -!- kallewoof_ [~quassel@240d:1a:759:6000:a7b1:451a:8874:e1ac] has joined #bitcoin-core-dev
14:47 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
14:51 -!- cncr04s_ [~cncr04s@2605:3800:2:1:a:f:c:1] has joined #bitcoin-core-dev
14:52 -!- BlueMatt_ [~BlueMatt@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
14:52 -!- Netsplit *.net <-> *.split quits: pierre_rochard, cncr04s, kallewoof, bosma, x4b1d, BlueMatt, nejon, mariorz, gleb, noganoo
14:52 -!- pierre_rochard_ is now known as pierre_rochard
14:52 -!- noganoo_ is now known as noganoo
14:52 -!- nejon_ is now known as nejon
14:52 -!- mariorz_ is now known as mariorz
14:52 -!- bosma_ is now known as bosma
14:55 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 255 seconds]
14:55 -!- cncr04s_ [~cncr04s@2605:3800:2:1:a:f:c:1] has quit [Client Quit]
14:56 -!- Netsplit over, joins: cncr04s
14:56 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 255 seconds]
14:56 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has quit [Ping timeout: 255 seconds]
14:57 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
14:57 -!- nullptr| [~nullptr|@ip-94-112-134-45.net.upcbroadband.cz] has joined #bitcoin-core-dev
14:59 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
14:59 -!- x4b1d [~nobody@unaffiliated/x4b1d] has joined #bitcoin-core-dev
15:03 -!- timothy [~tredaelli@redhat/timothy] has quit [Remote host closed the connection]
15:17 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Remote host closed the connection]
15:17 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
15:20 -!- kexkey [~kexkey@139.28.218.30] has quit [Quit: Scaling pentatonically]
15:37 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
15:39 -!- jarthur [~jarthur@207.114.244.5] has quit []
15:40 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
15:43 -!- zhangzf [~zhangzf@223.72.72.125] has joined #bitcoin-core-dev
15:45 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 244 seconds]
16:02 -!- zhangzf [~zhangzf@223.72.72.125] has quit [Remote host closed the connection]
16:02 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev
16:07 -!- zhangzf [~zhangzf@223.72.67.223] has joined #bitcoin-core-dev
16:07 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Ping timeout: 246 seconds]
16:11 -!- zhangzf [~zhangzf@223.72.67.223] has quit [Remote host closed the connection]
16:17 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.4]
16:23 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Remote host closed the connection]
16:24 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has joined #bitcoin-core-dev
16:27 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds]
16:28 -!- captjakk [~captjakk@63-238-229-186.dia.static.qwest.net] has quit [Ping timeout: 255 seconds]
16:29 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev
16:39 -!- zhangzf [~zhangzf@223.72.54.150] has joined #bitcoin-core-dev
16:42 -!- jarthur [~jarthur@2605:6000:1019:41ab:8e7:8c87:d373:aa48] has joined #bitcoin-core-dev
16:45 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #bitcoin-core-dev
16:50 -!- pinheadmz [~matthewzi@104-56-112-203.lightspeed.sntcca.sbcglobal.net] has quit [Quit: pinheadmz]
16:55 -!- zhangzf [~zhangzf@223.72.54.150] has quit [Ping timeout: 245 seconds]
16:56 -!- zhangzf [~zhangzf@120.244.115.85] has joined #bitcoin-core-dev
17:03 -!- kexkey [~kexkey@139.28.218.30] has joined #bitcoin-core-dev
17:14 -!- kexkey_ [~kexkey@139.28.218.30] has joined #bitcoin-core-dev
17:15 -!- kexkey [~kexkey@139.28.218.30] has quit [Ping timeout: 240 seconds]
17:37 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
17:48 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Read error: No route to host]
17:49 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
17:57 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
18:19 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has quit [Ping timeout: 245 seconds]
18:31 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection]
18:32 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
18:35 -!- mn949588 [~nodebot@cpe-67-243-201-127.nyc.res.rr.com] has joined #bitcoin-core-dev
18:37 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 250 seconds]
19:05 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 245 seconds]
19:07 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
19:12 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 250 seconds]
19:23 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev
19:27 -!- TheRec [~toto@drupal.org/user/146860/view] has quit [Read error: Connection reset by peer]
19:28 -!- TheRec [~toto@drupal.org/user/146860/view] has joined #bitcoin-core-dev
19:31 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
19:35 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 255 seconds]
19:48 -!- choince [d3da1ead@gateway/web/freenode/ip.211.218.30.173] has joined #bitcoin-core-dev
19:52 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev
20:11 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit []
20:16 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
20:20 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 245 seconds]
20:22 -!- harding [~quassel@li1258-130.members.linode.com] has quit [Ping timeout: 258 seconds]
20:23 -!- harding [~quassel@li1258-130.members.linode.com] has joined #bitcoin-core-dev
20:26 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
20:30 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 250 seconds]
20:38 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.4]
20:54 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
21:13 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev
21:49 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection]
22:27 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev
22:27 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
22:32 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 245 seconds]
22:35 -!- oharvey20 [~oharvey@78.192.54.215] has joined #bitcoin-core-dev
22:35 < oharvey20> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:36 -!- oharvey20 [~oharvey@78.192.54.215] has quit [Read error: Connection reset by peer]
22:37 -!- darkmage6 [~darkmage@46.221.115.42] has joined #bitcoin-core-dev
22:37 < darkmage6> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:37 -!- darkmage6 [~darkmage@46.221.115.42] has quit [Read error: Connection reset by peer]
22:37 -!- wloncom [~wloncom@zaqd37cc3f8.zaq.ne.jp] has joined #bitcoin-core-dev
22:37 < wloncom> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:38 -!- vhasi22 [~vhasi@114.200.238.35] has joined #bitcoin-core-dev
22:38 < vhasi22> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:38 -!- wloncom [~wloncom@zaqd37cc3f8.zaq.ne.jp] has quit [Remote host closed the connection]
22:38 -!- vhasi22 [~vhasi@114.200.238.35] has quit [Read error: Connection reset by peer]
22:39 -!- Al_lA [~Al_lA@82-64-69-79.subs.proxad.net] has joined #bitcoin-core-dev
22:39 < Al_lA> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:39 -!- Al_lA [~Al_lA@82-64-69-79.subs.proxad.net] has quit [Remote host closed the connection]
22:45 -!- zig [~zig@118.33.59.124] has joined #bitcoin-core-dev
22:45 < zig> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:45 -!- zig [~zig@118.33.59.124] has quit [Killed (Sigyn (Spam is off topic on freenode.))]
22:45 < fanquake> sipa / wumpus / luke-jr ^ 
22:46 -!- lithammer [~lithammer@49.143.119.71] has joined #bitcoin-core-dev
22:46 < lithammer> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:46 -!- lithammer [~lithammer@49.143.119.71] has quit [Remote host closed the connection]
22:52 < gwillen> fwiw I am a relatively experienced chanop, an op in #bitcoin and related channels, highlight on ! ops, and willing to ban people who need it, should this channel be desirous of more ops
22:53 < gwillen> although it seems that the network is mostly taking care of these particular ones as they appear
22:54 -!- alephnull2 [~alephnull@66-215-56-59.dhcp.gvrb.ca.charter.com] has joined #bitcoin-core-dev
22:54 < alephnull2> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:54 -!- alephnull2 [~alephnull@66-215-56-59.dhcp.gvrb.ca.charter.com] has quit [Killed (Sigyn (Spam is off topic on freenode.))]
22:58 -!- jimmysong_ [~jimmysong@72-48-253-51.dyn.grandenetworks.net] has quit [Read error: Connection reset by peer]
22:58 -!- mode/#bitcoin-core-dev [+o fanquake] by ChanServ
22:59 -!- jimmysong_ [~jimmysong@72-48-253-51.dyn.grandenetworks.net] has joined #bitcoin-core-dev
22:59 -!- bvitnik8 [~bvitnik@175.119.97.226] has joined #bitcoin-core-dev
22:59 < bvitnik8> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
22:59 < luke-jr> fanquake: I don't see a good ban mask that would work :/
22:59 -!- mode/#bitcoin-core-dev [+o luke-jr] by ChanServ
22:59 -!- bvitnik8 was kicked from #bitcoin-core-dev by luke-jr [User terminated!]
22:59 -!- mode/#bitcoin-core-dev [+o gwillen] by ChanServ
23:00 <@gwillen> I think this is a legit botnet unfortunately, so there probably isn't one
23:00 <@gwillen> it's targeting freenode, not us
23:00 <@luke-jr> I suppose if it gets bad enough, we can just set the channel to only allow registered users : /
23:01 <@gwillen> a temporary +i, +k, +r would work
23:01 <@gwillen> yeah
23:01 <@gwillen> I would suggest setting +r for a few hours and then taking it off
23:02 <@gwillen> but also, spam in the middle of the night is really only messing up scrollback, so maybe it's not worth it
23:03 < gmaxwell> it's pretty harmless overall. 
23:03 < gmaxwell> you can quiet unregisterd, though people tend to forget to turn it off
23:03 <@gwillen> *nods*
23:04 <@gwillen> elsewhere I have done "ban unregistered with exemptions" but that seems unmanageable at the size of this channel
23:10 -!- poopster17 [~poopster@177.53.136.196] has joined #bitcoin-core-dev
23:10 < poopster17> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
23:10 -!- poopster17 was kicked from #bitcoin-core-dev by luke-jr [User terminated!]
23:13 -!- distantorigin [~distantor@200.34.248.19] has joined #bitcoin-core-dev
23:13 < distantorigin> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
23:13 -!- distantorigin was kicked from #bitcoin-core-dev by luke-jr [User terminated!]
23:14 <@luke-jr> hm, if they only post one message, kicking may not be useful
23:14 <@luke-jr> how do we quiet unregistereds?
23:16 <@gwillen> let me find the syntax for that
23:16 <@gwillen>  +q $~a
23:18 -!- nightfrog28 [~nightfrog@125.42.237.222] has joined #bitcoin-core-dev
23:18 < nightfrog28> read about the new exciting pedo-friendly linux distribution https://exherbo.com/
23:19 -!- mode/#bitcoin-core-dev [+q $~a] by luke-jr
23:19 <@luke-jr> gwillen: ops still see messages, right? so if someone wants to talk, we can make the exception?
23:20 -!- Jbain_ [~Jbain_@111.165.134.148] has joined #bitcoin-core-dev
23:20 -!- Jbain_ [~Jbain_@111.165.134.148] has quit [Remote host closed the connection]
23:20 -!- mode/#bitcoin-core-dev [+z] by gwillen
23:20 <@gwillen> now we do
23:20 <@gwillen> (this is what +z does)
23:21 -!- justinmoon [~manjaro-i@cpe-70-113-80-71.austin.res.rr.com] has quit [Ping timeout: 240 seconds]
23:21 <@luke-jr> cool
23:21 <@gwillen> only people with channel mode +o though (@), not people with chanserv access
23:22 -!- nightfrog28 [~nightfrog@125.42.237.222] has quit [Ping timeout: 250 seconds]
23:33 -!- silverwhitefish [~silverwhi@103.98.191.75] has joined #bitcoin-core-dev
23:33 -!- silverwhitefish [~silverwhi@103.98.191.75] has quit [Killed (Sigyn (Spam is off topic on freenode.))]
23:56 -!- pinheadmz [~matthewzi@c-76-102-227-220.hsd1.ca.comcast.net] has quit [Quit: pinheadmz]
23:58 -!- loceur11 [~loceur@pool-109-191-167-171.is74.ru] has joined #bitcoin-core-dev
23:59 -!- loceur11 [~loceur@pool-109-191-167-171.is74.ru] has quit [Killed (Sigyn (Spam is off topic on freenode.))]
--- Log closed Sat Mar 02 00:00:05 2019