< sipa> gmaxwell: i'm sure that no matter how it is formulated, some people will misread it
< bitcoin-git> [bitcoin] jimmysong opened pull request #10256: [test] Add gettxout call to wallet.py (master...test_gettxout) https://github.com/bitcoin/bitcoin/pull/10256
< 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
< achow101> control of the account, so how should I go about doing that?
< gmaxwell> achow101: sounds great.
< gmaxwell> achow101: maybe the best way would be to get wumpus to forward you his prior communication with github on it?
< 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.
< achow101> the question now is how I should securely hand over the account to wumpus and other maintainers.
< gmaxwell> achow101: ask wumpus if he's willing to take it (he will be) then send him the password in gpg email.
< achow101> yeah, I figured that's how it would work. just waiting for a response to my pm
< gmaxwell> Sat Apr 22 01:41:19 UTC 2017
< gmaxwell> expect one in 6 hours or so.
< bitcoin-git> [bitcoin] jimmysong opened pull request #10257: [test] Add test for getmemoryinfo (master...test_getmemoryinfo) https://github.com/bitcoin/bitcoin/pull/10257
< midnightmagic> sigh. Or maybe Github could just fix the bug instead of making us work around their crappy design.
<@wumpus> midnightmagic: yes - what happened to 'confirm your email' kind of setup
<@wumpus> achow101: sure, thanks for doing that
< gmaxwell> well you can't confirm those emails, they contain no dot.
<@wumpus> gmaxwell: that's my point, if you used an invalid mail you probably shouldn't be able to claim credit for it
<@wumpus> e.g. being able to add arbitrary mail addresses to your account so they show up as you is a broken system
< 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...
<@wumpus> the burden on proof should be on them
< 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.
< gmaxwell> and then the 'fix' that, because github isn't about security or integrity in any form, it's a freeking web repository. :P
< 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. :) )
<@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
<@wumpus> or at least the owner of the repo
< gmaxwell> yea, or at least require the parties be repo members, so you could just kick out anyone who misused it.
< gmaxwell> but that would be like.. good. worse is better, or something.
<@wumpus> I have a paid github account
< gmaxwell> wumpus: still, it's not like it's expensive. :)
< gmaxwell> we probably use more in bandwidth alone than the cost of a couple paid accounts.
<@wumpus> that's true. I doubt I pay fairly for the share of bandwidth and CPU load I cause to them :)
<@wumpus> huh blockchain.info's pushtx doesn't accept transactions generated with bitcoind, "Not accepting transaction version 2"
< gmaxwell> derp
<@wumpus> luke-jr: -knots sigs up, I think I even submitted it to the right repository (lost in a maze of gitian.sigs folders)
< SopaXorzTaker> Is there a pushtx service that would accept a non-standard TX?
< SopaXorzTaker> I really need spend a P2SH puzzle
< sipa> SopaXorzTaker: in p2sh? what's nonstandard about it?
< sipa> i can't help you with getting it confirmed, but i wonder what you're trying to do
< SopaXorzTaker> not really P2SH
< SopaXorzTaker> but spending a script
< SopaXorzTaker> and the TX is in the P2SH spend format
< sipa> i would suggest doing it as real P2SH
< bitcoin-git> [bitcoin] Mikerah opened pull request #10258: Fixed typo in documentation for merkleblock.h (master...master) https://github.com/bitcoin/bitcoin/pull/10258
< SopaXorzTaker> Guys, just a quick question
< SopaXorzTaker> I started writing my own cryptocurrency from scratch to understand how stuff works
< SopaXorzTaker> Though I can't understand why the transaction inputs reference the TXID only
< SopaXorzTaker> if they referenced the block where that TX is, the nodes could be much faster
< SopaXorzTaker> or not?
< SopaXorzTaker> Also, why does PoW hash only the block header, not the entire block?
< sipa> SopaXorzTaker: altcoins are offtopic here
< SopaXorzTaker> sipa, this is not about altcoins
< sipa> 11:42:23 < SopaXorzTaker> I started writing my own cryptocurrency from scratch to understand how stuff works
< SopaXorzTaker> I am asking about the motivation of some Bitcoin design choices
< sipa> ok, you can't reference the block a tx was in, because you don't necessarily know that when creating a transaction
< 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
< SopaXorzTaker> hm
< sipa> if you have more questions like this in the future, please go to bitcoin.stackexchange.com... i'll gladly answer there
<@wumpus> this channel is about development of the bitcoin core code base, nothing else
< SopaXorzTaker> uh
< SopaXorzTaker> sipa, a question related to the bitcoin core: is the UTXO database initialized when loading the blockchain?
<@wumpus> there are tons of other channels, don't keep bothering this one
< sipa> SopaXorzTaker: bitcoin.stackexchange.com
< sipa> you're annoying everyone who tries to following the development discussions in this channel
< SopaXorzTaker> I mean, is it like forEach(block){forEach(block.transaction){utxo.remove(block.transaction.input);utxo.add(block.transaction.output);}}
< sipa> SopaXorzTaker: last warning
< SopaXorzTaker> sipa, I have to disagree. The question I asked *is* about the Bitcoin Core
< sipa> SopaXorzTaker: yes so?
< sipa> this channel is aboit development of bitcoin-core
< SopaXorzTaker> So I assumed that I can ask it here.
< sipa> not about guiding noobies
< SopaXorzTaker> Oh, so this channel is only for discussion of actual development?
<@wumpus> just ask these things in #bitcoin okay - more people that can answer, or use the stack overflow
<@wumpus> yes
< SopaXorzTaker> my apologies for misunderstanding that
<@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/
< sipa> i promise i'll personally try to answer your questions on https://bitcoin.stackexchange.com
< SopaXorzTaker> thanks sipa
< SopaXorzTaker> okay, I am asking my next questions there
< sipa> thanks
< sipa> wumpus: w00t 0.14.1
< da2ce7> :)
<@wumpus> sipa: yeah!
< BashCo> getting a 403 on the torrent file? https://bitcoin.org/bin/bitcoin-core-0.14.1/bitcoin-0.14.1.torrent
<@wumpus> let me see, I had to manually upload it
<@wumpus> should be accessible now, thanks for reporting
< BashCo> yep, got it. thanks.
< Lauda> Github says 0.14.0 is latest release
<@wumpus> gah, another thing to update
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/f8feaa4636260b599294c7285bcf1c8b7737f74e
< bitcoin-git> bitcoin/master f8feaa4 Wladimir J. van der Laan: doc: Add historical release notes for 0.14.1
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.14: https://github.com/bitcoin/bitcoin/commit/f2a96e7d0289682eb87877a3528cb6a170f8b786
< bitcoin-git> bitcoin/0.14 f2a96e7 Wladimir J. van der Laan: doc: clean out release notes
< jtimon_> should I reduce the scope of #8855 ?
< gribble> https://github.com/bitcoin/bitcoin/issues/8855 | Use a proper factory for creating chainparams by jtimon · Pull Request #8855 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] jonasschnelli closed pull request #10254: [Qt] Remove shutdown poll timer and replace it with a signal (master...2017/04/qt_shutdown) https://github.com/bitcoin/bitcoin/pull/10254