1 2017-04-22 00:40:42	0|sipa|gmaxwell: i'm sure that no matter how it is formulated, some people will misread it
 2 2017-04-22 01:11:20	0|bitcoin-git|[13bitcoin] 15jimmysong opened pull request #10256: [test] Add gettxout call to wallet.py (06master...06test_gettxout) 02https://github.com/bitcoin/bitcoin/pull/10256
 3 2017-04-22 01:26:32	0|achow101|control of the account, so how should I go about doing that?
 4 2017-04-22 01:26:32	0|achow101|I made dummy github user non-github-bitcoin (https://github.com/non-github-bitcoin) to account for the commits made by the people who committed but don't have github accounts. right now it has sirius-m (github removed it from saracen to allow me to add that account) and lasloh. I'll be asking github to also let me add s_nakamoto which is currently under invalid-email-address. I think it would be prudent to give the repo maintainers
 5 2017-04-22 01:32:35	0|gmaxwell|achow101: sounds great.
 6 2017-04-22 01:33:17	0|gmaxwell|achow101: maybe the best way would be to get wumpus to forward you his prior communication with github on it?
 7 2017-04-22 01:38:43	0|achow101|gmaxwell: I think github will let me assign satoshi's email to that account as they allowed me to do that for sirius's.
 8 2017-04-22 01:39:16	0|achow101|the question now is how I should securely hand over the account to wumpus and other maintainers.
 9 2017-04-22 01:39:37	0|gmaxwell|achow101: ask wumpus if he's willing to take it (he will be) then send him the password in gpg email.
10 2017-04-22 01:40:32	0|achow101|yeah, I figured that's how it would work. just waiting for a response to my pm
11 2017-04-22 01:41:20	0|gmaxwell|Sat Apr 22 01:41:19 UTC 2017
12 2017-04-22 01:41:33	0|gmaxwell|expect one in 6 hours or so.
13 2017-04-22 02:08:22	0|bitcoin-git|[13bitcoin] 15jimmysong opened pull request #10257: [test] Add test for getmemoryinfo (06master...06test_getmemoryinfo) 02https://github.com/bitcoin/bitcoin/pull/10257
14 2017-04-22 03:23:37	0|midnightmagic|sigh.  Or maybe Github could just fix the bug instead of making us work around their crappy design.
15 2017-04-22 05:24:11	0|wumpus|midnightmagic: yes - what happened to 'confirm your email' kind of setup
16 2017-04-22 05:24:26	0|wumpus|achow101: sure, thanks for doing that
17 2017-04-22 05:24:46	0|gmaxwell|well you can't confirm those emails, they contain no dot.
18 2017-04-22 05:25:06	0|wumpus|gmaxwell: that's my point, if you used an invalid mail you probably shouldn't be able to claim credit for it
19 2017-04-22 05:25:50	0|wumpus|e.g. being able to add arbitrary mail addresses to your account so they show up as you is a broken system
20 2017-04-22 05:30:47	0|gmaxwell|I'm sure the issue is that anything imported from SVN is like that... so you've got lots of repos where people complain they can't get credit...
21 2017-04-22 05:31:05	0|wumpus|the burden on proof should be on them
22 2017-04-22 05:31:08	0|gmaxwell|thats why we can't trust them to retain the fix... any time it's fixed more people complain they can't take credit for their own commits.
23 2017-04-22 05:31:28	0|gmaxwell|and then the 'fix' that, because github isn't about security or integrity in any form, it's a freeking web repository. :P
24 2017-04-22 05:32:17	0|gmaxwell|(I agree with you it's dumb, but we're expecting too much from github... or another way of looking at it: we're getting pretty much exactly what we pay for. :) )
25 2017-04-22 05:32:56	0|wumpus|there's other ways, they could also have added a form for the person doing the SVN import to fill in a name to user/real_email mapping
26 2017-04-22 05:33:09	0|wumpus|or at least the owner of the repo
27 2017-04-22 05:33:46	0|gmaxwell|yea, or at least require the parties be repo members, so you could just kick out anyone who misused it.
28 2017-04-22 05:33:56	0|gmaxwell|but that would be like.. good. worse is better, or something.
29 2017-04-22 05:33:57	0|wumpus|I have a paid github account
30 2017-04-22 05:34:07	0|gmaxwell|wumpus: still, it's not like it's expensive. :)
31 2017-04-22 05:34:39	0|gmaxwell|we probably use more in bandwidth alone than the cost of a couple paid accounts.
32 2017-04-22 05:34:44	0|wumpus|that's true. I doubt I pay fairly for the share of bandwidth and CPU load I cause to them :)
33 2017-04-22 07:29:52	0|wumpus|huh blockchain.info's pushtx doesn't accept transactions generated with bitcoind, "Not accepting transaction version 2"
34 2017-04-22 07:31:13	0|gmaxwell|derp
35 2017-04-22 07:59:20	0|wumpus|luke-jr: -knots sigs up, I think I even submitted it to the right repository (lost in a maze of gitian.sigs folders)
36 2017-04-22 10:09:01	0|SopaXorzTaker|Is there a pushtx service that would accept a non-standard TX?
37 2017-04-22 10:09:13	0|SopaXorzTaker|I really need spend a P2SH puzzle
38 2017-04-22 11:01:02	0|sipa|SopaXorzTaker: in p2sh? what's nonstandard about it?
39 2017-04-22 11:01:22	0|sipa|i can't help you with getting it confirmed, but i wonder what you're trying to do
40 2017-04-22 11:03:56	0|SopaXorzTaker|not really P2SH
41 2017-04-22 11:04:01	0|SopaXorzTaker|but spending a script
42 2017-04-22 11:04:12	0|SopaXorzTaker|and the TX is in the P2SH spend format
43 2017-04-22 11:07:10	0|sipa|i would suggest doing it as real P2SH
44 2017-04-22 11:24:15	0|bitcoin-git|[13bitcoin] 15Mikerah opened pull request #10258: Fixed typo in documentation for merkleblock.h (06master...06master) 02https://github.com/bitcoin/bitcoin/pull/10258
45 2017-04-22 11:42:06	0|SopaXorzTaker|Guys, just a quick question
46 2017-04-22 11:42:23	0|SopaXorzTaker|I started writing my own cryptocurrency from scratch to understand how stuff works
47 2017-04-22 11:43:04	0|SopaXorzTaker|Though I can't understand why the transaction inputs reference the TXID only
48 2017-04-22 11:43:23	0|SopaXorzTaker|if they referenced the block where that TX is, the nodes could be much faster
49 2017-04-22 11:43:25	0|SopaXorzTaker|or not?
50 2017-04-22 11:43:44	0|SopaXorzTaker|Also, why does PoW hash only the block header, not the entire block?
51 2017-04-22 11:44:21	0|sipa|SopaXorzTaker: altcoins are offtopic here
52 2017-04-22 11:44:37	0|SopaXorzTaker|sipa, this is not about altcoins
53 2017-04-22 11:44:45	0|sipa|11:42:23 < SopaXorzTaker> I started writing my own cryptocurrency from scratch to understand how stuff works
54 2017-04-22 11:44:52	0|SopaXorzTaker|I am asking about the motivation of some Bitcoin design choices
55 2017-04-22 11:45:17	0|sipa|ok, you can't reference the block a tx was in, because you don't necessarily know that when creating a transaction
56 2017-04-22 11:45:38	0|sipa|also, it's unneeded, we don't go look at the actual block an outputs was spent in, just in the UTXO database which is indexed... by txid
57 2017-04-22 11:46:31	0|SopaXorzTaker|hm
58 2017-04-22 11:46:42	0|sipa|if you have more questions like this in the future, please go to bitcoin.stackexchange.com... i'll gladly answer there
59 2017-04-22 11:46:53	0|wumpus|this channel is about development of the bitcoin core code base, nothing else
60 2017-04-22 11:47:26	0|SopaXorzTaker|uh
61 2017-04-22 11:47:55	0|SopaXorzTaker|sipa, a question related to the bitcoin core: is the UTXO database initialized when loading the blockchain?
62 2017-04-22 11:47:57	0|wumpus|there are tons of other channels, don't keep bothering this one
63 2017-04-22 11:48:35	0|sipa|SopaXorzTaker: bitcoin.stackexchange.com
64 2017-04-22 11:48:59	0|sipa|you're annoying everyone who tries to following the development discussions in this channel
65 2017-04-22 11:49:26	0|SopaXorzTaker|I mean, is it like forEach(block){forEach(block.transaction){utxo.remove(block.transaction.input);utxo.add(block.transaction.output);}}
66 2017-04-22 11:49:32	0|sipa|SopaXorzTaker: last warning
67 2017-04-22 11:50:00	0|SopaXorzTaker|sipa, I have to disagree. The question I asked *is* about the Bitcoin Core
68 2017-04-22 11:50:14	0|sipa|SopaXorzTaker: yes so?
69 2017-04-22 11:50:27	0|sipa|this channel is aboit development of bitcoin-core
70 2017-04-22 11:50:29	0|SopaXorzTaker|So I assumed that I can ask it here.
71 2017-04-22 11:50:38	0|sipa|not about guiding noobies
72 2017-04-22 11:50:47	0|SopaXorzTaker|Oh, so this channel is only for discussion of actual development?
73 2017-04-22 11:50:52	0|wumpus|just ask these things in #bitcoin okay - more people that can answer, or use the stack overflow
74 2017-04-22 11:50:54	0|wumpus|yes
75 2017-04-22 11:50:56	0|SopaXorzTaker|my apologies for misunderstanding that
76 2017-04-22 11:51:05	0|wumpus|channel topic: Bitcoin Core development discussion and commit log | This is the channel for developing Bitcoin Core. Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: https://botbot.me/freenode/bitcoin-core-dev, http://www.erisian.com.au/bitcoin-core-dev/
77 2017-04-22 11:51:18	0|sipa|i promise i'll personally try to answer your questions on https://bitcoin.stackexchange.com
78 2017-04-22 11:51:30	0|SopaXorzTaker|thanks sipa
79 2017-04-22 11:51:40	0|SopaXorzTaker|okay, I am asking my next questions there
80 2017-04-22 11:51:50	0|sipa|thanks
81 2017-04-22 13:41:14	0|sipa|wumpus: w00t 0.14.1
82 2017-04-22 13:43:24	0|da2ce7|:)
83 2017-04-22 13:44:28	0|wumpus|sipa: yeah!
84 2017-04-22 14:05:33	0|BashCo|getting a 403 on the torrent file? https://bitcoin.org/bin/bitcoin-core-0.14.1/bitcoin-0.14.1.torrent
85 2017-04-22 14:06:32	0|wumpus|let me see, I had to manually upload it
86 2017-04-22 14:07:01	0|wumpus|should be accessible now, thanks for reporting
87 2017-04-22 14:07:44	0|BashCo|yep, got it. thanks.
88 2017-04-22 14:12:09	0|Lauda|Github says 0.14.0 is latest release
89 2017-04-22 14:14:00	0|wumpus|gah, another thing to update
90 2017-04-22 14:19:27	0|bitcoin-git|13bitcoin/06master 14f8feaa4 15Wladimir J. van der Laan: doc: Add historical release notes for 0.14.1
91 2017-04-22 14:19:27	0|bitcoin-git|[13bitcoin] 15laanwj pushed 1 new commit to 06master: 02https://github.com/bitcoin/bitcoin/commit/f8feaa4636260b599294c7285bcf1c8b7737f74e
92 2017-04-22 14:22:35	0|bitcoin-git|13bitcoin/060.14 14f2a96e7 15Wladimir J. van der Laan: doc: clean out release notes
93 2017-04-22 14:22:35	0|bitcoin-git|[13bitcoin] 15laanwj pushed 1 new commit to 060.14: 02https://github.com/bitcoin/bitcoin/commit/f2a96e7d0289682eb87877a3528cb6a170f8b786
94 2017-04-22 15:13:23	0|jtimon_|should I reduce the scope of #8855 ?
95 2017-04-22 15:13:25	0|gribble|https://github.com/bitcoin/bitcoin/issues/8855 | Use a proper factory for creating chainparams by jtimon · Pull Request #8855 · bitcoin/bitcoin · GitHub
96 2017-04-22 19:39:10	0|bitcoin-git|[13bitcoin] 15jonasschnelli closed pull request #10254: [Qt] Remove shutdown poll timer and replace it with a signal (06master...062017/04/qt_shutdown) 02https://github.com/bitcoin/bitcoin/pull/10254