1 2018-03-11 00:33:04	0|bitcoin-git|[13bitcoin] 15eklitzke closed pull request #12664: Rename LevelDB background compaction thread (06master...06bgcompact) 02https://github.com/bitcoin/bitcoin/pull/12664
 2 2018-03-11 02:51:47	0|ProfMac_2|A rumor says that a core developer made a block-chain scanner to replace the znort scanner.  I would like to learn where this is.
 3 2018-03-11 02:55:12	0|Randolf|ProfMac_2:  If it's a rumour, then shouldn't the first step be to summarily dismiss it?
 4 2018-03-11 02:55:47	0|luke-jr|#bitcoin-core-dev is not "ask Core devs questions so you can build your scamcoin"
 5 2018-03-11 03:00:13	0|ProfMac_2|Randolf, verify.  As this is a direct place to do.
 6 2018-03-11 03:00:54	0|sipa|sounds totally plausible - many developers work on various projects
 7 2018-03-11 03:01:02	0|sipa|but i haven't heard about something like that
 8 2018-03-11 03:01:29	0|ProfMac_2|Thanks, sipa.
 9 2018-03-11 03:01:48	0|sipa|it's also the first time i hear znort mentioned in years - i sort of assume there have been various other related things
10 2018-03-11 03:04:08	0|ProfMac_2|I searched the best I could, and ended up there.  I'm starting to think that small utilities put into the best design place in the core-client is the best way to simultaneously get a working appliance, and learn the core code.
11 2018-03-11 03:06:46	0|Randolf|ProfMac_2:  Okay, fair enough.
12 2018-03-11 03:24:43	0|windsok|ProfMac_2: not sure if it's what you are looking for, but https://github.com/citp/BlockSci has a parser
13 2018-03-11 03:25:39	0|ProfMac_2|Thank you.  I'll look now.
14 2018-03-11 03:26:04	0|ProfMac_2|Um, 2 days since an update is scary.
15 2018-03-11 03:27:08	0|sipa|scary long or scary short?
16 2018-03-11 03:28:01	0|ProfMac_2|I think 19 year old are proud when they did an update minutes before an important meeting.  Older supervisors think the design is good when it is working fine 5 years later.
17 2018-03-11 03:28:49	0|ProfMac_2|'though I formed those attitudes before git was around.
18 2018-03-11 03:34:02	0|sipa|"design still working 5 years later" is not the same as "no development at all"
19 2018-03-11 03:40:02	0|Randolf|sipa++
20 2018-03-11 03:43:23	0|ProfMac_2|true.
21 2018-03-11 12:20:14	0|esotericnonsense|i mean, last commit to bitcoin/bitcoin is yesterday. :P
22 2018-03-11 14:16:26	0|bitcoin-git|[13bitcoin] 15nvercamm opened pull request #12668: Doc: Ubuntu xenial first dependencies (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/12668
23 2018-03-11 14:47:58	0|fanquake|wumpus/sipa could you ban Dungchuot7979 from GH
24 2018-03-11 15:27:57	0|kallewoof|what is GH?
25 2018-03-11 15:33:17	0|achow101|github
26 2018-03-11 15:38:26	0|kallewoof|oh
27 2018-03-11 18:07:27	0|sipa|sdaftuar: seems my benchmark was off, and the jacobi symbol implementation in GMP takes 2us rather than 0.2us; this means it's hardly worth it to use for hashing onto a curve for ECMH (it'd be 8.6us per update rather than 9.3us per update)
28 2018-03-11 18:45:17	0|bitcoin-git|[13bitcoin] 15aaassad opened pull request #12670: Link (060.9...06master) 02https://github.com/bitcoin/bitcoin/pull/12670
29 2018-03-11 18:47:12	0|bitcoin-git|[13bitcoin] 15sipa closed pull request #12670: Link (060.9...06master) 02https://github.com/bitcoin/bitcoin/pull/12670
30 2018-03-11 18:56:09	0|JHDHHHH|Hello guys
31 2018-03-11 18:57:06	0|JHDHHHH|I'm looking for an UTXO indexer with an (rest) api preferable
32 2018-03-11 18:57:19	0|JHDHHHH|I want to get all utxo by address
33 2018-03-11 18:57:28	0|JHDHHHH|any suggestions?
34 2018-03-11 21:32:17	0|bitcoin-git|13bitcoin/06master 140fbed98 15Akio Nakamura: [script] lint-whitespace: improve print linenumber...
35 2018-03-11 21:32:17	0|bitcoin-git|[13bitcoin] 15MarcoFalke pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/bb98aec6743e...d8d9162f5bad
36 2018-03-11 21:32:18	0|bitcoin-git|13bitcoin/06master 14d8d9162 15MarcoFalke: Merge #12572: [script] lint-whitespace: find errors more easily...
37 2018-03-11 21:33:12	0|bitcoin-git|[13bitcoin] 15MarcoFalke closed pull request #12572: [script] lint-whitespace: find errors more easily (06master...06morelinenumber) 02https://github.com/bitcoin/bitcoin/pull/12572
38 2018-03-11 21:49:04	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #12671: mempool: Avoid locking mutex that is already held by the same thread (06master...06avoid-locking-mutex-already-held) 02https://github.com/bitcoin/bitcoin/pull/12671
39 2018-03-11 22:28:55	0|bitcoin-git|[13bitcoin] 15practicalswift closed pull request #12671: mempool: Avoid locking mutex that is already held by the same thread (06master...06avoid-locking-mutex-already-held) 02https://github.com/bitcoin/bitcoin/pull/12671
40 2018-03-11 22:33:46	0|bitcoin-git|[13bitcoin] 15shmulim opened pull request #12672: Consensus: Remove unused dependencies (06master...06removed-unused-deps) 02https://github.com/bitcoin/bitcoin/pull/12672
41 2018-03-11 22:51:39	0|shmulim|First time pull-request here.. What is intended by this request "for steps to reproduce" in the given context? https://github.com/bitcoin/bitcoin/pull/12672
42 2018-03-11 22:52:37	0|sipa|shmulim: how did you find the unused dependencies?
43 2018-03-11 22:54:53	0|shmulim|peer-reviewed, removed and ran all tests without. did not use IWYU.
44 2018-03-11 22:55:42	0|sipa|right, but how do you know those are the only unused dependencies?
45 2018-03-11 23:01:17	0|shmulim|there may be other unused dependencies, this commit does not represent a comprehensive check..
46 2018-03-11 23:02:43	0|luke-jr|shmulim: just because it runs without them, doesn't mean they're unused (although in this case they are)
47 2018-03-11 23:06:08	0|sipa|shmulim: well if we're going to go through an effort to clean up unused dependencies, it would be nice to know it's xomprehensive
48 2018-03-11 23:06:13	0|sipa|*comprehensive
49 2018-03-11 23:09:17	0|luke-jr|would be nice if GCC/LLVM had a way to hide the stuff inherited from includes, such that it can at least detect missing dependencies
50 2018-03-11 23:10:32	0|shmulim|it is not comprehensive.. i'll leave a note on the PR.. thank you both for the pointers.. i'll look into iwyu.
51 2018-03-11 23:17:30	0|eklitzke|I am kind of confused about how CheckInputs works. since the script execution cache can return false positives, there must be a path where the scripts are checked without checking the cache. can someone explain how that works?
52 2018-03-11 23:23:40	0|sipa|eklitzke: how can it return false positives?
53 2018-03-11 23:24:10	0|sipa|all the context, data, and flags for validation are hashed cryptographically into the cache's key
54 2018-03-11 23:24:29	0|sipa|so at worst there is a discrepancy, and the entry just won't be found
55 2018-03-11 23:26:11	0|eklitzke|is it not a probabilistic data structure?
56 2018-03-11 23:28:15	0|sipa|it's probabilistic in the other direction
57 2018-03-11 23:28:29	0|eklitzke|i see
58 2018-03-11 23:29:10	0|sipa|and if you accept the chance of hash collisions on sha256, it also has a chance for false positives
59 2018-03-11 23:29:20	0|sipa|but if those are a concern, we have bigger proble.s
60 2018-03-11 23:31:10	0|eklitzke|i'm assuming that the problem of finding a sha256 collision is more difficult than finding a collision in the cache
61 2018-03-11 23:31:36	0|sipa|hmm?
62 2018-03-11 23:31:43	0|sipa|the cache stores the full hash
63 2018-03-11 23:32:00	0|eklitzke|ah
64 2018-03-11 23:32:01	0|sipa|its location can have collisions, in whicb case an entry will be evicted
65 2018-03-11 23:32:17	0|sipa|but that still only results in a false negative
66 2018-03-11 23:32:42	0|eklitzke|i had difficulty finding the original PR, it looks like the one that was merged on github is not the first PR put up (which probably has more of these details)
67 2018-03-11 23:33:20	0|eklitzke|actually i might be wrong, maybe this description is using "original PR" to refer to the unsquashed version
68 2018-03-11 23:33:24	0|eklitzke|https://github.com/bitcoin/bitcoin/pull/8895
69 2018-03-11 23:34:14	0|sipa|that PR is about the sigcache
70 2018-03-11 23:34:23	0|sipa|which is distinct from the scriptcache
71 2018-03-11 23:34:28	0|sipa|i think
72 2018-03-11 23:34:33	0|sipa|i'm not sure anymore
73 2018-03-11 23:38:16	0|eklitzke|ok i think i understand it now
74 2018-03-11 23:39:10	0|eklitzke|it's not really like a bloom filter because the original element is retained, and contains() does an == check if it finds an item in the cache, which is your point about it being probabilistic in the other direction
75 2018-03-11 23:39:52	0|eklitzke|so it just relies on sha256 of the item in the cache being unique
76 2018-03-11 23:41:13	0|sipa|it does a few interesting things
77 2018-03-11 23:41:29	0|sipa|every element can be in 8 different valid locations
78 2018-03-11 23:41:49	0|sipa|and it gets moved around to make space for new ones, unless a cycle forms
79 2018-03-11 23:42:21	0|sipa|and when an item is marked as expired, it it retained in the cache (and findable) but just available for overwriting