12016-08-23T00:15:53 *** Ylbam has quit IRC
22016-08-23T00:24:39 *** JackH_ has quit IRC
32016-08-23T00:31:20 *** fengling has joined #bitcoin-core-dev
42016-08-23T00:31:21 *** murch has quit IRC
52016-08-23T00:55:33 *** moli has quit IRC
62016-08-23T00:56:39 <GitHub188> [bitcoin] cbarcenas opened pull request #8560: Trivial: Fix two VarInt examples in serialize.h (master...fix_varint_examples) https://github.com/bitcoin/bitcoin/pull/8560
72016-08-23T01:01:33 *** belcher has quit IRC
82016-08-23T01:04:22 *** adiabat has joined #bitcoin-core-dev
92016-08-23T01:13:06 *** Alopex has quit IRC
102016-08-23T01:13:53 *** aureianimus_ has quit IRC
112016-08-23T01:14:11 *** Alopex has joined #bitcoin-core-dev
122016-08-23T01:18:28 *** aureianimus has joined #bitcoin-core-dev
132016-08-23T01:19:15 *** Chris_Stewart_5 has joined #bitcoin-core-dev
142016-08-23T01:40:04 *** aureianimus has quit IRC
152016-08-23T01:44:11 *** Alopex has quit IRC
162016-08-23T01:45:16 *** Alopex has joined #bitcoin-core-dev
172016-08-23T01:47:16 *** harrymm has quit IRC
182016-08-23T01:50:21 *** btcdrak has quit IRC
192016-08-23T01:59:50 *** JZA has joined #bitcoin-core-dev
202016-08-23T02:06:58 *** harrymm has joined #bitcoin-core-dev
212016-08-23T02:23:20 *** moli has joined #bitcoin-core-dev
222016-08-23T02:34:02 *** Alopex has quit IRC
232016-08-23T02:35:07 *** Alopex has joined #bitcoin-core-dev
242016-08-23T02:43:23 *** Chris_Stewart_5 has quit IRC
252016-08-23T02:58:20 *** TomMc has quit IRC
262016-08-23T03:04:01 *** Alopex has quit IRC
272016-08-23T03:05:07 *** Alopex has joined #bitcoin-core-dev
282016-08-23T03:25:41 *** TomMc has joined #bitcoin-core-dev
292016-08-23T03:37:01 *** Alopex has quit IRC
302016-08-23T03:38:06 *** Alopex has joined #bitcoin-core-dev
312016-08-23T03:46:30 <kanzure> a toy demo for finding most recent common blockhash between two data stores (one being a hypothetical bitcoind) (rpc calls not implemented) https://gist.github.com/kanzure/2fa531afaf03fddd6568eb0212ac8c4c
322016-08-23T03:46:34 <kanzure> this is re: https://botbot.me/freenode/bitcoin-core-dev/2016-04-28/?msg=65077020&page=3
332016-08-23T03:47:36 <kanzure> i was wondering about making this a patch for bitcoind itself- perhaps storing some external application synchronization state and letting bitcoind manage that based on reorgs and known time since last query from some authorized application. easier to manage chain diffs from the perspective of bitcoind. and probably application authors aren't going to bother doing this right anyway...
342016-08-23T03:48:36 <kanzure> (whereas application authors might be more likely to write code to handle an explicit "here's the exact bundle of block differences not yet consumed" data dump)
352016-08-23T03:56:08 *** TomMc has quit IRC
362016-08-23T04:36:32 *** zooko has joined #bitcoin-core-dev
372016-08-23T04:39:11 *** zooko has quit IRC
382016-08-23T04:44:06 *** fengling has quit IRC
392016-08-23T04:45:50 *** kadoban has quit IRC
402016-08-23T05:13:22 *** Alopex has quit IRC
412016-08-23T05:14:27 *** Alopex has joined #bitcoin-core-dev
422016-08-23T05:17:10 *** fengling has joined #bitcoin-core-dev
432016-08-23T05:39:38 *** molz has joined #bitcoin-core-dev
442016-08-23T05:43:12 *** moli has quit IRC
452016-08-23T05:53:26 *** Alopex has quit IRC
462016-08-23T05:54:31 *** Alopex has joined #bitcoin-core-dev
472016-08-23T06:11:26 <GitHub129> [bitcoin] rebroad opened pull request #8561: Show "end" instead of many zros when getheaders request received with⦠(master...LessGetheadersZeros) https://github.com/bitcoin/bitcoin/pull/8561
482016-08-23T06:15:28 *** shesek has quit IRC
492016-08-23T06:25:38 *** btcdrak has joined #bitcoin-core-dev
502016-08-23T06:33:02 *** Alopex has quit IRC
512016-08-23T06:34:07 *** Alopex has joined #bitcoin-core-dev
522016-08-23T06:39:43 *** shesek has joined #bitcoin-core-dev
532016-08-23T06:49:48 *** jannes has joined #bitcoin-core-dev
542016-08-23T06:50:29 *** BashCo has quit IRC
552016-08-23T06:55:01 *** Alopex has quit IRC
562016-08-23T06:56:07 *** Alopex has joined #bitcoin-core-dev
572016-08-23T07:08:31 *** aureianimus has joined #bitcoin-core-dev
582016-08-23T07:12:42 *** BashCo has joined #bitcoin-core-dev
592016-08-23T07:25:05 *** rubensayshi has joined #bitcoin-core-dev
602016-08-23T07:38:21 *** JackH_ has joined #bitcoin-core-dev
612016-08-23T07:41:37 *** laurentmt has joined #bitcoin-core-dev
622016-08-23T07:51:58 *** laurentmt has quit IRC
632016-08-23T07:53:52 *** owowo has quit IRC
642016-08-23T07:57:11 *** laurentmt has joined #bitcoin-core-dev
652016-08-23T08:09:51 *** paveljanik has quit IRC
662016-08-23T08:19:19 *** laurentmt1 has joined #bitcoin-core-dev
672016-08-23T08:21:44 *** laurentmt has quit IRC
682016-08-23T08:21:44 *** laurentmt1 is now known as laurentmt
692016-08-23T08:30:00 *** murch has joined #bitcoin-core-dev
702016-08-23T08:36:24 *** owowo has joined #bitcoin-core-dev
712016-08-23T08:39:20 *** Ylbam has joined #bitcoin-core-dev
722016-08-23T08:53:19 *** molz has quit IRC
732016-08-23T08:55:43 *** pedrobranco has joined #bitcoin-core-dev
742016-08-23T09:57:52 <timothy> hi, I'm changing the build procedure of official archlinux packages to use git tag directly instead of downloading the linux tar with the source code
752016-08-23T09:58:07 <timothy> with the check of tag signature ofc
762016-08-23T09:58:18 <timothy> any comments against that?
772016-08-23T10:02:53 <sipa> arch builds from source on install?
782016-08-23T10:03:12 <timothy> no, I build packages signed with my signature
792016-08-23T10:03:22 <timothy> but user can choose to build the package by itself
802016-08-23T10:07:10 *** Ginnarr has joined #bitcoin-core-dev
812016-08-23T10:14:53 <sipa> ok, and this applies only in case they choose to build from source?
822016-08-23T10:17:40 <timothy> also when I build from source
832016-08-23T10:17:58 <timothy> binary packages on archlinux are signed by my gpg key
842016-08-23T10:18:18 *** mkarrer has quit IRC
852016-08-23T10:18:49 *** mkarrer has joined #bitcoin-core-dev
862016-08-23T10:24:34 <sipa> timothy: i don't think it matters much. git tags are only on sha1 hashes, though, which may not be considered sufficiently secure in the future
872016-08-23T10:25:09 <timothy> builds are made by using git too
882016-08-23T10:25:20 <timothy> so if someone inject malware in git repository gitian doesn't help
892016-08-23T10:26:56 <sipa> fair enough
902016-08-23T10:27:31 <sipa> though we would detect different binaries through gitian... unless everyone got a version with modified history
912016-08-23T10:28:10 <sipa> so actually, i think that downloading the source tarball is stronger, if you verify multiple gitian signatures
922016-08-23T10:28:19 <sipa> which is nontrivial, i guess
932016-08-23T10:38:18 *** MarcoFalke has joined #bitcoin-core-dev
942016-08-23T10:39:06 <MarcoFalke> It should be mentioned that a lot of people mistake the tarball on the GitHub as something that can be verified
952016-08-23T10:39:08 <MarcoFalke> link: https://github.com/bitcoin/bitcoin/releases/tag/v0.13.0
962016-08-23T10:39:31 <btcdrak> there doesnt seem to be a way to turn those off :(
972016-08-23T10:39:35 <MarcoFalke> But I am not aware of disabling those
982016-08-23T10:39:40 <MarcoFalke> jup
992016-08-23T10:39:41 <btcdrak> we should ask Github about it
1002016-08-23T10:40:10 <btcdrak> timothy: you should build from the gitian tarballs at least
1012016-08-23T10:40:29 <btcdrak> wumpus do you upload the tar sources too?
1022016-08-23T10:40:37 *** spudowiar has joined #bitcoin-core-dev
1032016-08-23T10:41:30 <MarcoFalke> We could upload wumpus' sig.asc to the github releases and link to the site where we place the gitian binaries
1042016-08-23T10:42:14 <timothy> MarcoFalke: I'm using git clone + git verify-tag ofc
1052016-08-23T10:42:17 <MarcoFalke> btcdrak: yes https://bitcoin.org/bin/bitcoin-core-0.13.0/test.rc3/
1062016-08-23T10:43:14 <btcdrak> wumpus: also remember to include the hashes in your release announcement going forward so that information can be widely distributed.
1072016-08-23T10:44:24 <timothy> yes, I'm still waiting for 0.13.0 tarballs :p
1082016-08-23T10:47:43 <btcdrak> Starting today the bitcoincore.org merges will be git signed. (I have been lazy in this respect). I ask the other maintainers to do so also.
1092016-08-23T10:56:57 *** cryptapus has joined #bitcoin-core-dev
1102016-08-23T10:57:17 <warren> btcdrak: easier to force it if you have the web server update only to signed commits?
1112016-08-23T10:57:18 *** cryptapus has joined #bitcoin-core-dev
1122016-08-23T10:57:18 *** cryptapus has joined #bitcoin-core-dev
1132016-08-23T10:57:47 <btcdrak> if/when we do our own hosting
1142016-08-23T10:58:05 <btcdrak> I'll turn off the merge button on the repository at least
1152016-08-23T11:01:03 <btcdrak> oh they dont have that feature. I must be misremembering
1162016-08-23T11:01:41 <warren> github is so convenient they make people forget the "distributed" part.
1172016-08-23T11:22:29 <GitHub129> [bitcoin] ajtowns opened pull request #8563: Add configure check for -latomic (master...autoconf-latomic) https://github.com/bitcoin/bitcoin/pull/8563
1182016-08-23T11:30:25 *** Ginnarr has quit IRC
1192016-08-23T11:32:43 *** JackH_ has quit IRC
1202016-08-23T11:52:38 *** Megaf has joined #bitcoin-core-dev
1212016-08-23T11:55:55 *** jouke has quit IRC
1222016-08-23T11:55:55 *** jouke has joined #bitcoin-core-dev
1232016-08-23T12:03:58 *** Chris_Stewart_5 has joined #bitcoin-core-dev
1242016-08-23T12:08:34 *** Chris_Stewart_5 has quit IRC
1252016-08-23T12:12:36 *** Arnavion has quit IRC
1262016-08-23T12:12:41 *** Arnavion has joined #bitcoin-core-dev
1272016-08-23T12:12:46 *** fengling has quit IRC
1282016-08-23T12:13:03 *** AtashiCon has quit IRC
1292016-08-23T12:13:07 *** Arnavion3 has joined #bitcoin-core-dev
1302016-08-23T12:13:11 *** Arnavion3 is now known as AtashiCon
1312016-08-23T12:22:45 *** molz has joined #bitcoin-core-dev
1322016-08-23T12:27:38 *** Chris_Stewart_5 has joined #bitcoin-core-dev
1332016-08-23T12:44:00 *** laurentmt has quit IRC
1342016-08-23T12:51:03 *** laurentmt has joined #bitcoin-core-dev
1352016-08-23T13:09:08 *** Megaf has quit IRC
1362016-08-23T13:11:13 *** TomMc has joined #bitcoin-core-dev
1372016-08-23T13:11:41 *** Megaf has joined #bitcoin-core-dev
1382016-08-23T13:12:12 *** instagibbs has quit IRC
1392016-08-23T13:20:14 *** ArthurNumbanumba has quit IRC
1402016-08-23T13:26:46 * jonasschnelli stabs berkleyDb
1412016-08-23T13:29:51 *** harrymm has quit IRC
1422016-08-23T13:31:57 *** instagibbs has joined #bitcoin-core-dev
1432016-08-23T13:40:39 *** fengling has joined #bitcoin-core-dev
1442016-08-23T13:41:24 <GitHub107> [bitcoin] jonasschnelli opened pull request #8564: [Wallet] remove unused code/conditions in ReadAtCursor (master...2016/08/bdb_abstraction_1) https://github.com/bitcoin/bitcoin/pull/8564
1452016-08-23T13:44:22 *** harrymm has joined #bitcoin-core-dev
1462016-08-23T13:44:46 *** fengling has quit IRC
1472016-08-23T13:47:53 *** harrymm has quit IRC
1482016-08-23T13:48:09 *** harrymm has joined #bitcoin-core-dev
1492016-08-23T13:49:04 *** cryptapus has quit IRC
1502016-08-23T13:51:06 *** Guyver2 has joined #bitcoin-core-dev
1512016-08-23T13:52:51 *** cryptapus has joined #bitcoin-core-dev
1522016-08-23T13:52:51 *** cryptapus has joined #bitcoin-core-dev
1532016-08-23T13:53:30 *** aalex_ has quit IRC
1542016-08-23T13:54:22 *** Samdney has joined #bitcoin-core-dev
1552016-08-23T13:55:01 * btcdrak calls an ambulance
1562016-08-23T13:55:37 <kanzure> need something?
1572016-08-23T13:56:10 <sipa> ?
1582016-08-23T13:56:30 <wumpus> because of the heat wave?
1592016-08-23T13:56:48 <GitHub113> [bitcoin] roques opened pull request #8565: .gitignore TAGS and emacs lock files (master...gitignore) https://github.com/bitcoin/bitcoin/pull/8565
1602016-08-23T13:57:17 <btcdrak> "14:26 â jonasschnelli stabs berkleyDb"
1612016-08-23T13:57:38 <kanzure> man, i was about to schedule an airdrop of paramedics to you
1622016-08-23T13:57:42 <wumpus> noooo don't add your personal gitignores into the project
1632016-08-23T13:57:51 <sipa> i just flew from london to frankfurt
1642016-08-23T13:57:51 <wumpus> why do people keep doing that
1652016-08-23T13:57:56 <sipa> i did not see any clouds
1662016-08-23T13:58:00 <sipa> for the entire flight
1672016-08-23T13:58:02 <sipa> crazy
1682016-08-23T13:58:07 <wumpus> crazy indeed
1692016-08-23T13:59:36 *** cryptapus has quit IRC
1702016-08-23T13:59:40 *** shesek has quit IRC
1712016-08-23T13:59:46 *** cryptapus has joined #bitcoin-core-dev
1722016-08-23T14:00:24 *** laurentmt has quit IRC
1732016-08-23T14:00:25 *** juscamarena has joined #bitcoin-core-dev
1742016-08-23T14:06:12 <waxwing> open the window?
1752016-08-23T14:06:35 <wumpus> during a flight?
1762016-08-23T14:07:16 <sipa> no clouds in london on itself is oretty remarkable already :)
1772016-08-23T14:07:21 <juscamarena> There's always the emergency escape "window" ;)
1782016-08-23T14:08:00 *** kadoban has joined #bitcoin-core-dev
1792016-08-23T14:10:04 *** harrymm has quit IRC
1802016-08-23T14:15:40 *** shesek has joined #bitcoin-core-dev
1812016-08-23T14:15:55 *** aalex has joined #bitcoin-core-dev
1822016-08-23T14:18:14 *** Chris_Stewart_5 has quit IRC
1832016-08-23T14:28:57 *** harrymm has joined #bitcoin-core-dev
1842016-08-23T14:29:39 *** juscamarena has quit IRC
1852016-08-23T14:30:19 *** juscamarena has joined #bitcoin-core-dev
1862016-08-23T14:32:36 *** Chris_Stewart_5 has joined #bitcoin-core-dev
1872016-08-23T14:38:34 *** juscamarena has quit IRC
1882016-08-23T14:41:19 *** fengling has joined #bitcoin-core-dev
1892016-08-23T14:43:42 *** spudowiar has quit IRC
1902016-08-23T14:44:18 *** juscamarena has joined #bitcoin-core-dev
1912016-08-23T14:46:06 *** fengling has quit IRC
1922016-08-23T14:47:29 <sipa> there are a few changes that i don't think were considered for inclusion in the release notes... not sure they're important enough, or just forgotten: wallet encryption no longer relies on OpenSSL, debug symbol binaries are now separately downloadable, removal of no-fee send option in gui
1932016-08-23T14:54:55 <wumpus> well the last one clearly affect users, and may have been useful to include
1942016-08-23T14:55:10 <wumpus> the debug symbols are not downloadable, they're just generated by gitian
1952016-08-23T14:55:20 <sipa> oh, ok
1962016-08-23T14:55:45 <wumpus> that they are generated deterministically is useful for doing eg. addrtoline on stack traces in bug reports
1972016-08-23T14:55:53 *** Ylbam has quit IRC
1982016-08-23T14:56:28 <wumpus> no longer using OpenSSL may make some people happy I suppose :)
1992016-08-23T14:56:41 <wumpus> (only for random number generation now...)
2002016-08-23T14:57:55 <sipa> and payment protocol
2012016-08-23T14:58:33 <MarcoFalke> Well, let's hope that people no longer use the GUI to send no-fee txes
2022016-08-23T14:58:56 <MarcoFalke> So no one will notice, if above statement holds
2032016-08-23T14:59:17 *** spudowiar has joined #bitcoin-core-dev
2042016-08-23T14:59:51 <instagibbs> supporting "no fee" from GUI just gives plenty of work helping people get stuff unstuck
2052016-08-23T15:00:10 <wumpus> wasn't the no-fee option moved to coin control?
2062016-08-23T15:00:14 <wumpus> or really removed
2072016-08-23T15:00:15 <wumpus> I don't remember
2082016-08-23T15:00:24 *** harrymm has quit IRC
2092016-08-23T15:00:30 <wumpus> payment protocol *needs* TLS, we're not going to do without OpenSSL there
2102016-08-23T15:00:51 <wumpus> well it would be possible to use PolarSSL
2112016-08-23T15:01:07 *** Chris_Stewart_5 has quit IRC
2122016-08-23T15:01:16 <wumpus> AFAIK qt can use that as drop-in replacement
2132016-08-23T15:02:11 <wumpus> not that I'm sure why it would be better
2142016-08-23T15:03:33 *** cryptapus_ has joined #bitcoin-core-dev
2152016-08-23T15:05:16 *** cryptapus has quit IRC
2162016-08-23T15:06:50 <wumpus> and libressl
2172016-08-23T15:19:23 *** harrymm has joined #bitcoin-core-dev
2182016-08-23T15:24:42 <instagibbs> \o/ congrats
2192016-08-23T15:26:52 *** harrymm has quit IRC
2202016-08-23T15:28:18 <sipa> w00t
2212016-08-23T15:32:00 <MarcoFalke> wumpus: What about adding a link to https://bitcoin.org/bin/bitcoin-core-0.13.0/ on the tag ( https://github.com/bitcoin/bitcoin/releases/new?tag=v0.13.0 )
2222016-08-23T15:32:31 <wumpus> sounds good to me
2232016-08-23T15:33:13 <MarcoFalke> This helps to make clear that the zip and tarballs are "not official" but provided by GitHub
2242016-08-23T15:33:27 <wumpus> right
2252016-08-23T15:33:34 <wumpus> and would point people to actual executables
2262016-08-23T15:33:56 <wumpus> is it possible to add text there? I've never been in that interface I think
2272016-08-23T15:41:51 <MarcoFalke> Jup, you can add anything
2282016-08-23T15:41:54 <MarcoFalke> Even the binaries
2292016-08-23T15:42:04 <MarcoFalke> But I would advise against adding anything but text
2302016-08-23T15:42:35 <MarcoFalke> "Anyone" can change it anytime.
2312016-08-23T15:42:43 <wumpus> yes I wouldn't want to add the binaries there, that's just confusing, especially as the source tarballs don't match our gitian-generated oens
2322016-08-23T15:42:50 *** fengling has joined #bitcoin-core-dev
2332016-08-23T15:45:45 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2342016-08-23T15:46:29 *** harrymm has joined #bitcoin-core-dev
2352016-08-23T15:47:46 *** fengling has quit IRC
2362016-08-23T15:47:49 <GitHub48> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/9358893518a19f38eab9186c768ad81c7a2f9cec
2372016-08-23T15:47:49 <GitHub48> bitcoin/master 9358893 Wladimir J. van der Laan: doc: Add historical release notes for 0.12.1 0.13.0
2382016-08-23T15:47:54 *** harrymm has quit IRC
2392016-08-23T15:48:09 *** harrymm has joined #bitcoin-core-dev
2402016-08-23T15:50:00 *** harrymm has quit IRC
2412016-08-23T15:50:15 *** harrymm has joined #bitcoin-core-dev
2422016-08-23T15:54:26 *** laurentmt has joined #bitcoin-core-dev
2432016-08-23T15:54:59 *** laurentmt has quit IRC
2442016-08-23T15:56:44 *** cryptapus_ is now known as cryptapus
2452016-08-23T16:01:35 *** ryan`c is now known as ryan-c
2462016-08-23T16:02:08 *** Chris_Stewart_5 has quit IRC
2472016-08-23T16:03:00 *** ryan-c is now known as ryan`c
2482016-08-23T16:04:01 *** ryan`c is now known as ryan-c
2492016-08-23T16:06:28 <wumpus> woohoo \o/ congrats everyone
2502016-08-23T16:06:33 <wumpus> on to 0.13.1
2512016-08-23T16:07:30 <wumpus> bleh, having trouble with updating bitcoin.org https://github.com/bitcoin-dot-org/bitcoin.org/pull/1348
2522016-08-23T16:08:41 <timothy> should I enable zeromq?
2532016-08-23T16:11:16 <wumpus> are you planning to use it?
2542016-08-23T16:14:29 <btcdrak> wumpus: check your email please
2552016-08-23T16:19:13 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2562016-08-23T16:26:43 *** otium has joined #bitcoin-core-dev
2572016-08-23T16:27:56 *** zooko has joined #bitcoin-core-dev
2582016-08-23T16:29:26 <otium> To all the Core-dev
2592016-08-23T16:29:26 <otium> thank you for the great work and for our Bitcoin that you are nursing for all of us
2602016-08-23T16:29:27 <otium> I believe we are numerous QUIET watchers who are supporting all of you
2612016-08-23T16:29:27 <otium> Thanks !
2622016-08-23T16:29:48 *** otium has left #bitcoin-core-dev
2632016-08-23T16:30:47 *** Ylbam has joined #bitcoin-core-dev
2642016-08-23T16:35:08 *** juscamarena has quit IRC
2652016-08-23T16:37:29 *** harrymm has quit IRC
2662016-08-23T16:39:02 *** BashCo_ has joined #bitcoin-core-dev
2672016-08-23T16:39:29 *** BashCo has quit IRC
2682016-08-23T16:43:06 *** jannes has quit IRC
2692016-08-23T16:44:21 *** fengling has joined #bitcoin-core-dev
2702016-08-23T16:45:00 *** eenoch has quit IRC
2712016-08-23T16:45:33 *** eenoch has joined #bitcoin-core-dev
2722016-08-23T16:46:14 *** zooko` has joined #bitcoin-core-dev
2732016-08-23T16:46:35 *** Chris_Stewart_5 has quit IRC
2742016-08-23T16:47:53 *** zooko has quit IRC
2752016-08-23T16:48:02 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2762016-08-23T16:49:06 *** fengling has quit IRC
2772016-08-23T16:53:32 *** BashCo_ has quit IRC
2782016-08-23T16:54:22 *** laurentmt has joined #bitcoin-core-dev
2792016-08-23T16:54:27 *** laurentmt has quit IRC
2802016-08-23T16:55:45 *** harrymm has joined #bitcoin-core-dev
2812016-08-23T17:04:40 <luke-jr> petertodd: re your ACP-by-default PR: wouldn't this enable someone to add garbage inputs (spending, for example, the 0-value p2pool anyone-can-spend UTXOs) to high-fee transactions, avoiding reducing the fee enough to allow RBF by the original tx? (anyone else find themselves doing attack scenarios like this in dreams? O.o)
2822016-08-23T17:05:16 <wumpus> thanks otium
2832016-08-23T17:08:50 *** rubensayshi has quit IRC
2842016-08-23T17:10:18 <instagibbs> luke-jr, might be a standard rule that all the ACP inputs have to increase the feerate of the transaction?
2852016-08-23T17:10:35 <instagibbs> (I haven't thought this through)
2862016-08-23T17:11:01 <instagibbs> that immediately rules out 0-value by definition, for one
2872016-08-23T17:11:02 *** adiabat has quit IRC
2882016-08-23T17:11:14 *** adiabat has joined #bitcoin-core-dev
2892016-08-23T17:14:35 <luke-jr> instagibbs: the spam input wouldn't necessarily be ACP, and in any case you'd see the spam-malleated version first
2902016-08-23T17:15:19 *** adiabat has quit IRC
2912016-08-23T17:15:29 <instagibbs> luke-jr, well, if my premise was correct the latter part wouldn't "matter", but my premise is wrong it seems
2922016-08-23T17:15:31 *** adiabat has joined #bitcoin-core-dev
2932016-08-23T17:26:11 <michagogo> 18:47:51 <GitHub48> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/9358893518a19f38eab9186c768ad81c7a2f9cec 18:47:51 <GitHub48> bitcoin/master 9358893 Wladimir J. van der Laan: doc: Add historical release notes for 0.12.1 0.13.0
2942016-08-23T17:26:21 <michagogo> Backport that commit to 0.13?
2952016-08-23T17:26:42 <michagogo> (Maybe also 0.12, if we think there's a chance there'll be a .2?)
2962016-08-23T17:27:05 <michagogo> Well, "backport"
2972016-08-23T17:27:19 <wumpus> possibly
2982016-08-23T17:27:34 <wumpus> I'm still fighting the bitcoin.org release announcement here https://github.com/bitcoin-dot-org/bitcoin.org/pull/1348
2992016-08-23T17:28:20 <wumpus> there is an error in the html generated from the md, but it doesn't tell where or the context
3002016-08-23T17:28:52 <wumpus> I thought I'd try to bisect it, divide up the page until I've found the part of the page where it happens but the check is so slow that that's pointless
3012016-08-23T17:29:09 <btcdrak> ping harding
3022016-08-23T17:29:19 <wumpus> also can't run the tests locally, something about "Your Ruby version is 2.3.1, but your Gemfile specified 2.0.0
3032016-08-23T17:29:19 <wumpus> "
3042016-08-23T17:29:22 <wumpus> fuck ruby, really
3052016-08-23T17:29:26 *** Yogh has quit IRC
3062016-08-23T17:31:48 *** BashCo has joined #bitcoin-core-dev
3072016-08-23T17:31:49 <kanzure> use rbenv
3082016-08-23T17:31:53 <kanzure> or rvm
3092016-08-23T17:32:45 *** juscamarena has joined #bitcoin-core-dev
3102016-08-23T17:32:49 *** Yogh has joined #bitcoin-core-dev
3112016-08-23T17:33:53 <wumpus> can anyone that is able to run those scripts send me the malformed html file? thanks
3122016-08-23T17:35:16 <kanzure> you can use after_failure in the travis-ci yaml file to upload or store files from a failed build
3132016-08-23T17:36:49 <wumpus> good idea, or just cat the thing into the travis log
3142016-08-23T17:37:11 <kanzure> hah.
3152016-08-23T17:38:28 <luke-jr> wumpus: btw, the ann ML email doesn't verify either (not even the text/plain one)
3162016-08-23T17:38:46 <wumpus> it does verify here before sending
3172016-08-23T17:39:18 <wumpus> not sure what I'm doing wrong
3182016-08-23T17:39:30 <wumpus> getting kind of annoyed by this, nothing is working as it should
3192016-08-23T17:39:31 <luke-jr> the ML is doing some kind of changes, adding a footer at least; that's outside the signature, but who knows what else it's touching
3202016-08-23T17:39:43 <sipa> sigh
3212016-08-23T17:40:34 <wumpus> maybe MLs are unsuited for sending signed messages
3222016-08-23T17:40:49 <wumpus> next time i'll just upload the .asc file and send a link...
3232016-08-23T17:41:05 <luke-jr> probably. but this is a private ML, so it should be possible to configure it to just send like a regular PGP-signed email..
3242016-08-23T17:41:17 <luke-jr> I would think anyway
3252016-08-23T17:41:22 <wumpus> possible, but I don't have time to look into that stuff really
3262016-08-23T17:42:03 <wumpus> there's tons of subtle changes that can invalidate a gpg signature
3272016-08-23T17:42:08 <Lauda> Compact blocks is enabled by default in 0.13.0?
3282016-08-23T17:42:13 <wumpus> I spent multiple days in that rabbit hole once
3292016-08-23T17:42:14 <instagibbs> Lauda, yes
3302016-08-23T17:42:26 <Lauda> I see, time to update then. Thanks!
3312016-08-23T17:42:33 <wumpus> man it's 2016 and even basic shit like that isn't working
3322016-08-23T17:42:57 <wumpus> stuff like that was working better in the 90's
3332016-08-23T17:42:59 <luke-jr> FWIW, my BFGMiner announce list on nongnu.org works fine for PGP
3342016-08-23T17:43:07 <wumpus> maybe I'm just getting too old
3352016-08-23T17:43:18 <sipa> who manages the bitcoin-dev list, actually?
3362016-08-23T17:43:55 <sipa> maybe it is a particular setting
3372016-08-23T17:44:11 <wumpus> if only the mailing list sent me my own message, I could compare
3382016-08-23T17:44:12 <luke-jr> bitcoin core ML is different from bitcoin-dev; I imagine btcdrak manages it
3392016-08-23T17:44:16 <TD-Linux> enigmail correctly detects the part of the message that is signed
3402016-08-23T17:44:26 <luke-jr> wumpus: I'll forward it
3412016-08-23T17:44:44 <wumpus> oh wait you mean the notification list? I should have that one, I have a test message
3422016-08-23T17:44:57 <wumpus> TD-Linux: that's the one from bitcoin-dev?
3432016-08-23T17:45:18 <TD-Linux> yes
3442016-08-23T17:45:20 <luke-jr> wumpus: yes
3452016-08-23T17:45:53 *** fengling has joined #bitcoin-core-dev
3462016-08-23T17:46:01 <TD-Linux> actually no, it's bitcoin-core-dev. I haven't gotten the bitcoin-dev one yet
3472016-08-23T17:46:03 <wumpus> ok, so that one works, that's good to hear. There was already a complainer about that too, but he had the digest mode, so probably that messed up the message
3482016-08-23T17:46:31 <luke-jr> https://lists.gnu.org/mailman/listinfo/bfgminer-announce says it uses Mailman 2.1.21, so that's a known-usable ML sw
3492016-08-23T17:46:54 *** zooko` has quit IRC
3502016-08-23T17:47:03 <wumpus> bitcoin-core-dev is the same host and software as bitcoin-dev
3512016-08-23T17:47:20 <achow101> Copying the text from the bitcoin-dev mailing list archive verifies fine
3522016-08-23T17:47:27 *** zooko` has joined #bitcoin-core-dev
3532016-08-23T17:47:31 *** Sosumi has quit IRC
3542016-08-23T17:47:37 <instagibbs> yeah i did archive myself
3552016-08-23T17:49:06 <TD-Linux> it looks like I only got one of the two messages. does mailman deduplicate magically?
3562016-08-23T17:50:17 <kanzure> mail clients sometimes deduplicate on their own
3572016-08-23T17:52:01 <wumpus> this is the diff between the mail I sent and the one I received from bitcoin-announce: https://gist.github.com/laanwj/3807c6024c6c28ae06e567a63045fb25
3582016-08-23T17:52:09 <wumpus> I don't see any difference between the green and red lines
3592016-08-23T17:52:16 <wumpus> maybe I should open the diff in a hex editor...
3602016-08-23T17:52:37 *** zooko` has quit IRC
3612016-08-23T17:52:46 *** fengling has quit IRC
3622016-08-23T17:53:11 *** zooko` has joined #bitcoin-core-dev
3632016-08-23T17:53:42 <wumpus> 2d 20 20 at the beginning of a line becomes 2d a0 20
3642016-08-23T17:53:44 <wumpus> wow
3652016-08-23T17:54:51 <wumpus> oh wait no, 2d is the '-'. No, 20 20 at the beginning of a line becomes c2 a0 20
3662016-08-23T17:55:05 <wumpus> it's doing unicode magic!
3672016-08-23T17:56:09 <sipa> unicode magic... we should call that unicornde
3682016-08-23T17:56:16 <wumpus> lol sipa :D
3692016-08-23T17:57:00 *** gazhaz has joined #bitcoin-core-dev
3702016-08-23T18:00:27 <wumpus> so it looks like spaces are converted into non-breaking spaces
3712016-08-23T18:00:41 <wumpus> that could be an option
3722016-08-23T18:00:55 <sipa> solution: use non-breaking spaces in the announcement email!
3732016-08-23T18:01:08 <sipa> so which of the two lists does this?
3742016-08-23T18:01:34 *** gazhaz has quit IRC
3752016-08-23T18:02:30 <luke-jr> sipa: the announcement ML on bitcoincore.org
3762016-08-23T18:03:28 <luke-jr> hmm, I need an announce ML for Knots too. :x
3772016-08-23T18:04:44 <btcdrak> luke-jr: bitcoin-core-dev mailing list is another LF managed list.
3782016-08-23T18:05:01 <luke-jr> btcdrak: I'm aware, but that's not the list with the problem
3792016-08-23T18:05:40 <btcdrak> verifying by copy paste from the ML archive works fine https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2016-August/000018.html
3802016-08-23T18:05:42 *** aalex_ has joined #bitcoin-core-dev
3812016-08-23T18:05:56 <sipa> luke-jr: i'm confused
3822016-08-23T18:06:01 <luke-jr> btcdrak: the problem is the https://bitcoincore.org/en/list/announcements/join/
3832016-08-23T18:06:35 <btcdrak> luke-jr: oh. sorry I didnt understand. what happened?
3842016-08-23T18:07:26 <btcdrak> oh i see, it doesnt verify. Weird, the last ones did.
3852016-08-23T18:07:29 <luke-jr> btcdrak: it modified the message invalidating the PGP sig
3862016-08-23T18:08:59 <btcdrak> wumpus: I see what happened, I think you might have pasted it in the HTML window, so if you view the message original source there are HTML entities /tags all over the pace
3872016-08-23T18:09:02 <btcdrak> place*
3882016-08-23T18:09:15 <wumpus> after undoing the substititions (d.replace(b'\xc2\xa0',b'\x20')) it still does't pass, it also converts \#7840 on line 288 to #7840
3892016-08-23T18:09:22 <btcdrak> e.g https://i.imgur.com/oAzcLYb.png
3902016-08-23T18:09:28 *** aalex has quit IRC
3912016-08-23T18:11:29 <wumpus> btcdrak: I'm checking the text/plain attachment, not the html one, that's hopeless I'd fathom
3922016-08-23T18:12:04 <btcdrak> let me login and make a test with the test list
3932016-08-23T18:12:05 <btcdrak> sec
3942016-08-23T18:13:36 <sipa> i wonder whether we shouldn't link to the gitian build results in announcement emails
3952016-08-23T18:14:10 <sipa> it's probably not something every user should be confronted with, but i do think it is important to make this part of our process visible
3962016-08-23T18:14:24 <wumpus> I'm fine with that
3972016-08-23T18:14:42 <wumpus> I've added the hashes on recommendation of btcdrak, I'm fine with adding even more stuff next time
3982016-08-23T18:15:08 <btcdrak> and hopefully we'll have the verification too then as well.
3992016-08-23T18:15:12 <btcdrak> wumpus: pm
4002016-08-23T18:17:02 <sipa> btcdrak: not for 0.13.1 :)
4012016-08-23T18:18:08 <MarcoFalke> wumpus: Fingers crossed: https://github.com/bitcoin-dot-org/bitcoin.org/pull/1349
4022016-08-23T18:18:39 *** TomMc has quit IRC
4032016-08-23T18:20:23 <wumpus> gah I had just found out how to inject a cat into the right place into the makefile
4042016-08-23T18:20:27 <wumpus> but thanks :)
4052016-08-23T18:20:32 <wumpus> hope it solves it
4062016-08-23T18:22:20 *** TomMc has joined #bitcoin-core-dev
4072016-08-23T18:23:16 *** Lauda has quit IRC
4082016-08-23T18:29:45 *** zooko` has quit IRC
4092016-08-23T18:34:14 <wumpus> it passes with "sed 's/\xc2\xa0/ /g' /tmp/test | sed 's/^ #7840/ \\#7840/g' |gpg"
4102016-08-23T18:34:24 <wumpus> where /tmp/test is the exported text/plain message
4112016-08-23T18:34:46 *** Arichy has joined #bitcoin-core-dev
4122016-08-23T18:34:49 <wumpus> so we should probably publish a validation FAQ for wumpus' botched gpg messages
4132016-08-23T18:36:20 <gmaxwell> I was about to report that the list message doesn't verify.
4142016-08-23T18:37:37 <Arichy> Glad to hear that You are aware of the email signature problem. Same here with Claws Mail 3.11.1 . And I am wondering why the Email is not signed with the release signing key. I had to google the email signing key....
4152016-08-23T18:37:59 <wumpus> I should just give up trying to send GPG signed messages
4162016-08-23T18:39:00 <gmaxwell> Arichy: because the release signing key is kept offline and only used for release signing, presumably.
4172016-08-23T18:39:01 <wumpus> gmaxwell: the announce-list right? bitcoin-dev and bitcoin-core-dev messages should pass
4182016-08-23T18:39:13 <wumpus> I don't sign mails with a release-signing key
4192016-08-23T18:39:16 <wumpus> that's not what it's for
4202016-08-23T18:39:35 <wumpus> it only signs SHA256SUMS.asc files, if you want more of it, I' msorry to disappoint you
4212016-08-23T18:40:01 <kanzure> presumably the release signing key is only for release signing
4222016-08-23T18:40:11 <kanzure> announcement emails should probably not be signed by a release key
4232016-08-23T18:40:14 <wumpus> yes, trange uh
4242016-08-23T18:40:16 <kanzure> (instead signed by some other key)
4252016-08-23T18:40:26 <wumpus> although how kanzure words it does make sense
4262016-08-23T18:40:28 <gmaxwell> wumpus: yes.
4272016-08-23T18:40:50 <wumpus> gmaxwell: next time I'll convert spaces to non-breaking spaces first and it should work
4282016-08-23T18:41:02 <kanzure> oh this was email client fault?
4292016-08-23T18:41:08 <gmaxwell> wumpus: though if the content isn't plain ascii that might cause other mangling elsewhere.
4302016-08-23T18:41:11 <wumpus> (assuming there's no \# in the release notes)
4312016-08-23T18:41:54 <wumpus> kanzure: no, the client is not at fault, the list that failed to pass it through un-mangled has a web interface, the two lists I sent to with mutt did fine
4322016-08-23T18:42:15 <wumpus> gmaxwell: oh yes it may mangle it in another stage, fun!
4332016-08-23T18:42:18 <kanzure> oh. i'm not aware of a web interface for sending email to -announce.
4342016-08-23T18:42:24 <Arichy> @kanzure Makes sense regarding security to keep the release signing keys seperate, only from a user point of view, with the publicity about checking sigs, I thout ok let's import wumpus' key but that was the wrong one, and after googeling the missing one, that failed :-(
4352016-08-23T18:42:26 <wumpus> unicornde indeed
4362016-08-23T18:42:54 <sipa> wumpus: solution: next time just post a link to the bitcoin-core-dev LM archove page for the announcement mail :)
4372016-08-23T18:43:07 <kanzure> Arichy: one might think this is a feature not a bug of the release process- that users can recognize verification failure.
4382016-08-23T18:43:15 *** pedrobranco has quit IRC
4392016-08-23T18:43:25 <sipa> Arichy: i'm happy to see that therr are people who take that suggestion to verify signatures seriously
4402016-08-23T18:43:42 *** pedrobranco has joined #bitcoin-core-dev
4412016-08-23T18:43:53 <wumpus> sipa: heh, yes posting a link is probably the best idea, maybe it'll even be let through unmangled if signed
4422016-08-23T18:44:00 <gmaxwell> Arichy: it's signed with the same key as last release.
4432016-08-23T18:44:11 <wumpus> oh wait signing a link makes no sense
4442016-08-23T18:46:04 <Arichy> @gmaxwell I had an old other wumpus key that had expired a year ago or so, I deleted that. Maybe last time I was not so aware of checking the sigs
4452016-08-23T18:46:22 <btcdrak> gmaxwell: we've found the issue and workaround for the announce list
4462016-08-23T18:46:41 <wumpus> Arichy: I've signed the release signing key with my main key. There is no 'old wumpus key', I have a personal key, which I've used for years, and a release sigining key
4472016-08-23T18:46:42 *** pedrobra_ has joined #bitcoin-core-dev
4482016-08-23T18:47:03 *** juscamarena has quit IRC
4492016-08-23T18:47:07 <gmaxwell> Arichy: it's probably the same key but you needed to fetch an updated expiration.
4502016-08-23T18:47:40 <gmaxwell> Arichy: it's good practice to set keys to expire to force people to potentially go fetch a revocation.
4512016-08-23T18:47:49 <wumpus> I only have those two: any other keys on GPG keyservers, if they exist, are false
4522016-08-23T18:47:51 <Arichy> @gmaxwell I am very surprised of that! Did not know about something like that
4532016-08-23T18:47:52 *** pedrobranco has quit IRC
4542016-08-23T18:48:04 <gmaxwell> and then periodically update the expire if the key is still not believed to be compromised.
4552016-08-23T18:49:19 *** fengling has joined #bitcoin-core-dev
4562016-08-23T18:49:24 <Arichy> [little bit offensive] If I would be the NSA or the ZhÅnghuá RénmÃn Gònghéguó GuójiÄ Änquánbù , I would keep this Email and PGP crap forever
4572016-08-23T18:49:45 <MarcoFalke> Error: Start tag a seen but an element of the same type was already open
4582016-08-23T18:49:51 <MarcoFalke> ull/7762"><a href="https://github.com/bitcoin/bitcoin/pull/7762">#7762<
4592016-08-23T18:49:57 <wumpus> my main key has fingerprint 71A3 B167 3540 5025 D447 E8F2 7481 0B01 2346 C9A6, the release signing key is 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964
4602016-08-23T18:50:08 <luke-jr> also, expiration means it self-"revokes" if you lose the private key ;)
4612016-08-23T18:50:10 <wumpus> not that you should believe that coming from somone pretending to be wumpus on IRC
4622016-08-23T18:50:13 <wumpus> or something
4632016-08-23T18:50:30 <MarcoFalke> Maybe the hash tag before 7762?
4642016-08-23T18:50:55 *** pedrobra_ has quit IRC
4652016-08-23T18:51:18 <wumpus> oh my cat worked
4662016-08-23T18:52:25 <wumpus> <a href="https://github.com/bitcoin/bitcoin/pull/7762"><a href="https://github.com/bitcoin/bitcoin/pull/7762">#7762</a></a> yes that definitely doesn't look like standards-compliant HTML
4672016-08-23T18:53:09 <Arichy> @sipa Glad to get positive feedback :-)
4682016-08-23T18:53:17 <wumpus> though I'm sure internet explorer would just accept it...
4692016-08-23T18:53:19 <gmaxwell> nested links.
4702016-08-23T18:54:06 *** fengling has quit IRC
4712016-08-23T18:54:21 <GitHub149> [bitcoin] roques closed pull request #8565: .gitignore TAGS and emacs lock files (master...gitignore) https://github.com/bitcoin/bitcoin/pull/8565
4722016-08-23T18:54:24 <MarcoFalke> They call it Edge, now
4732016-08-23T18:55:14 <wumpus> I've factored the # out of the [], let's see if that does it
4742016-08-23T18:55:49 <wumpus> MarcoFalke: if it was that simple, I'm fairly sure that windows 10 has both IE and Edge
4752016-08-23T18:57:50 <GitHub45> [bitcoin] MarcoFalke closed pull request #8527: Take minRelayTxFee into account in FEEFILTER messages (master...clampfeefilter) https://github.com/bitcoin/bitcoin/pull/8527
4762016-08-23T19:02:00 *** paveljanik has joined #bitcoin-core-dev
4772016-08-23T19:04:04 *** jcorgan has quit IRC
4782016-08-23T19:06:02 <PatBoy> can i ask a question n the spec of 0.13.0 here ? or just developement ? (sry to ask)
4792016-08-23T19:06:16 <luke-jr> PatBoy: #bitcoin
4802016-08-23T19:06:32 <PatBoy> okk thx
4812016-08-23T19:06:34 <PatBoy> sry
4822016-08-23T19:06:39 *** spudowiar has quit IRC
4832016-08-23T19:06:52 *** Arichy has quit IRC
4842016-08-23T19:07:46 *** juscamarena has joined #bitcoin-core-dev
4852016-08-23T19:12:02 <MarcoFalke> wumpus: Passed!1!!
4862016-08-23T19:12:07 <wumpus> whooooo
4872016-08-23T19:12:21 <wumpus> thanks, going to clean up that pull
4882016-08-23T19:22:26 *** juscamarena has quit IRC
4892016-08-23T19:30:05 *** spudowiar has joined #bitcoin-core-dev
4902016-08-23T19:30:44 *** MarcoFalke has left #bitcoin-core-dev
4912016-08-23T19:33:26 *** juscamarena has joined #bitcoin-core-dev
4922016-08-23T19:39:18 *** aalex has joined #bitcoin-core-dev
4932016-08-23T19:40:40 *** aalex__ has joined #bitcoin-core-dev
4942016-08-23T19:42:40 *** aalex_ has quit IRC
4952016-08-23T19:43:50 *** pedrobranco has joined #bitcoin-core-dev
4962016-08-23T19:44:54 *** aalex has quit IRC
4972016-08-23T19:50:50 *** fengling has joined #bitcoin-core-dev
4982016-08-23T19:52:59 *** pedrobranco has quit IRC
4992016-08-23T19:53:04 *** cryptapus has quit IRC
5002016-08-23T19:53:32 *** pedrobranco has joined #bitcoin-core-dev
5012016-08-23T19:55:46 *** fengling has quit IRC
5022016-08-23T19:57:58 *** pedrobranco has quit IRC
5032016-08-23T19:58:29 <Chris_Stewart_5> Is the 'flags' hex representation right for this documentation on the bitcoin developer reference wrt to merkle blocks?
5042016-08-23T19:58:31 <Chris_Stewart_5> https://bitcoin.org/en/developer-reference#merkleblock
5052016-08-23T19:58:52 <Chris_Stewart_5> in the hex dump part
5062016-08-23T19:59:07 *** Guyver2 has quit IRC
5072016-08-23T19:59:10 <Chris_Stewart_5> wouldn't it be 'd1' instead of '1d'?
5082016-08-23T19:59:14 *** Guyver2 has joined #bitcoin-core-dev
5092016-08-23T20:02:55 <sipa> Chris_Stewart_5: no, in a hex dump you put the more significant of the 2 characters for a byte first
5102016-08-23T20:03:55 *** spudowiar has quit IRC
5112016-08-23T20:04:04 *** Guyver2 has quit IRC
5122016-08-23T20:09:34 *** juscamarena has quit IRC
5132016-08-23T20:13:13 *** spudowiar has joined #bitcoin-core-dev
5142016-08-23T20:15:25 *** mol has joined #bitcoin-core-dev
5152016-08-23T20:18:29 *** molz has quit IRC
5162016-08-23T20:20:28 *** pedrobranco has joined #bitcoin-core-dev
5172016-08-23T20:24:52 *** pedrobranco has quit IRC
5182016-08-23T20:25:00 <GitHub47> [bitcoin] achow101 opened pull request #8566: Easy to use gitian building script (master...gitian-build-script) https://github.com/bitcoin/bitcoin/pull/8566
5192016-08-23T20:25:13 <Chris_Stewart_5> sipa: Just to be clear though, on the wire would it look like 'd1'?
5202016-08-23T20:25:23 <sipa> Chris_Stewart_5: who knows
5212016-08-23T20:25:39 <sipa> Chris_Stewart_5: it depends on the transmission technology
5222016-08-23T20:26:00 <sipa> from the application perspective, the wire contains bytes
5232016-08-23T20:26:31 <sipa> not individual bits
5242016-08-23T20:26:50 <sipa> and the wire will contain the byte commonly referred to as 1d
5252016-08-23T20:27:03 <Chris_Stewart_5> I guess what I am getting at is it serialized differently for a hex dump compared to what it would be serialized for and sent over the network?
5262016-08-23T20:27:16 <Chris_Stewart_5> For instance if you called HexStr on it would be d1 correct?
5272016-08-23T20:27:16 <sipa> ffs no
5282016-08-23T20:27:27 <sipa> no
5292016-08-23T20:27:33 <sipa> it would be 1d
5302016-08-23T20:30:47 *** pmienk has quit IRC
5312016-08-23T20:42:39 *** pmienk has joined #bitcoin-core-dev
5322016-08-23T20:43:33 <GitHub90> [bitcoin] djpnewton opened pull request #8567: Add default port numbers to REST doc (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8567
5332016-08-23T20:48:27 *** belcher has joined #bitcoin-core-dev
5342016-08-23T20:49:02 *** cryptapus_afk is now known as cryptapus
5352016-08-23T20:49:14 *** pmienk has quit IRC
5362016-08-23T20:52:20 *** fengling has joined #bitcoin-core-dev
5372016-08-23T20:57:06 *** fengling has quit IRC
5382016-08-23T21:02:01 *** pmienk has joined #bitcoin-core-dev
5392016-08-23T21:27:35 *** waxwing has quit IRC
5402016-08-23T21:28:31 *** waxwing has joined #bitcoin-core-dev
5412016-08-23T21:31:06 *** cryptapus is now known as cryptapus_afk
5422016-08-23T21:39:12 *** jl2012 has quit IRC
5432016-08-23T21:53:53 *** fengling has joined #bitcoin-core-dev
5442016-08-23T21:58:46 *** fengling has quit IRC
5452016-08-23T22:04:04 *** aalex__ is now known as aalex
5462016-08-23T22:04:37 *** pedrobranco has joined #bitcoin-core-dev
5472016-08-23T22:09:07 *** pedrobranco has quit IRC
5482016-08-23T22:18:27 *** Lauda has joined #bitcoin-core-dev
5492016-08-23T22:26:12 *** owowo has quit IRC
5502016-08-23T22:35:21 *** mol has quit IRC
5512016-08-23T22:37:36 *** moli has joined #bitcoin-core-dev
5522016-08-23T22:43:04 *** TomMc has quit IRC
5532016-08-23T22:55:24 *** fengling has joined #bitcoin-core-dev
5542016-08-23T23:00:06 *** fengling has quit IRC
5552016-08-23T23:03:10 *** owowo has joined #bitcoin-core-dev
5562016-08-23T23:56:24 *** fengling has joined #bitcoin-core-dev
5572016-08-23T23:59:05 *** cryptapus has joined #bitcoin-core-dev
5582016-08-23T23:59:06 *** cryptapus has joined #bitcoin-core-dev