1 2017-09-19 00:26:31	0|achow101|0.15.0.1 needs to be released soon. A lot of people are reporting the nCustomFeeRadio bug
 2 2017-09-19 00:58:46	0|jtimon|review beg: https://github.com/bitcoin/bitcoin/pull/10669
 3 2017-09-19 02:25:13	0|bitcoin-git|[13bitcoin] 15theuni opened pull request #11363: net: Split socket create connect (06master...06split-socket-create-connect) 02https://github.com/bitcoin/bitcoin/pull/11363
 4 2017-09-19 02:33:57	0|cfields_|jonasschnelli: yes, will do
 5 2017-09-19 02:34:16	0|jonasschnelli|Thanks
 6 2017-09-19 04:03:36	0|cfields_|wtf, i totally missed the 0.15.0.1 tag. building/signing now.
 7 2017-09-19 04:11:28	0|achow101|so that's why it was taking so long
 8 2017-09-19 04:13:08	0|cfields_|:(
 9 2017-09-19 04:16:54	0|gmaxwell|cfields_: FWIW, the first I was aware of it was achow(?) asking about it in here or pieter telling someone to run it.
10 2017-09-19 04:17:00	0|gmaxwell|but I assumed you knew.
11 2017-09-19 04:18:15	0|cfields_|gmaxwell: i saw achow101's mention of 0.15.0.1 in backlog and checked the tags on a whim
12 2017-09-19 04:18:36	0|cfields_|just a freak failure of my notifications. Will update them.
13 2017-09-19 05:21:18	0|cfields_|gitian builders: v0.15.0.1 detached sigs pushed. Sorry for the delay.
14 2017-09-19 06:26:19	0|bitcoin-git|[13bitcoin] 15azuchi closed pull request #11357: doc: Fix description of maximumCount (06master...06fix-0.15.0-release-notes) 02https://github.com/bitcoin/bitcoin/pull/11357
15 2017-09-19 06:39:47	0|bitcoin-git|[13bitcoin] 15anditto opened pull request #11365: [Tests] Add Qt GUI tests to Overview and ReceiveCoin Page (06master...06Adding-Qt-tests) 02https://github.com/bitcoin/bitcoin/pull/11365
16 2017-09-19 07:42:18	0|bitcoin-git|[13bitcoin] 15mess110 closed pull request #11329: [test] Test abortrescan command (06master...06kallewoof/test-abort-rescan-2) 02https://github.com/bitcoin/bitcoin/pull/11329
17 2017-09-19 07:48:16	0|bitcoin-git|[13bitcoin] 15esotericnonsense opened pull request #11366: Trivial: RPC/getblockchaininfo: pruneheight is only present in pruned mode (06master...062017-09-getblockchaininfo-docs) 02https://github.com/bitcoin/bitcoin/pull/11366
18 2017-09-19 08:14:52	0|kallewoof|I don't really wanna waste anyone's time, but I've been trying to figure out the gitian build process lately and am having issues. I was following https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md and everything was fine down to "Getting and building the inputs". For one I had to cd into ../bitcoin/ for there to be a contrib/gitian-build.sh file (not mentioned, but no biggie),
19 2017-09-19 08:14:53	0|kallewoof|and secondly, it explodes messily when I run with the --setup flag. "lxcbr0: ERROR while getting interface flags: No such device [...]". Hints welcome.
20 2017-09-19 08:18:03	0|meshcollider|I had a similar issue, I gave up using the gitian-build.sh script and wrote a simple script of my own which basically follows the steps here: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#setup-and-perform-gitian-builds
21 2017-09-19 08:18:40	0|meshcollider|basically pull all the repos, checkout the tag, gbuild and then gsign for each OS
22 2017-09-19 08:20:48	0|meshcollider|its something to do with the `sudo ifconfig lxcbr0 up 10.0.2.2` line in the script I think
23 2017-09-19 08:23:38	0|meshcollider|I wonder, is it because https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md#setting-up-debian-for-gitian-building uses br0 but the script tries to use lxcbr0 which doesn't exist?
24 2017-09-19 08:24:40	0|kallewoof|meshcollider: ohh. cool, thanks, will check
25 2017-09-19 08:27:23	0|meshcollider|achow101: Any advice on https://github.com/bitcoin/bitcoin/blob/master/contrib/gitian-build.sh#L178-L184 ? Could they simply be removed?
26 2017-09-19 08:28:09	0|meshcollider|because the gitian-building instructions include `echo 'export USE_LXC=1' >> /home/debian/.profile` anyway
27 2017-09-19 08:38:21	0|bitcoin-git|[13bitcoin] 15esotericnonsense opened pull request #11367: RPC: getblockchaininfo: Add disk_size, prune_target_size (06master...062017-09-getblockchaininfo-addsize) 02https://github.com/bitcoin/bitcoin/pull/11367
28 2017-09-19 08:56:33	0|kallewoof|I tried switching to br0 in gitian-build.sh. The system kind of dies (VirtualBox window still responds, but ssh stops working and eventually times out.. and `top` shows no process using CPU)..
29 2017-09-19 08:58:45	0|meshcollider|yeah that's why I wrote my own script in the end, but I wonder if its possible to just delete those lines 178-184 completely from gitian-build.sh
30 2017-09-19 09:19:22	0|Duvdevan|hi Everyone
31 2017-09-19 09:19:29	0|Duvdevan|I'm fairly new into bitcoin
32 2017-09-19 09:19:35	0|Duvdevan|I have only one question
33 2017-09-19 09:19:53	0|Duvdevan|can I use this code to modify it and run my own cryptocurrency?
34 2017-09-19 09:19:53	0|Duvdevan|https://github.com/bitcoin/bitcoin
35 2017-09-19 09:19:53	0|mryandao|Duvdevan: #bitcoin probably better.
36 2017-09-19 09:20:23	0|Duvdevan|mryandao: I thinkt he question is suitable for this channy
37 2017-09-19 09:21:00	0|meshcollider|Duvdevan: this channel is only for discussion of bitcoin core development, to discuss altcoin development please use ##altcoin-dev
38 2017-09-19 09:21:03	0|Duvdevan|and I'm banned from #bitcoin for unknown reasons... :/
39 2017-09-19 09:21:15	0|Duvdevan|thank you for referring me to the right place!
40 2017-09-19 12:49:25	0|wumpus|0.15.0.1 executables up https://bitcoin.org/bin/bitcoin-core-0.15.0.1/ https://bitcoincore.org/bin/bitcoin-core-0.15.0.1/
41 2017-09-19 13:00:17	0|bitcoin-git|[13bitcoin] 15practicalswift opened pull request #11369: doc: Document locks - increase LOCK(...) comment coverage from 2 % to 77 % (06master...06lock-comments) 02https://github.com/bitcoin/bitcoin/pull/11369
42 2017-09-19 13:04:16	0|bitcoin-git|13bitcoin/06master 141ab1b68 15Wladimir J. van der Laan: doc: Add release notes for 0.15.0.1...
43 2017-09-19 13:04:16	0|bitcoin-git|[13bitcoin] 15laanwj pushed 1 new commit to 06master: 02https://github.com/bitcoin/bitcoin/commit/1ab1b687cb5870258add2b08169cd974f08ed032
44 2017-09-19 13:32:30	0|achow101|meshcollider: kallewoof use kvm
45 2017-09-19 13:33:06	0|achow101|meshcollider: lines 182 and 183 can probably be removed
46 2017-09-19 14:39:06	0|bitcoin-git|[13bitcoin] 15practicalswift closed pull request #11361: Remove redundant LOCK(…) and AssertLockHeld(…) (06master...06remove-redundant-locks) 02https://github.com/bitcoin/bitcoin/pull/11361
47 2017-09-19 15:46:44	0|bitcoin-git|13bitcoin/06master 14fadf31e 15MarcoFalke: wallet: Display non-HD error on first run
48 2017-09-19 15:46:44	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/1ab1b687cb58...4f7e37e26c5d
49 2017-09-19 15:46:45	0|bitcoin-git|13bitcoin/06master 144f7e37e 15Wladimir J. van der Laan: Merge #11307: wallet: Display non-HD error on first run...
50 2017-09-19 15:47:24	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #11307: wallet: Display non-HD error on first run (06master...06Mf1709-walletHDfirst) 02https://github.com/bitcoin/bitcoin/pull/11307
51 2017-09-19 15:49:33	0|esotericnonsense|hm
52 2017-09-19 15:49:53	0|esotericnonsense|0.15.0.1 extracts into bitcoin-0.15.0; is this expected? (not sure how minor-minor releases have gone before)
53 2017-09-19 15:50:15	0|esotericnonsense|nuked my folder, not that it really matters
54 2017-09-19 15:51:05	0|wumpus|that's how the gitian build makes them, yes
55 2017-09-19 15:51:47	0|wumpus|don't have a strong opinion on how it should be
56 2017-09-19 15:52:35	0|wumpus|though if the .1 would be added it'd need some logic like 'drop the final .0 if the build is 0', otherwise it'd get kind of ugly
57 2017-09-19 15:52:39	0|esotericnonsense|yeah
58 2017-09-19 15:53:23	0|wumpus|I hope we can just avoid doing build-releases for a few versions now :)
59 2017-09-19 15:53:35	0|wumpus|these are really exceptional
60 2017-09-19 15:59:54	0|Lightsword|is using addwitnessaddress the best way to use segwit for production right now with core?
61 2017-09-19 16:39:49	0|luke-jr|wumpus: another possibility would be to transform `git describe` - then builds of non-tagged commits would have a better name too
62 2017-09-19 17:26:23	0|gmaxwell|https://twitter.com/BcoreProject/status/910115487182450694  this imposter account keeps going :(
63 2017-09-19 17:33:45	0|instagibbs|should apply for a blue checkmark, I think that would expedite future flagging
64 2017-09-19 17:33:54	0|instagibbs|right now it's kind of a "he said she said"
65 2017-09-19 17:35:15	0|instagibbs|taking down by twitter fee bot for now, because their support is such crap :/
66 2017-09-19 17:38:02	0|alephzero|doesnt twitter have an impersonation policy?
67 2017-09-19 17:38:22	0|kinlo|they use blue checkmarks so you know who's real and who is not
68 2017-09-19 17:38:27	0|alephzero|thats not true
69 2017-09-19 17:38:37	0|alephzero|you can take down an impersonator as well
70 2017-09-19 17:39:00	0|kinlo|you can try, which someone should
71 2017-09-19 17:39:13	0|alephzero|https://support.twitter.com/articles/18366
72 2017-09-19 17:39:28	0|alephzero|it is a ToS violation. if successful, they will get suspended.
73 2017-09-19 17:39:38	0|alephzero|then after a period of time, you can take posession of that handle.
74 2017-09-19 17:40:03	0|alephzero|somebody who has verifiable ties to bitcoin core project should file a claim.
75 2017-09-19 17:40:39	0|kinlo|indeed
76 2017-09-19 17:42:06	0|instagibbs|right now, someone can file saying "Actually I'm Core, take this down" and they're asking for things like business cards
77 2017-09-19 17:42:11	0|kinlo|gmaxwell: maybe that should be you?  you're part of the bitcoin core team now, right?
78 2017-09-19 17:42:37	0|alephzero|instagibbs: somebody who runs bitcoincore domain and github should do the reporting
79 2017-09-19 17:42:43	0|instagibbs|alephzero, agreed
80 2017-09-19 17:42:48	0|alephzero|everyone else can click the report button. i have.
81 2017-09-19 17:42:50	0|alephzero|do your part.
82 2017-09-19 17:46:33	0|gmaxwell|Twitter apparently told us to go away when we reported before or something. :(
83 2017-09-19 17:47:00	0|alephzero|I have successfully taken over impersonating accounts previously. but that was for a registered legal entity.
84 2017-09-19 17:47:50	0|alephzero|can their subreddit be taken down for impersonation?
85 2017-09-19 17:47:56	0|alephzero|that is against reddit's ToS as well.
86 2017-09-19 18:52:14	0|grubles|you can report accounts for impersonation
87 2017-09-19 18:52:18	0|grubles|(on twitter)
88 2017-09-19 18:52:41	0|grubles|as in, if you aren't the account being impersonated
89 2017-09-19 20:43:56	0|midnightmagic|Impersonation reporting for Twitter accounts that are impersonating you or your organization--including even if it is someone you are friend with, or a fan of, btw: https://support.twitter.com/forms/impersonation
90 2017-09-19 20:44:08	0|midnightmagic|I would continue reporting them.
91 2017-09-19 22:39:53	0|alephzero|you will have to supply proof you are being impersonated.
92 2017-09-19 22:40:26	0|alephzero|i.e legal entity/pseudonym registration, plus some paperwork to prove ownership
93 2017-09-19 22:42:50	0|alephzero|the best way would be to have whoever owns bitcoincore.org or a similar domain provide proof of that domains ownership, i think it will count as a registered pseudonym
94 2017-09-19 22:43:28	0|alephzero|looks like it would have to be Wlad.
95 2017-09-19 23:50:24	0|bitcoin-git|[13bitcoin] 15promag opened pull request #11370: [test] Add getblockchaininfo functional test (06master...062017-09-add-getblockchaininfo-functional-test) 02https://github.com/bitcoin/bitcoin/pull/11370