1 2016-12-11 01:47:09	0|meow|hi all
 2 2016-12-11 01:48:19	0|meow|i was wondering if i wanted to test myself and make a simple bitcoin app that is a website which allows you to enter an address and then list all the addresses that have sent the given address bitcoin, how would i go about doing this at a high level?
 3 2016-12-11 01:49:07	0|sipa_|try #bitcoin or #bitcoin-dev... bitcoin core can't do this
 4 2016-12-11 01:50:39	0|meow|ok ty
 5 2016-12-11 01:50:43	0|sipa_|(it doesn't have a model of 'addresses that send', only wallets)
 6 2016-12-11 05:02:14	0|bitcoin-git|[13bitcoin] 15gmaxwell opened pull request #9319: Break addnode out from the outbound connection limits. (06master...06addnode_own_count) 02https://github.com/bitcoin/bitcoin/pull/9319
 7 2016-12-11 13:19:10	0|bitcoin-git|[13bitcoin] 15MarcoFalke opened pull request #9322: [qa] Don't set unknown rpcserialversion (06master...06Mf1612-qaSerial) 02https://github.com/bitcoin/bitcoin/pull/9322
 8 2016-12-11 15:43:21	0|paveljanik|sipa_, restarting bitcoind, it was started at 13:17:26 and Import mempool run at 13:18:40, ie. more than one minute after the new start. Is this as designed? I was even able to getmempoolinfo in between...
 9 2016-12-11 16:10:16	0|sipa_|paveljanik: it runs after connecting blocks on disk
10 2016-12-11 16:10:59	0|paveljanik|sipa_, yes.
11 2016-12-11 16:11:04	0|paveljanik|I have added some debugging
12 2016-12-11 16:11:12	0|paveljanik|load speed here is 1000 tx per 10seconds...
13 2016-12-11 16:11:35	0|paveljanik|or even more:
14 2016-12-11 16:11:36	0|paveljanik|2016-12-11 16:10:49 Loadmempool tx 3000
15 2016-12-11 16:11:36	0|paveljanik|2016-12-11 16:11:09 Loadmempool tx 4000
16 2016-12-11 16:13:22	0|paveljanik|2016-12-11 16:11:27 Loadmempool tx 5000
17 2016-12-11 16:13:22	0|paveljanik|2016-12-11 16:11:51 Loadmempool tx 6000
18 2016-12-11 16:13:22	0|paveljanik|2016-12-11 16:11:59 Loadmempool tx 7000
19 2016-12-11 16:13:38	0|sipa_|transaction validation is not that fast
20 2016-12-11 16:16:45	0|paveljanik|I was a bit surprised that it took more than minute (67MB mempool.dat)
21 2016-12-11 17:04:46	0|bitcoin-git|[13bitcoin] 15rebroad closed pull request #9055: Skip processing of cmpctblocks we have previously downloaded. (06master...06SkipCmpctblocksPreviouslyDownloaded) 02https://github.com/bitcoin/bitcoin/pull/9055
22 2016-12-11 17:11:46	0|bitcoin-git|[13bitcoin] 15rebroad closed pull request #9300: Check for oversized getblocktxn message. (06master...06CheckOversizedGetblocktxns) 02https://github.com/bitcoin/bitcoin/pull/9300
23 2016-12-11 19:43:12	0|Chris_Stewart_5|How is OP_0 handled inside of a witness, because it is an empty byte vector when actually placed onto the stack? Is it replaced some where in the serialization code from 0x00 -> []?
24 2016-12-11 19:57:15	0|luke-jr|0x00 has always been []
25 2016-12-11 19:59:03	0|sipa_|OP_0 produces [] on the stack
26 2016-12-11 19:59:27	0|sipa|in the witness stack, we just bypass the opcode, and use [] directly
27 2016-12-11 20:02:22	0|Chris_Stewart_5|So that is done the witness serialization code? the 'bypass the opcode'?
28 2016-12-11 20:02:34	0|luke-jr|oh, hm. I guess small numbers take 2x the bytes in segwit then
29 2016-12-11 20:02:54	0|luke-jr|Chris_Stewart_5: segwit witnesses aren't scripts, so it's just automatic
30 2016-12-11 20:03:59	0|luke-jr|although AFAIK OP_0 is just serialized as 0 which is also the length of [] so I'm not sure why that specific case would appear any different?
31 2016-12-11 20:05:28	0|sipa|Chris_Stewart_5: scriptSigs being a script is just a legacy, probably intended to support delegation
32 2016-12-11 20:05:51	0|sipa|the script witness stack is just encoded as a vector of vectors of bytes
33 2016-12-11 20:06:30	0|Chris_Stewart_5|Maybe this is what I'm getting confused about, when a vector is '00' it is indicating that the length of the vector is zero in the witness, correct?
34 2016-12-11 20:06:44	0|sipa|yes
35 2016-12-11 20:06:52	0|Chris_Stewart_5|yeah, doh! Thanks guys.
36 2016-12-11 20:07:00	0|luke-jr|☺
37 2016-12-11 20:07:10	0|Chris_Stewart_5|luke-jr: What did you mean by 2x the bytes in segwit?
38 2016-12-11 20:07:50	0|Chris_Stewart_5|because they require a pushop to be encoded before the actual number if it is only a number in a byte vector?
39 2016-12-11 20:07:59	0|luke-jr|Chris_Stewart_5: OP_1 would be a single byte (0x81) in Script, but in segwit it is 0x01 (length) 0x01 (data)
40 2016-12-11 20:08:46	0|Chris_Stewart_5|Yeah, I think that is what was confusing me. A small but important difference
41 2016-12-11 20:10:09	0|luke-jr|of course, it rarely makes sense to have a small integer in a witness by itself I think
42 2016-12-11 20:10:16	0|luke-jr|usually it'd be part of the program
43 2016-12-11 20:10:32	0|Chris_Stewart_5|Yeah I agree, I can't think of anything off of the top of my head
44 2016-12-11 20:11:04	0|sipa|luke-jr: i recently generated a histogram of the sizes of pushes in scriptSigs
45 2016-12-11 20:11:28	0|sipa|there are 48M 1-byte pushes
46 2016-12-11 20:11:48	0|sipa|sorry, 23.5M 1-byte pushes
47 2016-12-11 20:12:04	0|luke-jr|sipa: exclude OP_1 and scriptSigs which are only OP_TRUE?
48 2016-12-11 20:12:09	0|luke-jr|OP_0*
49 2016-12-11 20:12:32	0|sipa|408M signatures
50 2016-12-11 20:12:42	0|sipa|359M pubkeys
51 2016-12-11 20:12:56	0|sipa|15.3M 107-byte pushes
52 2016-12-11 20:13:31	0|sipa|7.7M 72-byte pushes (= mostly non-DER signatures, as those aren't counted under the signatures field)
53 2016-12-11 20:15:33	0|sipa|0.5M 138-byte pushes
54 2016-12-11 20:15:42	0|sipa|all the rest is less than 0.2M
55 2016-12-11 20:17:13	0|luke-jr|1-byte pushes besides OP_0 and entire-scriptSig-is-OP_TRUE seem like they wouldn't be used much, but I have no real data measuring it
56 2016-12-11 20:25:42	0|sipa|i agree, i don't know what they're for
57 2016-12-11 20:27:42	0|gmaxwell|hm? checkmultisig paramters
58 2016-12-11 20:27:56	0|gmaxwell|oh in signatures. hm
59 2016-12-11 20:28:08	0|gmaxwell|well used to activate if branches.
60 2016-12-11 20:32:30	0|sipa|i would be surprised if there are 23M spends of outputs with branches in the chain
61 2016-12-11 20:33:54	0|sipa|(but i don't know)
62 2016-12-11 20:35:25	0|gmaxwell|Oh I missed the number, that is a lot
63 2016-12-11 20:37:01	0|gmaxwell|sipa: would you like me to give a crack at writing a release note for 9302?
64 2016-12-11 20:37:42	0|sipa|gmaxwell: sure
65 2016-12-11 20:49:10	0|gmaxwell|sipa: https://0bin.net/paste/49XqHf2k61I38lxn#pMcwMTsRWlKraOsU+dk93V-rv/if0qV+IRlrwTwil3f
66 2016-12-11 21:03:57	0|MarcoFalke|gmaxwell: ACK
67 2016-12-11 21:06:55	0|gmaxwell|How do we deal with release notes for backports  for features that are initially going into master?
68 2016-12-11 21:08:20	0|sipa|backport the release notes as well?
69 2016-12-11 21:09:45	0|MarcoFalke|Only create a pull against 0.13
70 2016-12-11 21:10:13	0|MarcoFalke|We don't need the release notes in 0.14, as the feature was already released
71 2016-12-11 21:21:08	0|bitcoin-git|[13bitcoin] 15gmaxwell opened pull request #9323: [0.13] Add release notes for wallet/mempool rejections. (PR #9302 and #9290) (060.13...06mempool_relnote) 02https://github.com/bitcoin/bitcoin/pull/9323