1 2016-03-10 00:01:48 <Luke-Jr> I wonder if there's a better place than GitLab I can push my historical dns seed info to
 2 2016-03-10 00:02:09 <Luke-Jr> GitLab seems to be unresolvably incompetent; hasn't worked in months due to TCP MSS issues
 3 2016-03-10 00:05:40 <btcdrak> Luke-Jr: github
 4 2016-03-10 00:06:01 <Luke-Jr> btcdrak: GitHub has size limits :<
 5 2016-03-10 00:06:14 <btcdrak> Luke-Jr: not if you pay
 6 2016-03-10 00:06:21 <Luke-Jr> the repo is 6.5 GB so far
 7 2016-03-10 00:06:53 <btcdrak> luke-Jr: https://git-lfs.github.com/
 8 2016-03-10 00:07:18 <Luke-Jr> btcdrak: n/a when the files aren't large :P
 9 2016-03-10 00:07:20 <btcdrak> Luke-Jr: sounds like you need a VPS for $60 a year
10 2016-03-10 00:07:31 <Luke-Jr> eh, I suppose I could throw it on my dedi
11 2016-03-10 00:07:37 <Luke-Jr> but no fancy GUI
12 2016-03-10 00:07:48 <Luke-Jr> … actually, it is on my dedi, so it'd be like a symlink
13 2016-03-10 00:08:07 <btcdrak> you can install gitlab :)
14 2016-03-10 00:09:58 <Luke-Jr> btcdrak: it's Ruby :<
15 2016-03-10 00:11:50 <btcdrak> Digital ocean have one click install of gitlab.
16 2016-03-10 00:12:46 <Luke-Jr> -.-
17 2016-03-10 00:20:53 <Luke-Jr> there http://luke.dashjr.org/programs/bitgit/w/luke-jr-bitcoin-dnsseed-historical-seeds.txt.git
18 2016-03-10 00:21:51 <Luke-Jr> although the original point of doing it on GitLab was so I didn't upload 7 GB to every fetcher..
19 2016-03-10 01:11:00 <Chris_Stewart_5> jonasschnelli: In case you were curious, the problem I was having was that I was passing the hash of the p2sh scriptPubKey instead of passing the redeemScript embedded in the scriptSig
20 2016-03-10 01:11:19 <Chris_Stewart_5> hash of the redeemScript* instead of the full redeemScript
21 2016-03-10 16:40:46 <dangersalad> Could anyone tell me the easiest way for me to test RBF transactions on testnet? I found this (https://github.com/petertodd/replace-by-fee-tools) but it seems to not be working with testnet.. I may need to dive into the code there unless someone has a quick way
22 2016-03-10 16:46:12 <dangersalad> Scratch that there is a -t flag.. sorry to bother.
23 2016-03-10 16:46:39 <dangersalad> One other question though, what would cause a transaction to display "bip125-replaceable":"unknown" instead of yes or no?
24 2016-03-10 16:48:41 <instagibbs> https://github.com/bitcoin/bitcoin/blob/b6e00af8193f46fa02af13c2e9852a6bd7461d00/src/wallet/rpcwallet.cpp#L89
25 2016-03-10 16:49:28 <dangersalad> thanks instagibbs
26 2016-03-10 17:18:24 <sdaftuar> dangersalad: if it's in your wallet, but not in your mempool, then you can get "unknown"
27 2016-03-10 17:19:46 <sdaftuar> dangersalad: the issue is that we check a transaction for being bip125 replaceable by looking at whether it's signaling opt-in, or whether any of its unconfirmed ancestors are signaling opt-in
28 2016-03-10 17:20:57 <sdaftuar> this is easy to do for in-mempool transactions, but not for ones that aren't in the mempool, so we return "unknown" in that situation instead
29 2016-03-10 17:21:15 <dangersalad> sdaftuar: gotcha, thanks for the detail
30 2016-03-10 17:38:17 <instagibbs> sdaftuar, ah, the reasoning was non-obvious, thanks
31 2016-03-10 17:39:33 <lysobit> If someone wants to start contributing to Bitcoin core, what would be a good place to start to find work that needs to be done in core?
32 2016-03-10 17:43:40 <jouke> I guess: https://github.com/bitcoin/bitcoin/issues
33 2016-03-10 17:44:44 <lysobit> Kind of hard to filter out issues of priority, but I guess https://github.com/bitcoin/bitcoin/issues/3665 is a start
34 2016-03-10 17:50:31 <jonasschnelli> lysobit: you could pick an issue depending on your skills and interests.
35 2016-03-10 20:58:38 <e0__> exit
36 2016-03-10 22:52:57 <lysobit> fresh build from latest source, make check gives me 1 failed test: unknown location(0): fatal error in "AlertApplies": memory access violation at address: 0x00000001: no mapping at fault address
37 2016-03-10 22:52:57 <lysobit> test/addrman_tests.cpp(519): last checkpoint
38 2016-03-10 22:53:25 <lysobit> any ideas? couldn't find anything in the issues. it's configured with the --incomptaible-berkleydb flag