--- Day changed Mon Jul 25 2016 00:10 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:15 -!- frankenmint [~frankenmi@174-25-59-173.ptld.qwest.net] has joined #bitcoin-core-dev 00:16 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 00:32 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 00:32 -!- ratoder [~ratoder@static.111.19.201.138.clients.your-server.de] has joined #bitcoin-core-dev 00:35 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds] 00:58 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 01:33 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-core-dev 02:29 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 02:30 -!- Giszmo [~leo@ppp-83-171-162-142.dynamic.mnet-online.de] has joined #bitcoin-core-dev 02:49 -!- Ginnarr [~Ginnarr@unaffiliated/ginnarr] has joined #bitcoin-core-dev 02:56 -!- berndj [~berndj@197.242.93.84] has quit [Ping timeout: 260 seconds] 03:00 -!- berndj [~berndj@197.242.93.84] has joined #bitcoin-core-dev 03:29 -!- harrymm [~wayne@178.162.199.45] has quit [Ping timeout: 264 seconds] 03:45 -!- harrymm [~wayne@178.162.211.236] has joined #bitcoin-core-dev 03:46 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 260 seconds] 03:50 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:50 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 03:51 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 03:51 < GitHub86> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0df9ea42b888...99c0ac2fd9be 03:51 < GitHub86> bitcoin/master cc021ef lizhi: remove outdated legacy code... 03:51 < GitHub86> bitcoin/master 99c0ac2 Wladimir J. van der Laan: Merge #8396: remove outdated legacy code from key.h... 03:52 < GitHub85> [bitcoin] laanwj closed pull request #8396: remove outdated legacy code from key.h (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8396 03:53 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 04:06 < GitHub24> [bitcoin] laanwj pushed 1 new commit to 0.13: https://github.com/bitcoin/bitcoin/commit/73adfe3bb935cead8e4d91f8d1c8a9feb55e4a7d 04:06 < GitHub24> bitcoin/0.13 73adfe3 Jonas Schnelli: [Wallet] Correct hdmasterkeyid/masterkeyid name confusion... 04:08 -!- CubicEarth [~cubiceart@c-50-159-126-21.hsd1.wa.comcast.net] has quit [] 04:24 -!- frankenmint [~frankenmi@174-25-59-173.ptld.qwest.net] has quit [] 04:30 -!- Ginnarr [~Ginnarr@unaffiliated/ginnarr] has quit [Quit: Textual IRC Client: www.textualapp.com] 04:36 -!- mkarrer_ [~mkarrer@109.69.10.67] has joined #bitcoin-core-dev 04:40 -!- mkarrer [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has quit [Ping timeout: 260 seconds] 04:44 -!- mkarrer [~mkarrer@109.69.10.67] has joined #bitcoin-core-dev 04:44 -!- mkarrer_ [~mkarrer@109.69.10.67] has quit [Read error: Connection reset by peer] 04:47 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 04:52 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 04:57 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 05:02 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 05:06 -!- mkarrer_ [~mkarrer@109.69.10.67] has joined #bitcoin-core-dev 05:08 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 05:10 -!- mkarrer [~mkarrer@109.69.10.67] has quit [Ping timeout: 260 seconds] 05:14 -!- mkarrer [~mkarrer@109.69.10.67] has joined #bitcoin-core-dev 05:16 -!- mkarrer__ [~mkarrer@213.143.48.41] has joined #bitcoin-core-dev 05:17 -!- mkarrer_ [~mkarrer@109.69.10.67] has quit [Ping timeout: 258 seconds] 05:18 -!- mkarrer_ [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 05:19 -!- mkarrer_ [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has quit [Remote host closed the connection] 05:19 -!- mkarrer [~mkarrer@109.69.10.67] has quit [Ping timeout: 265 seconds] 05:20 -!- mkarrer [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 05:21 -!- mkarrer__ [~mkarrer@213.143.48.41] has quit [Ping timeout: 258 seconds] 05:26 < wumpus> gah happy the heatwave in NL seems to have abated a bit 05:30 -!- cryptapus_afk is now known as cryptapus 05:45 -!- YOU-JI [~youyouyou@FL1-125-195-1-168.chb.mesh.ad.jp] has joined #bitcoin-core-dev 05:49 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 05:54 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 06:16 < sipa> sdaftuar: yes, that relying on extra state for cb/segwit is unfortunate... though it's restricted to the decision of what to advertize as 06:17 < sipa> sdaftuar: a proper solution is making it a 2-way handshake, where both nodes advertize which versions they support, and then a second message is returned to indicate which version will actually be used (potentially a different one in both directions) 06:17 < sdaftuar> sipa: there's also sort of an implicit behavior, where you're relying on your peer to know to only request compactblocks from you, if you're NODE_WITNESS 06:17 < sdaftuar> yeah that's basically what i was thinking. it's a little confusing the version number has two meanings 06:17 < sipa> indeed 06:17 < sipa> but the sendcmpct message already has two meanings as well 06:17 < sdaftuar> yeah 06:18 < sipa> 1) i can offer compact blocks 06:18 < sipa> 2) i want you to potentially advertize using compact blocks, if you support it 06:19 < sdaftuar> i guess my question is, if a peer sends you a version 2 compactblock message, and you don't support version 2 compact blocks but you do support NODE_WITNESS, what should happen? 06:19 < sdaftuar> i don't think there's any way to communicate to your peer that they made a mistake 06:19 < sipa> yes 06:20 < sipa> wumpus: not just in NL... 06:20 < sdaftuar> so at the least, we should document that explicitly. 06:20 < sipa> sdaftuar: now you bring it up, i feel like fixing it properly... 06:20 < sdaftuar> that's also my preference :) 06:20 * sipa hanging out with jonasschnelli 06:21 < sipa> sdaftuar: so, in that case, i think sendcmpct should only have the meaning "i support compact blocks version up to X" 06:22 < sdaftuar> and not distinguish sending/receiving? 06:22 < sdaftuar> i think i'd agree with that 06:22 < sipa> hmm, no... "i can send you version X compact blocks" 06:22 < sipa> and a separate version for asking the peer to actually do that 06:24 < sdaftuar> why not just assume that the two peers will send/receive at the highest version they both support? i was thinking the peer who supports the higher version will advertise at the lower version to complete the handshake 06:25 < sipa> well the protocol is not necessarily symmetric 06:26 < sipa> one side may want inv using cmpctblock 06:26 < sipa> while the other does not 06:26 < sdaftuar> well we have the separate announcements bool inside the message 06:26 < sipa> BlueMatt: ping ^ 06:26 < sdaftuar> i just figure that the chances that you are able to announce a compactblock with wtxid's, but prefer compactblock announcements using txid's, is an unsupported use case 06:27 < sdaftuar> prefer receiving* 06:29 < sdaftuar> so my proposed protocol flow would be: you send me SENDCMPCT(announce=whatever, version=2). i send you SENDCMPCT(announce=whatever, version=1). you send me SENDCMPCT(announce=false, version=1). 06:29 < sdaftuar> (i have to ignore your first SENDCMPCT because it's too high version and i don't support it, as per the BIP) 06:30 < sipa> who sends first? 06:30 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 06:30 < sdaftuar> i don't think it matters, except that if you got mine first, you wouldn't bother sending a version=2 message 06:30 < sipa> i find protocols that try to negotiate things for both directions hard to reason about 06:31 < sdaftuar> i'm not sure it matters that announcements are a different direction than decoding, since we can just assume that if you can encode, you can decode, right? 06:31 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 06:31 < sdaftuar> that's not strictly true of course, but just seems like not something we'd need to support 06:31 < sipa> well a segwit node with wtxid-based table can encode compact blocks with txids or wtxids, but only decide wtxid based ones 06:32 < sipa> s/decide/decode/ 06:32 < sdaftuar> fair point 06:35 < sdaftuar> in this situation it's the opposite case that would be the concern, ie if you're capable of encoding with wtxid's or txid's, but are only able to decode txid-based ones 06:35 < sdaftuar> because in your example, you'd just never request compactblocks from the version1 peer 06:35 < sdaftuar> by using announce=false, and not requesting compact blocks otherwise 06:41 < sipa> right 06:44 -!- mkarrer_ [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 06:44 -!- YOU-JI_ [~youyouyou@FL1-125-195-1-168.chb.mesh.ad.jp] has joined #bitcoin-core-dev 06:45 -!- YOU-JI [~youyouyou@FL1-125-195-1-168.chb.mesh.ad.jp] has quit [Ping timeout: 260 seconds] 06:47 -!- mkarrer [~mkarrer@142.red-83-47-107.dynamicip.rima-tde.net] has quit [Ping timeout: 260 seconds] 06:51 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 06:56 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 06:58 -!- frankenmint [~frankenmi@174-25-59-173.ptld.qwest.net] has joined #bitcoin-core-dev 06:58 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev 06:59 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection] 07:00 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 07:01 -!- YOU-JI_ [~youyouyou@FL1-125-195-1-168.chb.mesh.ad.jp] has quit [Quit: Leaving...] 07:02 -!- arubi [~ese168@unaffiliated/arubi] has quit [Ping timeout: 244 seconds] 07:02 -!- TomMc [~tom@unaffiliated/tommc] has joined #bitcoin-core-dev 07:08 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 258 seconds] 07:24 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 07:42 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-gbaisvwhaxavqhub] has quit [Ping timeout: 260 seconds] 07:42 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-bcwfshnpybdflran] has joined #bitcoin-core-dev 07:48 -!- zooko [~user@2601:281:8000:8387:e43f:1962:2609:8aed] has joined #bitcoin-core-dev 07:51 -!- arubi__ [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev 07:53 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 07:54 -!- frankenmint [~frankenmi@174-25-59-173.ptld.qwest.net] has quit [Remote host closed the connection] 07:54 -!- arubi_ [~ese168@unaffiliated/arubi] has quit [Ping timeout: 240 seconds] 07:58 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 08:06 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 08:11 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 08:14 -!- Giszmo [~leo@ppp-83-171-162-142.dynamic.mnet-online.de] has quit [Quit: Leaving.] 08:27 < GitHub84> [bitcoin] rebroad opened pull request #8403: Process "notfound" messages, and safeguard against unreasonably long … (master...ProcessNotfound) https://github.com/bitcoin/bitcoin/pull/8403 08:31 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-muuyhhdedyjqqkeh] has joined #bitcoin-core-dev 08:37 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 08:37 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection] 08:38 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 08:45 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection] 08:45 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 08:54 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 08:56 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 276 seconds] 08:58 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:59 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 09:08 < GitHub43> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/99c0ac2fd9be...517eee3e8f8b 09:08 < GitHub43> bitcoin/master 682aa0f Suhas Daftuar: Scale legacy sigop count in CreateNewBlock 09:08 < GitHub43> bitcoin/master 517eee3 Wladimir J. van der Laan: Merge #8362: Scale legacy sigop count in CreateNewBlock... 09:08 < GitHub191> [bitcoin] laanwj closed pull request #8362: Scale legacy sigop count in CreateNewBlock (master...coinbase-sigops-scale) https://github.com/bitcoin/bitcoin/pull/8362 09:09 < GitHub149> [bitcoin] laanwj pushed 1 new commit to 0.13: https://github.com/bitcoin/bitcoin/commit/86edc20a178cc17cdc6915e9e93a7241c27c368c 09:09 < GitHub149> bitcoin/0.13 86edc20 Suhas Daftuar: Scale legacy sigop count in CreateNewBlock... 09:13 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection] 09:13 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 09:22 -!- jtimon [~quassel@55.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 09:34 -!- arubi__ is now known as arubi 09:36 -!- anu0 [~anu0@unaffiliated/anu0] has joined #bitcoin-core-dev 09:56 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 09:58 -!- zooko [~user@2601:281:8000:8387:e43f:1962:2609:8aed] has quit [Ping timeout: 250 seconds] 09:58 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 10:00 -!- DongSwanson [2ea5fb94@gateway/web/freenode/ip.46.165.251.148] has joined #bitcoin-core-dev 10:01 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 10:01 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev 10:03 -!- arubi [~ese168@unaffiliated/arubi] has quit [Disconnected by services] 10:03 -!- arubi_ is now known as arubi 10:04 < DongSwanson> can somebody help me with utilizing CHECKSEQUENCEVERIFY with bitcoin-core? I want to create a "escrow with timeout" with bitcoin-core 10:04 -!- d_t [~textual@185.69.203.10] has joined #bitcoin-core-dev 10:20 < jl2012> DongSwanson: I think you can only do it manually. Try on the testnet first 10:21 < DongSwanson> jl2012: what do you mean by manually? 10:23 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 10:24 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 10:27 < sipa> DongSwanson: the wallet code can't sign such transactions 10:27 < sipa> so you'll need to construct the scriptSig using other tools 10:27 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Remote host closed the connection] 10:28 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has joined #bitcoin-core-dev 10:29 < DongSwanson> sipa: oh. so if I wanted to create a escrow with timeout for a real world scenario, we cannot use bitcoin-core? 10:31 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Quit: Leaving.] 10:32 -!- pedrobranco [~pedrobran@79.242.108.93.rev.vodafone.pt] has quit [Ping timeout: 252 seconds] 10:34 < sipa> DongSwanson: you can't use its wallet code for constructing such transactions 10:34 < Chris_Stewart_5> DongSwanson: Bitcoin Core doesn't expose functionality to create custom contracts through a user interface (that I know of...) You need to manually construct the contract 10:34 < sipa> manually construct the contract (the easy part) and manually satisfy the contract (the hard part...) 10:34 < gmaxwell> Creating it is not a big deal, but without a way to sign for it you will burn your funds. 10:35 < Chris_Stewart_5> You can use something like peter todd's python bitcoin library or whatever library there is for your favorite language 10:35 < sipa> or you can help review pull request 7601 10:36 < Chris_Stewart_5> as sipa and gmaxwell said, best to experiment on testnet/regtest 10:36 < sipa> which adds support for HTLC's (contracts which have a timelock and a hashlock) 10:37 < Chris_Stewart_5> through bitcoin core's wallet UI? 10:37 < JackH> there is a pull request for wallet features that enables "smarter" functions? 10:38 < DongSwanson> so bitcoin-core cannot create CSV escrows but can sign it's outgoing transactions if you provide the correct redeemscript? 10:38 < sipa> DongSwanson: nope 10:39 < sipa> the other way around 10:39 < DongSwanson> it cannot sign as well? 10:39 < JackH> found it: https://github.com/bitcoin/bitcoin/pull/7601 10:39 < DongSwanson> okay. i understand 10:39 < JackH> why are you guys keeping all these gems for yourself 10:39 < sipa> it can create outputs to csv scripts 10:39 < sipa> but it can't spend them 10:40 < sipa> JackH: how do you mean to ourself? 10:40 < Chris_Stewart_5> sipa: Even if you construct the inputs for the contract correctly, it won't be propogated will it? 10:40 < JackH> I was joking because I didnt know about this myself 10:40 < JackH> I know its public ;) 10:40 < sipa> ha ok 10:40 < sipa> Chris_Stewart_5: it's standard 10:41 < JackH> I always wanted a core wallet with a bit more options unlocked, as we have nothing like that 10:41 < Chris_Stewart_5> Hmm for some reason I thought redeem scripts needed to be standard scriptPubKey 10:41 < JackH> probably both good and bad as you wouldn have to answer support questions on IRC all day about how people can get their 10 year time locked Bitcoins back 10:42 -!- netsinn [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev 10:42 < sipa> Chris_Stewart_5: not anymore since a few releases 10:44 < sipa> JackH: well CSV only activated a few weeks ago 10:45 < JackH> yeah I can see in the pull maxwell says he will take a look at it after segwit 10:45 < DongSwanson> so I guess I'll give it some more time 10:48 < DongSwanson> thanks everybody for your input. I'll ask again in a few weeks. Be prepared :-) 10:49 < sipa> DongSwanson: you can help make things move forward by testing the HTLC pull request, for example 10:50 < sipa> waiting may work, helping gets you further 10:53 < DongSwanson> good idea. Bitcoin has given me a lot. Maybe it is time to give something back. I'll look into that tomorrow. 10:53 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 10:57 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 11:02 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 11:09 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 11:15 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 11:18 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 11:21 -!- BitcoinErrorLog [~bitcoiner@c-98-231-56-138.hsd1.fl.comcast.net] has joined #bitcoin-core-dev 11:22 -!- netsinn [~jiggalato@unaffiliated/jiggalator] has quit [Remote host closed the connection] 11:26 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 11:28 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 11:29 -!- netsinn [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev 11:59 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 12:04 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 12:10 -!- Lauda [~Lauda@133.ip-92-222-169.eu] has quit [Remote host closed the connection] 12:12 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 12:13 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 12:14 -!- Lauda [~Lauda@133.ip-92-222-169.eu] has joined #bitcoin-core-dev 12:17 -!- BitcoinErrorLog [~bitcoiner@c-98-231-56-138.hsd1.fl.comcast.net] has quit [] 12:40 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev 12:44 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev 12:44 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 244 seconds] 12:55 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 13:00 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 13:03 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 13:04 -!- anu1 [~anu0@unaffiliated/anu0] has joined #bitcoin-core-dev 13:04 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 13:05 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 13:05 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 13:07 -!- anu0 [~anu0@unaffiliated/anu0] has quit [Ping timeout: 264 seconds] 13:23 -!- menix01 [menix01@86.125.251.101] has joined #bitcoin-core-dev 13:24 < menix01> anyboady talck here? 13:24 < sipa> nope, never 13:25 < btcdrak> I can confirm 13:29 < menix01> and why you stay here peoples 13:29 < sipa> to discuss the development of the software project called Bitcoin Core 13:29 < sipa> see the topic 13:29 < menix01> i see but u say noboady speack 13:29 < menix01> that why\m comfuse 13:30 < sipa> well, us saying that nobody says something is a clearly self-defeating statement 13:30 < sipa> so perhaps it is a joke? 13:30 < menix01> ok i was pm u private sipa 13:31 < sipa> sorry, not interested 13:31 < menix01> ok 13:37 -!- cryptapus is now known as cryptapus_afk 13:44 < PatBoy> thx for ur great work dev :) 13:48 -!- jannes [~jannes@178.132.211.90] has quit [Quit: Leaving] 13:54 -!- Lauda [~Lauda@133.ip-92-222-169.eu] has quit [Remote host closed the connection] 13:57 -!- Lauda [~Lauda@178.236.88.230] has joined #bitcoin-core-dev 14:01 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 14:06 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 14:20 -!- LaudaM [~Lauda@2a06:8ec0:3::1:b224] has joined #bitcoin-core-dev 14:21 -!- Lauda [~Lauda@178.236.88.230] has quit [Quit: Leaving] 14:22 -!- LaudaM is now known as Lauda 14:35 -!- TomMc [~tom@unaffiliated/tommc] has quit [Ping timeout: 276 seconds] 14:47 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Quit: Leaving.] 14:47 -!- TomMc [~tom@gateway/vpn/privateinternetaccess/tommc] has joined #bitcoin-core-dev 14:49 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 14:56 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 15:02 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 15:03 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 15:08 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 15:11 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Ping timeout: 250 seconds] 15:14 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer] 15:15 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev 15:17 -!- jtimon [~quassel@55.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 260 seconds] 15:18 -!- netsinn [~jiggalato@unaffiliated/jiggalator] has quit [Remote host closed the connection] 15:25 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Quit: Leaving.] 15:26 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 15:28 -!- harrymm [~wayne@178.162.211.236] has quit [Ping timeout: 240 seconds] 15:31 -!- netsinn [~jiggalato@unaffiliated/jiggalator] has joined #bitcoin-core-dev 15:43 < BlueMatt> sdaftuar: sipa sorry, whats up? 15:46 < BlueMatt> I was figuring if you're getting witnesses in blocks, and a peer doesnt support receiving witnesses over cmpctblocks, you just send them full blocks 15:47 < BlueMatt> like, backward compat there is not hugely important to me? 15:49 -!- harrymm [~wayne@37.58.59.75] has joined #bitcoin-core-dev 16:04 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 16:05 -!- spudowiar [~spudowiar@unaffiliated/spudowiar] has quit [Quit: Leaving.] 16:07 -!- spudowiar1 [~spudowiar@unaffiliated/spudowiar] has joined #bitcoin-core-dev 16:07 -!- spudowiar1 is now known as spudowiar 16:09 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 16:11 < sipa> BlueMatt: brb in 5 minutes 16:12 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 276 seconds] 16:14 < sipa> BlueMatt: i think the first question is more general about how to deal with multiple versions cmpctblocks 16:14 < sipa> BlueMatt: because there is no way to negotiate 16:14 < BlueMatt> hmm, I had a scheme in mind when I wrote it..... 16:14 < BlueMatt> lemme go look 16:15 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev 16:18 -!- ryan-c [~ryan@znc.rya.nc] has joined #bitcoin-core-dev 16:22 -!- adiabat [~tx@159.203.193.74] has quit [Remote host closed the connection] 16:23 -!- ryan-c [~ryan@znc.rya.nc] has quit [K-Lined] 16:26 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)] 16:29 < BlueMatt> ahh, yea, in the `sendcmpct` section: "Upon receipt of a "sendcmpct" message with the second integer set to something other than 1, nodes MUST treat the peer as if they had not received the message (as it indicates the peer will provide an unexpected encoding in cmpctblock, and/or other, messages). This allows future versions to send duplicate sendcmpct messages with different versions as a part of a version handshake for future versio 16:29 < BlueMatt> ns." 16:29 < sipa> BlueMatt: aha! 16:30 < sipa> that sounds interesting 16:30 < BlueMatt> intention was that, if you support version 2, you can just send 2 sendcmpct messages 16:30 < BlueMatt> 1 with version 1, one with version 2 16:30 < sipa> i'll adapt bip and pr 16:30 < sipa> actually, only pr 16:30 < gmaxwell> also means you can stop supporting v1 at some point. 16:31 < sipa> indeed 16:31 -!- frankenmint [~frankenmi@67-5-255-55.ptld.qwest.net] has joined #bitcoin-core-dev 16:31 < sipa> code now decides what to send based on whether the peer sets node_witness 16:31 < BlueMatt> sipa: if you want, you could pull that out and put it elsewhere in the bip...its kinda easy to miss as a bullet in a seemingly-unrelated section :p 16:31 < sipa> but we shoukd just send both 16:31 < sipa> and let the receiver decide 16:31 < BlueMatt> yea, I was thinking do cmpctblockversion = max(all received sendcmpctblock messages) 16:32 < sipa> *should 16:32 < BlueMatt> but...whatever 16:37 -!- frankenmint [~frankenmi@67-5-255-55.ptld.qwest.net] has quit [Remote host closed the connection] 16:44 -!- frankenmint [~frankenmi@67-5-255-55.ptld.qwest.net] has joined #bitcoin-core-dev 16:57 < luke-jr> so.. not having a solution to the GBT weightlimit issue.. is it correct that the weight of a gen tx is always (size * 4) + (1 byte for witness stack size + 1 byte for stack item size + 32 bytes stack item nonce) = (size*4)+34 ? 16:57 < luke-jr> sipa: ^ 17:01 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev 17:03 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer] 17:03 -!- justanot1eruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 17:05 < sipa> luke-jr: don't forget marker and flag byte 17:05 -!- pedrobranco [~pedrobran@167.225.61.94.rev.vodafone.pt] has quit [Ping timeout: 244 seconds] 17:06 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 17:11 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 17:20 < luke-jr> sipa: ah, right, so +36 17:35 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-muuyhhdedyjqqkeh] has quit [Quit: Connection closed for inactivity] 17:47 -!- justanot1eruser is now known as justanotheruser 18:00 -!- ryan-c [~ryan@znc.rya.nc] has joined #bitcoin-core-dev 18:07 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 18:12 -!- fengling [~fengling@58.135.95.136] has quit [Ping timeout: 240 seconds] 18:13 -!- fengling [~fengling@58.135.95.136] has joined #bitcoin-core-dev 18:17 -!- frankenmint [~frankenmi@67-5-255-55.ptld.qwest.net] has quit [Remote host closed the connection] 19:40 -!- TomMc [~tom@gateway/vpn/privateinternetaccess/tommc] has quit [Ping timeout: 240 seconds] 19:47 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 258 seconds] 20:27 -!- d_t [~textual@185.69.203.10] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 21:03 -!- anu0 [~anu0@unaffiliated/anu0] has joined #bitcoin-core-dev 21:07 -!- anu1 [~anu0@unaffiliated/anu0] has quit [Ping timeout: 276 seconds] 21:22 -!- harrymm [~wayne@37.58.59.75] has quit [Remote host closed the connection] 21:26 -!- harrymm [~wayne@37.58.59.83] has joined #bitcoin-core-dev 21:32 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Disconnected by services] 21:32 -!- Arnavion3 [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 21:32 -!- Arnavion3 is now known as Arnavion 21:50 -!- d_t [~textual@185.69.203.10] has joined #bitcoin-core-dev 21:54 -!- d_t [~textual@185.69.203.10] has quit [Ping timeout: 252 seconds] 22:07 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Disconnected by services] 22:07 -!- Arnavion3 [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 22:07 -!- Arnavion3 is now known as Arnavion 22:16 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Quit: Arnavion] 22:23 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev 22:24 -!- d_t [~textual@185.69.203.10] has joined #bitcoin-core-dev 22:30 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev 22:33 -!- go1111111 [~go1111111@104.232.116.217] has quit [Ping timeout: 258 seconds] 22:46 -!- go1111111 [~go1111111@104.200.154.22] has joined #bitcoin-core-dev 23:02 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev 23:06 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 258 seconds] 23:06 -!- netsinn [~jiggalato@unaffiliated/jiggalator] has quit [Remote host closed the connection] 23:26 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 23:48 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 23:58 < jonasschnelli> I'm impressed. A guy implemented bip151 in JS: https://github.com/bcoin-org/bcoin/blob/4af5273c0eb0f5fb5c9cfe68e4fe13afb005e410/lib/bcoin/bip151.js