--- Day changed Tue Dec 20 2016 00:05 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 00:06 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:06 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 00:11 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 260 seconds] 00:13 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 00:19 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Ping timeout: 245 seconds] 00:24 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving] 00:25 -!- JackH [~laptop@79-73-186-204.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev 00:27 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:27 -!- molz [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer] 00:28 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 00:32 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #bitcoin-core-dev 00:39 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:42 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 246 seconds] 01:27 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 01:35 -!- otium [~otium@2a01:e35:2eeb:c00:bdc2:3c15:6b70:5e5e] has joined #bitcoin-core-dev 01:40 -!- e4xit [~e4xit@cpc1-cmbg20-2-0-cust188.5-4.cable.virginm.net] has quit [Read error: Connection reset by peer] 01:42 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 01:42 -!- e4xit [~e4xit@cpc1-cmbg20-2-0-cust188.5-4.cable.virginm.net] has joined #bitcoin-core-dev 01:58 -!- kallle [~kallle@124x35x83x162.ap124.ftth.ucom.ne.jp] has joined #bitcoin-core-dev 02:15 < wumpus> tagged #9212 02:15 < gribble> https://github.com/bitcoin/bitcoin/issues/9212 | Assertion failed: (nSendVersion != 0), function GetSendVersion, file ./net.h, line 775. · Issue #9212 · bitcoin/bitcoin · GitHub 02:22 -!- otium [~otium@2a01:e35:2eeb:c00:bdc2:3c15:6b70:5e5e] has left #bitcoin-core-dev ["..."] 02:27 -!- chris2000 [~chris2000@p5DCB5E6D.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 02:30 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7f72568e6b15...3097ea40d719 02:30 < bitcoin-git> bitcoin/master faf4ca8 MarcoFalke: [wallet] Disable free transactions when relay is disabled 02:30 < bitcoin-git> bitcoin/master 3097ea4 Wladimir J. van der Laan: Merge #9316: [wallet] Disable free transactions when relay is disabled... 02:30 -!- chris200_ [~chris2000@p5DCB4634.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 02:30 < bitcoin-git> [bitcoin] laanwj closed pull request #9316: [wallet] Disable free transactions when relay is disabled (master...Mf1612-sendFreeNo) https://github.com/bitcoin/bitcoin/pull/9316 02:40 -!- MarcoFalke_web [8af602fa@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.250] has joined #bitcoin-core-dev 02:59 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev 03:09 < btcdrak> wumpus: now that instagibbs addressed the maps nit in 9262, is it mergeable? 03:10 < btcdrak> i backported it aswell 03:23 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 03:31 -!- chris200_ [~chris2000@p5DCB560C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:34 -!- chris2000 [~chris2000@p5DCB5E6D.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 03:34 -!- chris20__ [~chris2000@p5DCB5A3C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:37 -!- chris200_ [~chris2000@p5DCB560C.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 03:37 -!- chris2000 [~chris2000@p5082A35D.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:39 -!- chris20__ [~chris2000@p5DCB5A3C.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 03:41 -!- chris200_ [~chris2000@p5DCB5E36.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:42 -!- chris2000 [~chris2000@p5082A35D.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 03:43 -!- chris2000 [~chris2000@p5DCB54C1.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:46 -!- chris200_ [~chris2000@p5DCB5E36.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds] 03:50 -!- jtimon [~quassel@231.110.132.37.dynamic.jazztel.es] has quit [Ping timeout: 265 seconds] 04:08 -!- cjamthagen [~user@h-88-153.a230.priv.bahnhof.se] has joined #bitcoin-core-dev 04:12 < wumpus> btcdrak: yes. I think so 04:13 -!- chris200_ [~chris2000@p5DCB4788.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 04:15 -!- chris2000 [~chris2000@p5DCB54C1.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 04:16 -!- chris2000 [~chris2000@p5DCB56DB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 04:16 -!- cjamthagen [~user@h-88-153.a230.priv.bahnhof.se] has left #bitcoin-core-dev ["WeeChat 1.0.1"] 04:18 -!- chris200_ [~chris2000@p5DCB4788.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds] 04:18 -!- chris200_ [~chris2000@p5DCB47AF.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 04:21 -!- chris20__ [~chris2000@p5082A8D2.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 04:21 -!- chris2000 [~chris2000@p5DCB56DB.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 04:24 -!- chris200_ [~chris2000@p5DCB47AF.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 04:25 -!- cjamthagen [~user@h-88-153.a230.priv.bahnhof.se] has joined #bitcoin-core-dev 04:27 -!- kallle [~kallle@124x35x83x162.ap124.ftth.ucom.ne.jp] has quit [Remote host closed the connection] 04:27 < bitcoin-git> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/3097ea40d719...5a70572049d0 04:27 < bitcoin-git> bitcoin/master 0b2294a Gregory Sanders: SelectCoinsMinConf: Prefer coins with fewer ancestors 04:27 < bitcoin-git> bitcoin/master 5882c09 Gregory Sanders: CreateTransaction: Don't return success with too-many-ancestor txn 04:27 < bitcoin-git> bitcoin/master af9bedb Gregory Sanders: Test for fix of txn chaining in wallet 04:27 < bitcoin-git> [bitcoin] laanwj closed pull request #9262: Prefer coins that have fewer ancestors, sanity check txn before ATMP (master...toolong) https://github.com/bitcoin/bitcoin/pull/9262 04:33 < bitcoin-git> [bitcoin] laanwj closed pull request #9382: [backport 0.13] Prefer coins that have fewer ancestors, sanity check txn before ATMP (0.13...backport9262) https://github.com/bitcoin/bitcoin/pull/9382 04:36 < bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.13: https://github.com/bitcoin/bitcoin/commit/8e707e868d6020de0d352279eed4fcd0138f3695 04:36 < bitcoin-git> bitcoin/0.13 8e707e8 Wladimir J. van der Laan: doc: Add #9382 to release notes 04:43 < wumpus> will label 0.13.2rc1 in a bit - doing last-minute checks 04:46 -!- jtimon [~quassel@231.110.132.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 04:56 < btcdrak> wumpus: exciting :) 04:56 < rabidus_> nice 04:57 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 05:03 < jtimon> yeah, nice 05:22 < wumpus> * [new tag] v0.13.2rc1 -> v0.13.2rc1 05:24 < btcdrak> \o/ 05:26 -!- BonyM1 [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has quit [Ping timeout: 260 seconds] 05:27 < instagibbs> woohoo 05:28 < thrasher`> nice :D 05:32 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has joined #bitcoin-core-dev 05:33 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has joined #bitcoin-core-dev 05:40 -!- BonyM1 [~BonyM-I@ua-83-227-211-4.cust.bredbandsbolaget.se] has joined #bitcoin-core-dev 05:41 -!- jjkklll [4e302514@gateway/web/freenode/ip.78.48.37.20] has quit [Ping timeout: 260 seconds] 05:43 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 05:45 -!- kadoban [~mud@unaffiliated/kadoban] has joined #bitcoin-core-dev 05:46 -!- MarcoFalke_web [8af602fa@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.250] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 05:47 -!- MarcoFalke_web [8af602fa@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.250] has joined #bitcoin-core-dev 05:47 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Ping timeout: 250 seconds] 05:56 -!- alpalp [~alpalp@unaffiliated/alpalp] has quit [Ping timeout: 258 seconds] 06:06 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Ping timeout: 250 seconds] 06:23 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 06:27 -!- Lauda [~quassel@unaffiliated/lauda] has quit [Ping timeout: 250 seconds] 06:50 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 06:56 < bitcoin-git> [bitcoin] rebroad opened pull request #9388: Relative time (master...RelativeTime) https://github.com/bitcoin/bitcoin/pull/9388 07:20 -!- wvr [~wvr@215.red-83-59-62.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 07:42 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 07:43 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 07:44 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 07:47 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 246 seconds] 07:48 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Ping timeout: 245 seconds] 08:19 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:51 -!- abpa [~abpa@96-82-80-25-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 08:52 -!- chris2000 [~chris2000@p5082A8AB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 08:55 -!- chris200_ [~chris2000@p5DCB4837.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 08:55 -!- chris20__ [~chris2000@p5082A8D2.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 08:57 -!- chris2000 [~chris2000@p5082A8AB.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 08:57 -!- chris2000 [~chris2000@p5DCB440A.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 09:00 -!- chris200_ [~chris2000@p5DCB4837.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 09:05 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 09:06 -!- chris200_ [~chris2000@p5DCB4B39.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 09:09 -!- chris2000 [~chris2000@p5DCB440A.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 09:09 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 09:10 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Ping timeout: 256 seconds] 09:48 < achow101> eh, a tag. I'm late to the party! 09:49 < MarcoFalke_web> first matching sig! 09:57 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 10:04 -!- JackH [~laptop@79-73-186-204.dynamic.dsl.as9105.com] has quit [Ping timeout: 258 seconds] 10:20 -!- chris2000 [~chris2000@p5082AFBF.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:22 -!- chris200_ [~chris2000@p5DCB4B39.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 10:22 -!- chris20__ [~chris2000@p5082A196.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:25 -!- chris2000 [~chris2000@p5082AFBF.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 10:25 -!- chris200_ [~chris2000@p5082A5F5.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:26 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 10:28 -!- chris2000 [~chris2000@p5DCB4882.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:28 -!- chris20__ [~chris2000@p5082A196.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 10:30 -!- Lauda [~quassel@unaffiliated/lauda] has joined #bitcoin-core-dev 10:30 -!- chris200_ [~chris2000@p5082A5F5.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 10:31 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 10:31 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Ping timeout: 264 seconds] 10:39 -!- chris200_ [~chris2000@p5DCB5192.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:42 -!- chris20__ [~chris2000@p5DCB400F.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 10:42 -!- chris2000 [~chris2000@p5DCB4882.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 10:45 -!- chris200_ [~chris2000@p5DCB5192.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 10:54 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 10:55 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 10:59 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has joined #bitcoin-core-dev 11:08 -!- paveljanik [~paveljani@79.98.72.176] has joined #bitcoin-core-dev 11:08 -!- paveljanik [~paveljani@79.98.72.176] has quit [Changing host] 11:08 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev 11:10 < jtimon> I would really welcome help from experts on ./rpc-tests/segwit.py or ./rpc-tests/p2p-compactblocks.py I really can't understand why changing the genesis block of regtests should be an issue or how can I correct it or find my error 11:17 < jtimon> sorry, I'm talking about #8994 again, which changes all rpc/py tests from "regtest" to "custom" (the tests should be identical except for the genesis block, those 2 tests resist) 11:17 < gribble> https://github.com/bitcoin/bitcoin/issues/8994 | Testchains: Introduce custom chain whose constructor... by jtimon · Pull Request #8994 · bitcoin/bitcoin · GitHub 11:19 -!- chris2000 [~chris2000@p5082A4F9.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:21 -!- chris20__ [~chris2000@p5DCB400F.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 11:22 -!- chris200_ [~chris2000@p5082A370.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:24 -!- chris2000 [~chris2000@p5082A4F9.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 11:24 -!- chris2000 [~chris2000@p5DCB557F.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:27 -!- chris200_ [~chris2000@p5082A370.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 11:28 -!- chris200_ [~chris2000@p5DCB40F2.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:30 -!- chris2000 [~chris2000@p5DCB557F.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds] 11:30 -!- chris2000 [~chris2000@p5DCB4F2E.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:33 -!- chris200_ [~chris2000@p5DCB40F2.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds] 11:33 -!- chris200_ [~chris2000@p5082AF02.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:36 -!- chris2000 [~chris2000@p5DCB4F2E.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds] 11:38 -!- chris2000 [~chris2000@p5082AD4E.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:39 -!- chris200_ [~chris2000@p5082AF02.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds] 11:41 -!- chris200_ [~chris2000@p5082AAB8.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:43 -!- chris2000 [~chris2000@p5082AD4E.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 11:44 -!- chris20__ [~chris2000@p5082A60F.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:46 -!- chris2000 [~chris2000@p5DCB4BBD.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:46 -!- chris200_ [~chris2000@p5082AAB8.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 11:48 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 11:49 -!- chris20__ [~chris2000@p5082A60F.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 11:51 -!- chris200_ [~chris2000@p5082A40E.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:52 -!- chris2000 [~chris2000@p5DCB4BBD.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 11:52 -!- chris2000 [~chris2000@p5DCB532C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:52 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Ping timeout: 268 seconds] 11:55 -!- chris20__ [~chris2000@p5DCB574C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 11:55 -!- chris200_ [~chris2000@p5082A40E.dip0.t-ipconnect.de] has quit [Ping timeout: 250 seconds] 11:56 < instagibbs> jtimon, what error are you getting 11:57 < jtimon> in each of them, one test is failing, let me go back to what line was failing on each 11:57 -!- chris2000 [~chris2000@p5DCB532C.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 12:00 -!- chris200_ [~chris2000@p5DCB5909.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:00 -!- chris20__ [~chris2000@p5DCB574C.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 12:02 -!- chris20__ [~chris2000@p5082A962.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:05 -!- chris200_ [~chris2000@p5DCB5909.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 12:06 -!- chris2000 [~chris2000@p5DCB50F5.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:08 -!- chris20__ [~chris2000@p5082A962.dip0.t-ipconnect.de] has quit [Ping timeout: 260 seconds] 12:08 -!- chris200_ [~chris2000@p5DCB4B4C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:10 -!- chris2000 [~chris2000@p5DCB50F5.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds] 12:10 -!- chris2000 [~chris2000@p5082AC5A.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:13 -!- chris20__ [~chris2000@p5082AA5B.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:13 -!- chris200_ [~chris2000@p5DCB4B4C.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 12:15 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has quit [Ping timeout: 252 seconds] 12:16 -!- chris200_ [~chris2000@p5DCB5ED9.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:16 -!- chris2000 [~chris2000@p5082AC5A.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 12:17 -!- instagibbs [~instagibb@pool-100-15-114-3.washdc.fios.verizon.net] has joined #bitcoin-core-dev 12:18 < gmaxwell> \O/ hurray about the RC. 12:19 -!- chris20__ [~chris2000@p5082AA5B.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds] 12:19 < instagibbs> jtimon, please give more info thanks 12:20 < jtimon> oh, sorry, I forgot 12:21 -!- chris2000 [~chris2000@p5082A469.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 12:23 < jtimon> in segwit.py the first error is in L428, in L844 12:23 < jtimon> in segwit.py the first error is in L428, in qa/rpc-tests/p2p-compactblocks.py in L844 12:23 -!- chris200_ [~chris2000@p5DCB5ED9.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds] 12:25 < jtimon> in all the rest everything seems to be working fine, my fear is omse of them aren't calling setup_chain() 12:26 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 12:26 < jtimon> in segwit.py the error is "missing inputs", my guess is that the tests are somehow using regtest genesis block instead of the custom chain one 12:27 < MarcoFalke_web> Does the new chain work with the caching in the python tests? 12:28 < MarcoFalke_web> looking at your pull, it should 12:30 < jtimon> the custom chain should be completely identical for regtest and custom by default expect for the genesis block 12:32 < jtimon> mhmm, this commit says I need to fix p2p-segwit too...https://github.com/bitcoin/bitcoin/pull/8994/commits/8e3de77110892e3684a9cb98ced9c9129997257c 12:33 < jtimon> ideally, that commit would only touch test_framework.py and be squashed somewhere 12:37 < jtimon> I'm pretty convinced it has something to do with the mininodes, but there still some chain-dependent code I'm looking fore 12:40 < cfields> gitian builders: detached sigs for 0.13.2rc1 pushed. 12:40 < timothy> hi, I have a slightly question. I'm trying to integrate bitcoin with tor under docker 12:40 < timothy> it works, but unlucky -proxy and -torcontrol doesn't support hostnames, but only IPs and this doesn't work under docker-compose 12:41 < gmaxwell> the tor support in Bitcoin Core really intends the tor daemon to be on localhost. 12:41 < gmaxwell> if it's on another host right now it will end up banning the tor host. 12:41 < timothy> well, it works also if you have the tor daemon on another host, but I need to specify the ip :P 12:41 < gmaxwell> It doesn't work for long. 12:42 < timothy> ok, wrong idea. thank you :) 12:42 < sipa> -proxy certainly accepts IP addresses 12:43 < gmaxwell> hopefully we'll fix that in an upcoming version. 12:43 < gmaxwell> sipa: yes, outbound would be fine. 12:44 < jtimon> right, for simple proxies an env variable for docker may be enough 12:44 < gmaxwell> Proxy won't take a hostname? 12:45 < btcdrak> I dont mean to be a stick in the mud, but why are merge commits not signed in the gitian.sigs repository? 12:45 < MarcoFalke_web> What would it help? 12:45 < sipa> gmaxwell: seems it doesn't 12:45 < jtimon> no, but environment variable would give the ip, no? I'm not really sure what he is trying to do so probably I shouldn't talk 12:45 < gmaxwell> lol, gitian sigs are already sigs. 12:46 < MarcoFalke_web> btcdrak: Your linux has a mismatch 12:46 < btcdrak> MarcoFalke_web: just the linux one? 12:46 < MarcoFalke_web> jup 12:46 < btcdrak> weird. 12:50 -!- MarcoFalke [~marco@2001:4ca0:0:f226:a063:75b:7f88:d780] has joined #bitcoin-core-dev 13:01 < gmaxwell> A request for 0.13rc2 testers: Please run ./qa/pull-tester/rpc-tests.py ... we have this fantastic test suite and I get the impression that a lot of people only use it via travis. If there are bad interactions with your system and the software these tests are probably more likely to reveal them then just your local testing alone. 13:49 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9389: 0.13.2 release process (0.13...Mf1612-01302Bump) https://github.com/bitcoin/bitcoin/pull/9389 13:55 < achow101> a bunch of tests just failed for me 13:56 < instagibbs> achow101, make sure you don't have zombie processes or cache folder lying around 13:56 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9390: travis: make distdir (master...Mf1612-travisDistDir) https://github.com/bitcoin/bitcoin/pull/9390 13:56 < achow101> I'm gitian building at the same time, so that might be interfering with something too 13:56 < MarcoFalke> Could be also OOM 13:57 < achow101> could be 14:05 < morcos> sipa: i've spent too long confused by move semantics already today, but i think there is an easily fixable potential bug... can you take a quick look 14:05 < morcos> in wallet.cpp under the logic for -walletrejectlongchains 14:05 < morcos> hasn't txNew been moved from? 14:06 < sipa> what line? 14:06 < morcos> search for walletrejectlongchains, i'm not on master 14:06 < morcos> right under that 14:08 < morcos> sorry second occurence, line 2566 14:08 < sipa> yup 14:08 < sipa> i wonder how that code works at all 14:08 < morcos> thats what i mean by confused 14:09 < morcos> i made the same error myself on some other wallet code i was working on earlier 14:09 < sipa> txNew in practice will just have empty txin and txout 14:10 < morcos> same bug in 0.13.2 14:10 < morcos> if you don't mind taking it from here.. i have a couple things i'm rushing to finish before dinner 14:11 < morcos> but out of curiousity, why is that such an easy mistake to make? shouldn't there be a compiler warning or something 14:12 < sipa> there can't be 14:12 < sipa> well, it could be a suggestion 14:12 < sipa> but in general, use after move is well defined 14:22 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9391: wallet: Remove sendfree (master...Mf1612-015walletSendFreeNONO) https://github.com/bitcoin/bitcoin/pull/9391 14:23 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 14:28 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Ping timeout: 265 seconds] 14:52 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 14:53 < gmaxwell> rc1 appears to be reporting "subver": "/Satoshi:0.13.1/", 14:57 < sipa> see #9389 14:57 < gribble> https://github.com/bitcoin/bitcoin/issues/9389 | 0.13.2 release process by MarcoFalke · Pull Request #9389 · bitcoin/bitcoin · GitHub 14:58 < gmaxwell> heh just went and made most of those changes.. should have paid more attention. 15:24 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 15:30 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Ping timeout: 258 seconds] 15:42 < achow101> for what reasons would core close a connection to another node besides shutdown on one side? 15:45 < phantomcircuit> achow101, various protocol violations which are eggregious 15:46 < achow101> would a getdata message with the segwit flags (msg_witness_tx, etc) cause that right now since segwit is not activated? 15:46 < achow101> also, would such a disconnect show up in the debug.log? 15:52 -!- MykelSIlver [~MykelSIlv@192-228-145-85.ftth.glasoperator.nl] has joined #bitcoin-core-dev 15:57 < BlueMatt> before anyone freaks out, no, I think #9392 is 0.14.0 tag not 0.13.2, as mentioned in the review of 9262 15:57 < gribble> https://github.com/bitcoin/bitcoin/issues/9392 | Wallet ancestor sanity-check ignores sigops · Issue #9392 · bitcoin/bitcoin · GitHub 15:59 < achow101> what's up with these 0.13.1 nodes with short sendcmpct messages? 16:06 < sipa> 15:46:28 < achow101> would a getdata message with the segwit flags (msg_witness_tx, etc) cause that right now since segwit is not activated? 16:06 < sipa> i don't think so 16:06 < gmaxwell> BlueMatt: yea, well I think that improvement is boring. 16:06 < sipa> if it's an incoming connection, it may just be evicted 16:06 < gmaxwell> BlueMatt: I really do not believe anyone has ever had a tx they created fail due to excessive sigops. 16:07 < BlueMatt> gmaxwell: yes, thats pretty much my point 16:07 < gmaxwell> BlueMatt: in fact, I suspect it's not even possible without modifying the software. 16:07 < BlueMatt> gmaxwell: the api refactor, though, needs to happen 16:07 < instagibbs> achow101, I doubt it as well, since usually banning is done for things that are always false, theoretically segwit could have activated and you're partitioned off or something 16:07 < instagibbs> at least, I'd hope not 16:08 < gmaxwell> BlueMatt: I think we should consider changing the behavior so that violation of sigops in a package has no effect on relay, merely prevents a txn from getting package aggregated in the block creation. 16:08 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 16:23 -!- wvr [~wvr@215.red-83-59-62.dynamicip.rima-tde.net] has quit [Quit: Leaving] 16:37 -!- jtimon [~quassel@231.110.132.37.dynamic.jazztel.es] has quit [Ping timeout: 268 seconds] 16:50 -!- alpalp [~alpalp@unaffiliated/alpalp] has joined #bitcoin-core-dev 16:55 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9393: build: Include cuckoocache header in Makefile (master...Mf1612-makeHeader) https://github.com/bitcoin/bitcoin/pull/9393 17:08 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 17:08 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 17:11 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Read error: Connection reset by peer] 17:11 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 17:27 < achow101> any idea what a packet of length 8 would be? I'm trying to debug something in armory and it is receiving data from core that has a length of 8 17:28 < sipa> pong? 17:28 < sipa> or ping 17:29 < achow101> maybe.. I think the data size should also include the message header 17:30 < sipa> the message header is 24 bytes 17:30 < sipa> (magic + command + checksum) 17:30 < achow101> right. well something is coming in from the socket that is 8 bytes 17:30 < sipa> that's possible 17:30 < sipa> you should wait for more data to arrive :) 17:31 < sipa> tcp does not guarantee message boundaries 17:32 < bitcoin-git> [bitcoin] morcos opened pull request #9395: Actually calculate mempool ancestors (master...fixmovedtx) https://github.com/bitcoin/bitcoin/pull/9395 17:32 < morcos> sipa: ok i made the fix 17:33 < morcos> i guess one could argue we don't NEED to fix that for 0.13.2, if you're sure that the behavior is guaranteed to be what you said (vin is empty). Why is that safe to assume? 17:39 < sipa> morcos: the vector move constructor in practice (though not defined by the standard) leaves the argument empty 17:39 < sipa> the standard just says that it needs to be in a valid but unspecified state 17:39 < sipa> but there really is nothing that can be done efficiently that isn't leaving it empty 17:40 < morcos> sipa: but what does a valid state mean? could the entries in the vector be such that it crashed your node when you tried to look at it? 17:40 < sipa> nope 17:40 < sipa> that would not be a valid state 17:40 < morcos> i think its fine if -walletrejectlongchains doesn't work for 0.13.2, as long as you can't crash 17:40 < sipa> well perhaps that code somehow assuming a non-empty vin? 17:41 < morcos> well its not just the vin vector right, its the whole tx 17:42 < sipa> right, but CTransaction is move-constructed from CMutableTransaction, which move-constructs vin and vout from the old vectors 17:43 < sipa> which leaves txNew.vin and txNew.vout empty 17:43 < bitcoin-git> [bitcoin] accraze opened pull request #9396: Updated listsinceblock rpc documentation (master...docs-listsinceblock-rpc) https://github.com/bitcoin/bitcoin/pull/9396 17:44 < gmaxwell> well it's not like we don't have to do an rc2 considering we missed the version bump. 17:45 < morcos> well if we're doing one anyway, i think we should probably include 9395.. will save us at least explaining that the option doesn't actually work 17:45 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has quit [Quit: Whatever] 17:45 < gmaxwell> right. 17:46 < sipa> i'm confused 17:46 < sipa> the CTransaction(CMutableTransaction&& x) constructor is not in 0.13 afaik 17:47 < sipa> nor is MakeTransactionRef 17:48 < morcos> sipa: oh.. oops. i confess i didn't look too closely at 0.13 17:49 < sipa> so the backport is correct 17:49 < sipa> but the version in master is not 17:49 < sipa> irony. 17:49 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 264 seconds] 17:50 < morcos> thats nice! 17:57 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-zreizyygpqzmvcgg] has quit [Quit: Connection closed for inactivity] 18:01 -!- abpa [~abpa@96-82-80-25-static.hfc.comcastbusiness.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 18:05 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 18:16 -!- MarcoFalke [~marco@2001:4ca0:0:f226:a063:75b:7f88:d780] has left #bitcoin-core-dev [] 18:24 -!- MarcoFalke_web [8af602fa@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.250] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client] 18:33 < instagibbs> oops, I likely wrote the pr with working tests for:*static_cast(&wtxNew) = CTransaction(txNew); then it was changed while rebasing 18:36 < instagibbs> yeah timeline for that looks right, my bad 18:36 < instagibbs> Some kind of irony :) 18:55 * luke-jr wonders if it would make sense to have a GUI option for "API Key" that sets up a rpcauth. 18:57 < morcos> instagibbs: yeah i was pretty sure we had tested -walletrejectlongchains 18:59 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds] 19:01 < luke-jr> 0.13.2: should doc/release-notes/ include the 0.13.1 notes? 19:01 < luke-jr> nm ^, had the wrong branch checkout out 19:01 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 19:03 -!- harrymm [~wayne@188.42.223.22] has quit [Remote host closed the connection] 19:05 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 19:06 -!- harrymm [~wayne@188.42.252.254] has joined #bitcoin-core-dev 19:06 < instagibbs> morcos, we did and I got cyberbullied into removing it (jk, your tests are better) 19:14 -!- alpalp [~alpalp@unaffiliated/alpalp] has quit [Ping timeout: 264 seconds] 19:16 < bitcoin-git> [bitcoin] droark closed pull request #9373: Linearize script update (hash byte reversal and Python 3 support) (master...linearize-update) https://github.com/bitcoin/bitcoin/pull/9373 19:23 -!- To7 [~theo@cpe-158-222-222-232.nyc.res.rr.com] has joined #bitcoin-core-dev 19:30 < bitcoin-git> [bitcoin] droark reopened pull request #9373: Linearize script update (hash byte reversal and Python 3 support) (master...linearize-update) https://github.com/bitcoin/bitcoin/pull/9373 19:34 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 19:34 -!- blkdb [~blkdb@2a01:4f8:140:1407::2] has quit [Remote host closed the connection] 19:35 -!- blkdb [~blkdb@2a01:4f8:140:1407::2] has joined #bitcoin-core-dev 20:07 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 20:23 -!- chris200_ [~chris2000@p5082ADBB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 20:26 -!- chris2000 [~chris2000@p5082A469.dip0.t-ipconnect.de] has quit [Ping timeout: 258 seconds] 20:31 -!- PRab_ [~chatzilla@c-68-62-95-247.hsd1.mi.comcast.net] has joined #bitcoin-core-dev 20:32 -!- PRab [~chatzilla@c-68-62-95-247.hsd1.mi.comcast.net] has quit [Ping timeout: 260 seconds] 20:32 -!- PRab_ is now known as PRab 20:56 -!- Sosumi [~Leon@bl10-113-190.dsl.telepac.pt] has quit [Quit: Bye] 21:00 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 21:03 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 21:06 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 21:07 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 21:43 -!- pete [792c47fa@gateway/web/freenode/ip.121.44.71.250] has joined #bitcoin-core-dev 21:44 -!- pete is now known as Guest57013 21:44 -!- Guest57013 [792c47fa@gateway/web/freenode/ip.121.44.71.250] has quit [Client Quit] 21:47 -!- blkdb [~blkdb@2a01:4f8:140:1407::2] has quit [Ping timeout: 260 seconds] 21:48 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 21:55 -!- arowser [~quassel@106.120.101.38] has quit [Read error: Connection reset by peer] 22:01 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev 22:01 -!- arowser [~quassel@106.120.101.38] has quit [Client Quit] 22:02 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev 22:03 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 22:16 -!- blkdb [~blkdb@2a01:4f8:140:1407::2] has joined #bitcoin-core-dev 22:22 < luke-jr> - #9293 `e591c10` [0.13 Backport #9053] IBD using chainwork instead of height and not using header timestamp (gmaxwell) 22:22 < luke-jr> - #9053 `5b93eee` IBD using chainwork instead of height and not using header timestamps (gmaxwell) 22:22 < gribble> https://github.com/bitcoin/bitcoin/issues/9293 | [0.13 Backport] IBD using chainwork instead of height and not using header timestamp (#9053) by gmaxwell · Pull Request #9293 · bitcoin/bitcoin · GitHub 22:22 < luke-jr> ^ redundant? 22:22 < gribble> https://github.com/bitcoin/bitcoin/issues/9053 | IBD using chainwork instead of height and not using header timestamps by gmaxwell · Pull Request #9053 · bitcoin/bitcoin · GitHub 22:22 < gribble> https://github.com/bitcoin/bitcoin/issues/9053 | IBD using chainwork instead of height and not using header timestamps by gmaxwell · Pull Request #9053 · bitcoin/bitcoin · GitHub 22:22 * luke-jr stabs gribble 22:23 < gmaxwell> gribble is just demonstrating redundancy. 22:26 -!- mannu [239a16fe@gateway/web/freenode/ip.35.154.22.254] has joined #bitcoin-core-dev 22:27 < luke-jr> haha 22:27 < mannu> How do I see the incoming transaction in a service 22:27 < mannu> I want to separate out the components ! 22:27 < luke-jr> mannu: using -walletnotify, discuss/ask on #bitcoin 22:30 < mannu> Can I write a blockchain app 22:30 < mannu> rather than developing the bitcore further 22:30 < luke-jr> Bitcore is not the same as Bitcoin Core, and while you can certainly develop other applications, this channel is for developing Bitcoin Core. 22:31 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 22:31 < mannu> Ok ! 22:31 < mannu> Can you help me get started with writing the .js code for txns 22:31 < luke-jr> Myself and many others are in #bitcoin and willing to help when we can. 22:32 < mannu> I have put up the node running ! 22:32 < mannu> luke-jr: How do I get started with writing a service basics 22:32 < mannu> Like how to catch txns 22:32 < mannu> and separate out its components 22:33 < luke-jr> I answered your first question here to be polite, but I will not continue to answer questions here that are off-topic. Move to #bitcoin for asking them. 22:34 < luke-jr> (to do that, type: /join #bitcoin 22:34 < mannu> Ok Thanks 22:34 -!- mannu [239a16fe@gateway/web/freenode/ip.35.154.22.254] has quit [Quit: Page closed] 22:37 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 22:40 -!- kadoban [~mud@unaffiliated/kadoban] has quit [Quit: bye] 22:47 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection] 22:48 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev 22:52 -!- jtimon [~quassel@231.110.132.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 22:54 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 252 seconds] 22:57 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-pyafmkrgqpshfqca] has joined #bitcoin-core-dev 22:59 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 23:00 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 23:00 -!- dermoth [~thomas@dsl-199-102-158-23.mtl.aei.ca] has quit [Read error: Connection reset by peer] 23:01 -!- dermoth [~thomas@dsl-199-102-158-23.mtl.aei.ca] has joined #bitcoin-core-dev 23:04 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 250 seconds] 23:05 < BlueMatt> achow101: earlier you mentioned 5-byte sendcmpct messages.....were they coming from digitalocean-frankfurt? 23:05 < BlueMatt> (not me, but I've been seeing them recently too on something claiming to be /Satoshi:0.13.1/ so curious who the fuck it is) 23:06 < BlueMatt> whoever it is they bothered to set up their shit with the public fibre network (ie put their ip in the whitelist) 23:12 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev 23:27 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has quit [Remote host closed the connection] 23:30 -!- kallle [~kallle@zz2014411797B6F89E81.userreverse.dion.ne.jp] has joined #bitcoin-core-dev 23:33 < bitcoin-git> [bitcoin] laanwj pushed 5 new commits to 0.13: https://github.com/bitcoin/bitcoin/compare/8e707e868d60...b31e13eeb6d9 23:33 < bitcoin-git> bitcoin/0.13 20817ce MarcoFalke: Bump version to 0.13.2 23:33 < bitcoin-git> bitcoin/0.13 7a26a34 MarcoFalke: Bump nMinimumChainWork 23:33 < bitcoin-git> bitcoin/0.13 3882c05 MarcoFalke: [qt] Bump BLOCK_CHAIN_SIZE 23:38 < wumpus> luke-jr wonders if it would make sense to have a GUI option for "API Key" that sets up a rpcauth <- being able to enable RPC through the GUI would make sense, but with the automatic auth cookie stuff I wouldn't like to add another authentication method 23:39 < luke-jr> oh, good point. 23:39 < luke-jr> arguably no purpose to a key if cookies are usable :D 23:40 < paveljanik> cookies works perfectly! 23:40 < paveljanik> It would be nice to have "read-only" cookies though. 23:41 < wumpus> you mean multiple authentication levels or something? 23:43 < wumpus> the idea is to add everything that only inspects public data to the REST interface 23:43 < wumpus> that is already a "read-only" interface 23:44 < sipa> we could even have sendrawtransaction and submitblock to the REST interface as well 23:44 < sipa> the read-only part isn't what matters - the public data is 23:45 < sipa> though i guess it's also an avenue for DoS 23:45 < wumpus> meh. 23:46 < wumpus> well I guess that's true, those two can be done over the P2P interface just as well, so in principle no extra authentication should be necessary for them 23:46 < wumpus> but I find a read-only REST interface much easier to reason about 23:46 < wumpus> so I'd prefer to keep it that way 23:51 < wumpus> being able to affect state opens a whole new can of worms of DoSes and attack surface. The whole REST thing has never really sit very well with me. But we have it, so if you need something like that you should use it, instead of adding more fluff to RPC auth. 23:53 < wumpus> (and an option to enable the REST interface in the GUI options would also make sense) 23:54 -!- Giszmo [~leo@pc-40-227-45-190.cm.vtr.net] has quit [Quit: Leaving.]