2016-04-28

< GitHub17> [bitcoin] jonasschnelli opened pull request #7967: [RPC] add feerate option to fundrawtransaction (master...2016/04/fund_fee) https://github.com/bitcoin/bitcoin/pull/7967
< wumpus> as said, just check 'bitcoin-cli help getnewaddress` and you'll see
< jonasschnelli> Yes. There is even no clear logo that Bitcoin Core uses/represents.
< jonasschnelli> Somehow that made me think that Bitcoin Core has no clear logo/visual identity. Its not define what to use when, the font, the colors. Not sure if anyone from us cares about that though.
< jonasschnelli> topic: another boring one, not sure if this is the right place: Someone contacted me that we should have a repository for Bitcoin Core logos and communication material.
< jonasschnelli> instagibbs: I was also thinking about that. But does the normal bitcoin-qt user really knows what the mempool is?
< GitHub114> [bitcoin] laanwj opened pull request #7966: http: Do a pending c++11 simplification handling work items (master...2016_04_httpserver_c++11) https://github.com/bitcoin/bitcoin/pull/7966
< wumpus> FYI my attempt at http streaming (still kind of unstable) https://github.com/bitcoin/bitcoin/pull/7759
< GitHub69> [bitcoin] laanwj closed pull request #7962: CalculateNextWorkRequired Cleanup (master...cleanpow) https://github.com/bitcoin/bitcoin/pull/7962
< GitHub81> bitcoin/master 20f9ecd Wladimir J. van der Laan: Merge #7962: CalculateNextWorkRequired Cleanup...
< GitHub81> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5725807402ec...20f9ecd343bb
< GitHub81> bitcoin/master c7aac2d 21E14: Deprecating the remaining LogPrintf dependencies that were made obsolete in PR #7459.
< GitHub86> [bitcoin] laanwj closed pull request #7926: [RPC] push back getaddednodeinfo dead value (master...getaddedpushbackmaster) https://github.com/bitcoin/bitcoin/pull/7926
< GitHub95> bitcoin/master 9c0bcb6 instagibbs: push back getaddednodeinfo dead value
< GitHub95> bitcoin/master 5725807 Wladimir J. van der Laan: Merge #7926: [RPC] push back getaddednodeinfo dead value...
< GitHub95> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/a9c8b744e887...5725807402ec
< GitHub128> [bitcoin] laanwj closed pull request #7952: Log invalid block hash to make debugging easier. (master...20160426_Log_invalid_block) https://github.com/bitcoin/bitcoin/pull/7952
< GitHub168> bitcoin/master a9c8b74 Wladimir J. van der Laan: Merge #7952: Log invalid block hash to make debugging easier....
< GitHub168> bitcoin/master 61c0170 Pavel Janík: Log invalid block hash to make debugging easier.
< GitHub168> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d9594bfe0c3e...a9c8b744e887
< GitHub41> [bitcoin] laanwj opened pull request #7964: Minor changes for c++11 consistency (master...2016_04_c++11_consistency) https://github.com/bitcoin/bitcoin/pull/7964
< GitHub167> [bitcoin] laanwj closed pull request #7514: Fix IsInitialBlockDownload for testnet (master...fixisinitialblock) https://github.com/bitcoin/bitcoin/pull/7514
< GitHub110> bitcoin/master d9594bf Wladimir J. van der Laan: Merge #7514: Fix IsInitialBlockDownload for testnet...
< GitHub110> bitcoin/master 8aa7226 jmacwhyte: Fix IsInitialBlockDownload to play nice with testnet
< GitHub110> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/574ddc63d6ff...d9594bfe0c3e
< GitHub134> [bitcoin] laanwj closed pull request #7939: qt: Make it possible to show details for multiple transactions (master...2016_04_qt_multiple_transaction_details) https://github.com/bitcoin/bitcoin/pull/7939
< GitHub185> bitcoin/master 574ddc6 Wladimir J. van der Laan: Merge #7939: qt: Make it possible to show details for multiple transactions...
< GitHub185> bitcoin/master f135e3c Wladimir J. van der Laan: qt: Add transaction hash to details window title
< GitHub185> bitcoin/master 17a6a21 Wladimir J. van der Laan: qt: Make it possible to show details for multiple transactions...
< GitHub185> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/06162f19d7dd...574ddc63d6ff
< JackH> what I want to do is to ./bitcoin-cli sendfrom but also include a fee. And I cant find any documentation on how to include both "sendfrom" and " settxfee ". The wiki doesnt explain it, and I am confused if I can type both commands on the same line?
< JackH> I know this is not the place for it, but could one of you help me out for a bitcoin-cli command I am struggling about? :)
< jonasschnelli> Call for a quick review: https://github.com/bitcoin/bitcoin/pull/7826 (<-- this will allow to GUI to display RBF conflicts)
< GitHub116> [bitcoin] laanwj closed pull request #7165: build: Enable C++11 in build, require C++11 compiler (master...2015_12_c++11) https://github.com/bitcoin/bitcoin/pull/7165
< GitHub149> bitcoin/master 2aacc72 Wladimir J. van der Laan: build: update ax_cxx_compile_stdcxx to serial 4
< GitHub149> bitcoin/master a398549 Cory Fields: depends: use c++11
< GitHub149> bitcoin/master 67969af Wladimir J. van der Laan: build: Enable C++11 build, require C++11 compiler...
< GitHub149> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/08b37c5e06bf...06162f19d7dd
< GitHub154> [bitcoin] 21E14 opened pull request #7962: CalculateNextWorkRequired Cleanup (master...cleanpow) https://github.com/bitcoin/bitcoin/pull/7962
< achow101> would it be possible, for after segwit deployment, to have a command line option to have Bitcoin Core write blocks to the disk in the pre-fork block forkmat?
< randy-waterhouse> cfields: re https://github.com/bitcoin/bitcoin/pull/7165 I dont think libsecpk251 requires c++11 ... or does it?

2016-04-27

< GitHub19> [bitcoin] sdaftuar opened pull request #7960: Only use AddInventoryKnown for transactions (master...block-inv-filter) https://github.com/bitcoin/bitcoin/pull/7960
< GitHub147> [bitcoin] kazcw opened pull request #7959: fix race that could fail to persist a ban (master...banmap_race) https://github.com/bitcoin/bitcoin/pull/7959
< GitHub25> [bitcoin] paveljanik opened pull request #7958: Remove useless argument to AlertNotify. (master...20160427_AlertNotify_remove_arg) https://github.com/bitcoin/bitcoin/pull/7958
< GitHub78> [bitcoin] paveljanik closed pull request #7810: Refactor AlertNotifyOnce out of UpdateTip (master...20160405_AlertNotifyOnce) https://github.com/bitcoin/bitcoin/pull/7810
< afk11> Chris_Stewart_5, indeed. check here to see why https://github.com/bitcoin/bitcoin/blob/master/src/script/script.h#L503
< GitHub11> [bitcoin] jonasschnelli opened pull request #7957: [RPC][Bitcoin-TX] Add support for sequence number (master...2016/04/rbf_base) https://github.com/bitcoin/bitcoin/pull/7957
< GitHub85> [bitcoin] laanwj closed pull request #7950: [0.12] travis: switch to Trusty (0.12...Mf1604-012travisTrusty) https://github.com/bitcoin/bitcoin/pull/7950
< GitHub122> bitcoin/0.12 564aaa2 Cory Fields: travis: switch to Trusty...
< GitHub122> bitcoin/0.12 18b3c3c Wladimir J. van der Laan: Merge #7950: [0.12] travis: switch to Trusty...
< GitHub122> bitcoin/0.12 9ca957b Wladimir J. van der Laan: tests: Make proxy_test work on travis servers without IPv6...
< GitHub122> [bitcoin] laanwj pushed 3 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/89ae85484c8b...18b3c3ced812
< GitHub156> [bitcoin] laanwj closed pull request #7899: optionally provide privkey to signmessage RPC (master...signmessage-using-privkey) https://github.com/bitcoin/bitcoin/pull/7899
< GitHub89> [bitcoin] laanwj closed pull request #7954: build: quiet annoying warnings without adding new ones (master...clean-warnings) https://github.com/bitcoin/bitcoin/pull/7954
< GitHub24> bitcoin/master 08b37c5 Wladimir J. van der Laan: Merge #7954: build: quiet annoying warnings without adding new ones...
< GitHub24> bitcoin/master 63b3111 Cory Fields: build: quiet annoying warnings without adding new ones...
< GitHub24> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5c7df7022bcd...08b37c5e06bf
< GitHub56> [bitcoin] laanwj opened pull request #7956: test: Add more thorough test for dbwrapper iterators (master...2016_04_dbwrapper_iterator_tess) https://github.com/bitcoin/bitcoin/pull/7956
< GitHub148> [bitcoin] MarcoFalke closed pull request #7951: [qa] test_framework: Properly print exception (master...Mf1604-qaMinorFixes) https://github.com/bitcoin/bitcoin/pull/7951
< GitHub28> bitcoin/master 5c7df70 MarcoFalke: Merge #7951: [qa] test_framework: Properly print exception...
< GitHub28> bitcoin/master fada064 MarcoFalke: [qa] test_framework: Properly print exceptions and assert empty dict
< GitHub28> bitcoin/master 5555528 MarcoFalke: [qa] mininode: Unfiddle strings into bytes
< GitHub28> [bitcoin] MarcoFalke pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/e26b62093ae2...5c7df7022bcd
< da2ce7_mobile> what is the best way to do it *now* if I don't want to compile bitcoin with that pull request merged?
< da2ce7_mobile> is there a easy way to 'reset' an unconfirmed transaction in Bitcoin-QT?
< GitHub131> [bitcoin] pstratem opened pull request #7955: [WIP] sync mempool after new block (master...2016-04-26-mempoolsync) https://github.com/bitcoin/bitcoin/pull/7955
< GitHub115> [bitcoin] theuni opened pull request #7954: build: quiet annoying warnings without adding new ones (master...clean-warnings) https://github.com/bitcoin/bitcoin/pull/7954
< GitHub193> [bitcoin] achow101 opened pull request #7953: Create signmessagewithprivkey rpc (master...signmessagewithprivkey) https://github.com/bitcoin/bitcoin/pull/7953

2016-04-26

< GitHub9> [bitcoin] paveljanik opened pull request #7952: Log invalid block hash to make debugging easier. (master...20160426_Log_invalid_block) https://github.com/bitcoin/bitcoin/pull/7952
< GitHub25> [bitcoin] MarcoFalke opened pull request #7951: [qa] test_framework: Properly print exception (master...Mf1604-qaMinorFixes) https://github.com/bitcoin/bitcoin/pull/7951
< GitHub57> [bitcoin] MarcoFalke opened pull request #7950: [0.12] travis: switch to Trusty (0.12...Mf1604-012travisTrusty) https://github.com/bitcoin/bitcoin/pull/7950
< GitHub26> [bitcoin] jonasschnelli opened pull request #7949: [RPC] Add RPC long poll notifications (master...2016/04/rpc_signals) https://github.com/bitcoin/bitcoin/pull/7949
< GitHub176> [bitcoin] mruddy opened pull request #7948: RPC: add locked_in block hash to getblockchaininfo bip9_softforks data (master...version_bits_locked_in_block) https://github.com/bitcoin/bitcoin/pull/7948
< jonasschnelli> I think this should work now as intended: https://github.com/bitcoin/bitcoin/pull/7946/files
< jonasschnelli> sipa: Yes. And we use the position for "merges" https://github.com/bitcoin/bitcoin/blob/master/src/wallet/wallet.cpp#L715
< jonasschnelli> the only problematic part would be: https://github.com/bitcoin/bitcoin/blob/master/src/wallet/wallet.cpp#L3288
< GitHub95> [bitcoin] hmel opened pull request #7947: Global params cleanup (master...global-params-cleanup) https://github.com/bitcoin/bitcoin/pull/7947
< GitHub138> [bitcoin] jonasschnelli opened pull request #7946: Reduce cs_main locks during ConnectTip/SyncWithWallets (master...2016/04/cs_main_wallet) https://github.com/bitcoin/bitcoin/pull/7946
< GitHub157> [bitcoin] MarcoFalke opened pull request #7945: Revert "travis: temporarily disable qt to avoid timeouts" (master...Mf1604-travisQtCache) https://github.com/bitcoin/bitcoin/pull/7945
< GitHub38> [bitcoin] laanwj closed pull request #7936: CDataStream::ignore Throw exception instead of assert on negative nSize. (master...2016-04-24-cdatastream-ignore) https://github.com/bitcoin/bitcoin/pull/7936
< GitHub86> [bitcoin] laanwj closed pull request #7933: Fix OOM when deserializing UTXO entries with invalid length (master...fixcompressoroom) https://github.com/bitcoin/bitcoin/pull/7933
< GitHub135> bitcoin/master 4bf631e Patrick Strateman: CDataStream::ignore Throw exception instead of assert on negative nSize....
< GitHub135> bitcoin/master 4f87af6 Pieter Wuille: Treat overly long scriptPubKeys as unspendable
< GitHub135> bitcoin/master f8e6fb1 Pieter Wuille: Introduce constant for maximum CScript length
< GitHub135> [bitcoin] laanwj pushed 6 new commits to master: https://github.com/bitcoin/bitcoin/compare/0ea394188611...e26b62093ae2
< GitHub188> [bitcoin] laanwj closed pull request #7941: Fixing comment in script_test.json test case (master...fix_script_test_comment) https://github.com/bitcoin/bitcoin/pull/7941
< GitHub0> bitcoin/master 62a9abd Chris Stewart: Fixing comment in script_test.json test case
< GitHub0> bitcoin/master 0ea3941 Wladimir J. van der Laan: Merge #7941: Fixing comment in script_test.json test case...
< GitHub0> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c3e3cfb5d1ea...0ea394188611
< GitHub8> [bitcoin] laanwj closed pull request #7920: Switch Travis to Trusty (master...travis-trusty) https://github.com/bitcoin/bitcoin/pull/7920
< GitHub111> bitcoin/master 9267a47 Cory Fields: depends: enable pre-compiled headers for qt...
< GitHub111> bitcoin/master 06fdffd Cory Fields: travis: switch to Trusty
< GitHub111> bitcoin/master a6666b2 Wladimir J. van der Laan: depends: mac deploy Py3 compatibility...
< GitHub111> [bitcoin] laanwj pushed 7 new commits to master: https://github.com/bitcoin/bitcoin/compare/a4078071e0b4...c3e3cfb5d1ea
< GitHub26> [bitcoin] laanwj closed pull request #7944: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035. (master...master) https://github.com/bitcoin/bitcoin/pull/7944
< GitHub154> bitcoin/master a407807 Wladimir J. van der Laan: Merge #7944: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035....
< GitHub154> bitcoin/master 89c844d randy-waterhouse: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035.
< GitHub154> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/46880ed2fd96...a4078071e0b4
< MarcoFalke> Interesting, we didn't yet switch to trusty or py3, yet https://github.com/bitcoin/bitcoin/pull/7944 fails due to https://github.com/bitcoin/bitcoin/issues/7893 ...
< sipa> wumpus: interesting... the Qt GUI was what brought you into bitcoin development in the first place, no?
< sipa> i'm sure bitcoin 0.13 will ship with the ability to maintain the utxo set in RAM, in LevelDB, in LMDB, in BDB and in CSV files.
< randy-waterhouse> wumpus: cfields : https://github.com/bitcoin/bitcoin/pull/7944
< GitHub178> [bitcoin] randy-waterhouse opened pull request #7944: Re-instate TARGET_OS=linux in configure.ac. Removed by 351abf9e035. (master...master) https://github.com/bitcoin/bitcoin/pull/7944
< cfields> gmaxwell: we could make sure the bitcoin configs are covered in the downstream matrix, but yea, I suppose it's best to keep them running in case we get out of sync
< cfields> sipa: in the bitcoin repo. They're pretty redundant, I should think
< gmaxwell> kanzure: it's intentional incompetence in bitcoinj... it used to be worse, google up the bitcoin-dev logs for this lovely conversation
< GitHub160> [bitcoin] kazcw opened pull request #7942: lock cs_main for State/Misbehaving/chainActive (master...locking) https://github.com/bitcoin/bitcoin/pull/7942

2016-04-25

< Guest32930> kanzure: bitcoin core at most pings once per minute, i think
< GitHub173> [bitcoin] Christewart opened pull request #7941: Fixing comment in script_test.json test case (master...fix_script_test_comment) https://github.com/bitcoin/bitcoin/pull/7941
< GitHub117> [bitcoin] pstratem opened pull request #7940: [WIP] Fuzzing framework (master...2016-04-20-fuzzing-framework) https://github.com/bitcoin/bitcoin/pull/7940
< arubi> why are the expansions of op_cltv and op_csv done in different ways in 'script.h'? https://github.com/bitcoin/bitcoin/blob/master/src/script/script.h#L165-L168
< GitHub25> [bitcoin] laanwj opened pull request #7939: qt: Make it possible to show details for multiple transactions (master...2016_04_qt_multiple_transaction_details) https://github.com/bitcoin/bitcoin/pull/7939
< phantomcircuit> NotAnNSAgent, you've been unbanned from #bitcoin please move your discussion there
< GitHub177> [bitcoin] MarcoFalke opened pull request #7938: [0.12.2] Backports (0.12...Mf1604-012backp) https://github.com/bitcoin/bitcoin/pull/7938
< Chris_Stewart_5> I don't think that is only relevant inside of the mempool - https://github.com/bitcoin/bitcoin/blob/master/src/script/interpreter.cpp#L940
< Chris_Stewart_5> Also, how could 0 be a validly encoded public key, doesn't it trivially fail this https://github.com/bitcoin/bitcoin/blob/master/src/script/interpreter.cpp#L66
< NotAnNSAgent> Just one more note, since sipa isn't in ##bitcoin: yes, I learned what "accounts" actually are in Bitcoin, but I also learned that the labels stuff is not stable/finished either, and that I can use "accounts" as a form of label until things stabilize, but I cannot use them to segregate money in the way I first thought was possible.
< Chris_Stewart_5> Is it becuse it is not properly encoded as per https://github.com/bitcoin/bitcoin/blob/master/src/script/interpreter.cpp#L202
< GitHub133> bitcoin/0.12 6aae129 MarcoFalke: [qa] wallet: Print maintenance...
< GitHub133> bitcoin/0.12 d89fbfe MarcoFalke: [qa] rpc-test: Normalize assert()...
< GitHub133> bitcoin/0.12 ad8c743 MarcoFalke: [qa] Extend tests...
< GitHub133> [bitcoin] MarcoFalke pushed 12 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/9779e1e1f320...89ae85484c8b
< GitHub46> [bitcoin] MarcoFalke closed pull request #7811: [0.12.2] qa Backports (0.12...Mf1604-qa012) https://github.com/bitcoin/bitcoin/pull/7811
< phantomcircuit> NotAnNSAgent, you've been unbanned from #bitcoin please move your discussion there
< MarcoFalke> wumpus, I think it makes sense to merge https://github.com/bitcoin/bitcoin/pull/7811#issuecomment-212380135 now
< GitHub66> [bitcoin] laanwj closed pull request #7688: List solvability in listunspent output and improve help (master...helpspendsolv) https://github.com/bitcoin/bitcoin/pull/7688
< GitHub91> bitcoin/master 46880ed Wladimir J. van der Laan: Merge #7688: List solvability in listunspent output and improve help...
< GitHub91> bitcoin/master c3932b3 Pieter Wuille: List solvability in listunspent output and improve help
< GitHub91> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/c4e8390047a1...46880ed2fd96
< wumpus> bitcoin core is not something you should upgrade without paying attention, especially if you use it in production and there's actual money involved
< NotAnNSAgent> There is very little interest in making it possible to have any idea who owns a given address in a "Bitcoin bank" (wallet)?
< wumpus> this is the label API that will replace it: https://github.com/bitcoin/bitcoin/pull/7729 ... note that this is mostly just a subset of the account functionality, the only thing that will disappear is the account balance
< NotAnNSAgent> That is, any label I need for my own reference to know which "account" (not the deprecated Bitcoin concept of "accounts") it belongs to.
< NotAnNSAgent> wumpus: I manage to not get the bitcoin-cli binary because I only installed bitcoin-daemon because why would I want the -cli thing?
< GitHub61> [bitcoin] laanwj closed pull request #7792: depends: mac deploy Py3 compatibility (fixes macosx gitian build) (master...2016_04_fix_macosx_gitian) https://github.com/bitcoin/bitcoin/pull/7792
< da2ce7_mobile> Ok, I have just the blkXXX files, and a wallet.dat file. Will load bitcoin.
< da2ce7_mobile> I'm using Bitcoin 0.12.1
< da2ce7_mobile> hello, I wish to copy the blocks from one PC to another, what is the minimum I need to copy? It If I just copy the blk0xxx files it overwrites the files. If I include the rev00xxx files bitcoin throws an assertion. I suppose it has something to do with the chainstate obfuscation.
< wumpus> how do you manage to not get the bitcoin-cli binary?
< NotAnNSAgent> (I don't have bitcoin-cli binary)
< wumpus> NotAnNSAgent: the best documentation for the API is in bitcoind itself, using bitcoin-cli help
< instagibbs> NotAnNSAgent, bitcoin-cli help ?
< NotAnNSAgent> And has "not been reviewed by Bitcoin developers", which makes no sense to me.
< NotAnNSAgent> wumpus: I'm talking about the API to talk to bitcoind. Which seems to be explained (messily) at https://bitcoin.org/en/developer-reference#bitcoin-core-apis , but that documentation is full of dangerously outdated information.
< assder> This looks very good for those wanting to start developing: https://en.bitcoin.it/wiki/Bitcoin_Core_0.11_(ch_1):_Overview. Haven't checked it out in depth myself.
< wumpus> have you seen https://bitcoin.org/en/developer-documentation ? I think it's pretty okay
< NotAnNSAgent> This is obviously going to offend you, but I have to ask... Is the not only poor, but grossly *misleading* documentation deliberately so? I mean, maybe you don't want Bitcoin to be easy to implement to ensure job security or something? I've seriously begun asking myself if that could be the case. Again, though, I understand that this is both very difficult stuff, and you can't change things directly as individuals without first talking
< GitHub161> [bitcoin] laanwj closed pull request #7881: Update release process (master...2016_04_update_release_process) https://github.com/bitcoin/bitcoin/pull/7881
< GitHub158> bitcoin/master f154470 MarcoFalke: [contrib] Remove reference to sf and add doc to verify.sh
< GitHub158> bitcoin/master 182bec4 Wladimir J. van der Laan: contrib: remove hardcoded version from verify.sh...
< GitHub158> bitcoin/master c907f4d Wladimir J. van der Laan: doc: Update release process...
< GitHub158> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/f9c2ac72327e...c4e8390047a1
< GitHub121> bitcoin/master b69836d Wladimir J. van der Laan: dbwrapper: Pass parent CDBWrapper into CDBBatch and CDBIterator...
< GitHub160> [bitcoin] laanwj closed pull request #7927: Minor changes to dbwrapper to simplify support for other databases (master...2016_04_dbwrapper_modernization) https://github.com/bitcoin/bitcoin/pull/7927
< GitHub121> bitcoin/master 878bf48 Wladimir J. van der Laan: dbwrapper: Remove CDBWrapper::GetObfuscateKeyHex...
< GitHub121> bitcoin/master 74f7b12 Wladimir J. van der Laan: dbwrapper: Remove throw keywords in function signatures...
< GitHub121> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/f604bf63211f...f9c2ac72327e
< GitHub179> [bitcoin] laanwj closed pull request #6821: Avoid duplicate getheaders requests (master...no-duplicate-getheaders) https://github.com/bitcoin/bitcoin/pull/6821
< GitHub136> [bitcoin] pstratem opened pull request #7936: CDataStream::ignore Throw exception instead of assert on negative nSize. (master...2016-04-24-cdatastream-ignore) https://github.com/bitcoin/bitcoin/pull/7936
< GitHub66> [bitcoin] luke-jr opened pull request #7935: Versionbits: GBT support (master...gbt_bip9) https://github.com/bitcoin/bitcoin/pull/7935
< NotAnNSAgent> You make about as much sense as the Bitcoin API.
< NotAnNSAgent> It feels as if I'm desperately trying to help get some enthusiasm going for Bitcoin as a project, but everyone seems to have sort of given up mentally.
< belcher> the gui client is generally called bitcoin-qt, bitcoin core is the project that includes both of those
< NotAnNSAgent> Also, Bitcoin Core is bitcoind, no?
< luke-jr> that's how bitcoin works
< luke-jr> and Bitcoin has no concept of users
< phantomcircuit> NotAnNSAgent, you're right that should be updated, i opened an issue for it on github https://github.com/bitcoin-dot-org/bitcoin.org/issues/1287
< NotAnNSAgent> phantomcircuit: To be able to support Bitcoin donations to one of my services, and to deal with another Bitcoin account for my commercial site.
< NotAnNSAgent> Why is it so hard for Bitcoin to simply support multiple wallets? Why do I have to run entire separate blockchains and instances of the daemon for this?
< phantomcircuit> NotAnNSAgent, in bitcoin terms a "wallet" is just a collection of private keys and the transactions related to those keys in the blockchain
< NotAnNSAgent> I have to ignore the accounts stuff, because I learned it's practically removed from the Bitcoin software.
< NotAnNSAgent> Why didn't Bitcoin support multiple "wallets" right away? I have no idea what you mean that "accounts" are supposed to be, still.
< phantomcircuit> NotAnNSAgent, the "accounts" stuff is completely separate from handling of bitcoin transactions
< NotAnNSAgent> And why Bitcoin forces me to have separate instances and separate blockchains for each "account" I want to have (each "wallet" in your terms).
< NotAnNSAgent> phantomcircuit: I'm trying to discuss the concept of "accounts" in Bitcoin and why they were made the way they were.
< NotAnNSAgent> But the "wallet" idea is also an attractive thing to advertise. Though I think the "wallets" could rather be Bitcoin's own term for an "account", all inside a "Bitcoin bank" (bank.dat).
< NotAnNSAgent> So I would've liked it better if the initial metaphor wasn't "wallet" and "wallet.dat", but instead "virtual Bitcoin bank" and "bank.dat".

2016-04-24

< NotAnNSAgent> Which could only be known to somebody who is very intimately familiar with the Bitcoin development process.
< sipa> the documentation on bitcoin.org is often very good though, and better than what developers would write :)
< NotAnNSAgent> If Bitcoin.org is unofficial.
< NotAnNSAgent> Where is the actual manual for Bitcoin?
< sipa> at least, not the Bitcoin Core maintainers
< sipa> Bitcoin developers do not run that site.
< NotAnNSAgent> I mean "you" as in "Bitcoin developers".
< NotAnNSAgent> sipa: I'm referring to https://bitcoin.org/en/developer-reference#sendtoaddress
< belcher> i think i found out accounts were deprecated from the bitcoin wiki or something
< sipa> 18:12:28 < NotAnNSAgent> Since Windows 10, the Bitcoin Core client for Windows uses the awful Windows 10 notifications, which I've been forced to turn off globally.
< sipa> NotAnNSAgent: i must say that i'm somewhat surprised to see someone comment about using bitcoin on both Win10 and FreeBSD :)
< NotAnNSAgent> My experiences especially these last few weeks have really convinced me that Bitcoin has a looooong way to go before it can be implemented by anyone other than hardcore experts.
< sipa> NotAnNSAgent: for the longest time i was not paid to work on bitcoin, and i still spent weekends and evenings on it. please don't say that money is the only reason to do things
< NotAnNSAgent> Now you're just being ridiculous. Are you saying that every Bitcoin business in the world uses third-party clients because the official one only allows one single wallet?
< gmaxwell> There isn't really any "from" in the design of the bitcoin protocol in any case-- that people often think there is an artifact of the forensic analysis done by block explorers and the presentation of that analysis as 'transactions' in a way that doesn't actually reflect the operation of the bitcoin system.
< gmaxwell> sturles: the lack of good durability options for bitcoin wallets probably makes that workflow suboptimal. You probably want to have something that lets you send a transaction atomically with making a backup.
< sipa> but it's good to know that we should probably ask the bitcoin.org people to mark those RPCs as deprecated on the site
< NotAnNSAgent> But then why does this up-to-date, apparently-official manual mention accounts for the very same API call? https://bitcoin.org/en/developer-reference#sendfrom
< belcher> well they are, since before i got interested in bitcoin
< NotAnNSAgent> https://bitcoin.org/en/developer-reference#bitcoin-core-apis <-- This page doesn't seem to even display correctly.
< sipa> i suggest using the developer documentation on bitcoin.org
< NotAnNSAgent> sipa: "<amount> is a real and is rounded to 8 decimal places." <-- 0.1 seems to not mean "one tenth of a Bitcoin".
< sipa> bitcoin core's wallet is design so it only needs a backup every 100 (or whatever you set the keypool size too) transactions
< GitHub188> [bitcoin] sipa opened pull request #7934: Improve rolling bloom filter performance and benchmark (master...benchrollingbloom) https://github.com/bitcoin/bitcoin/pull/7934
< sipa> i'm not sure what kind of notifications you're talking about, as i haven't used windows or the bitcoin core GUI in a long time
< NotAnNSAgent> And it appears to be impossible to enable them only for Bitcoin Core.
< NotAnNSAgent> Since Windows 10, the Bitcoin Core client for Windows uses the awful Windows 10 notifications, which I've been forced to turn off globally.
< GitHub10> [bitcoin] sipa opened pull request #7933: Fix OOM when deserializing UTXO entries with invalid length (master...fixcompressoroom) https://github.com/bitcoin/bitcoin/pull/7933
< GitHub137> [bitcoin] pstratem closed pull request #7931: [WIP] Fuzzing framework (master...2016-04-20-fuzzing-framework) https://github.com/bitcoin/bitcoin/pull/7931
< gmaxwell> phantomcircuit: bitcoin-fuzzy should probably be in test/
< GitHub54> [bitcoin] pstratem opened pull request #7932: CAddrMan::Deserialize handle corrupt serializations better. (master...2016-04-23-addrman-deserialize-limits) https://github.com/bitcoin/bitcoin/pull/7932
< GitHub198> [bitcoin] pstratem closed pull request #7930: CAddrMan::Deserialize Initialize to NULL on insane input. (master...2014-04-23-addrman-deserialize-limits) https://github.com/bitcoin/bitcoin/pull/7930
< GitHub119> [bitcoin] pstratem opened pull request #7931: [WIP] Fuzzing framework (master...2016-04-20-fuzzing-framework) https://github.com/bitcoin/bitcoin/pull/7931
< GitHub117> [bitcoin] pstratem opened pull request #7930: CAddrMan::Deserialize Initialize to NULL on insane input. (master...2014-04-23-addrman-deserialize-limits) https://github.com/bitcoin/bitcoin/pull/7930

2016-04-23

< luke-jr> Lightsword: see https://github.com/bitcoin/bips/pull/365
< luke-jr> ok, step 1 done I hope: https://github.com/bitcoin/bips/pull/365
< belcher> wrong channel, go to #bitcoin-otc or similar
< airmac> anyone wanna trade i got 29g of bitgold with trade for bitcoin intrested msg me for trade we can use escrow if you want\
< sipa> #bitcoin-otc or similar channels please
< airmac> anyone wanna trade i got 29g of bitgold with trade for bitcoin intrested msg me for trade we can use escrow if you want
< NicolasDorier> in the bitcoin folder does not compile bitcoin2 does
< randy-waterhouse> recent commit 351abf9e035581e3320fbb72ec5b1fa452b09c2f (depends build) introduces following error http://pastebin.com/q5cP70y8 (and core dump) on bitcoin-qt
< luke-jr> NicolasDorier: ideally, copy the entire bitcoin/ dir somewhere, then re-do it successfully and compare
< GitHub187> [bitcoin] laanwj opened pull request #7927: Minor changes to dbwrapper to simplify support for other databases (master...2016_04_dbwrapper_modernization) https://github.com/bitcoin/bitcoin/pull/7927

2016-04-22

< GitHub6> [bitcoin] instagibbs opened pull request #7926: [RPC] push back getaddednodeinfo dead value (master...getaddedpushbackmaster) https://github.com/bitcoin/bitcoin/pull/7926
< GitHub82> [bitcoin] MarcoFalke closed pull request #7918: [qa] mininode: Use hexlify wrapper from util (master...Mf1604-qaMininodeHexlify) https://github.com/bitcoin/bitcoin/pull/7918
< GitHub26> [bitcoin] laanwj closed pull request #7925: qt: Fix out-of-tree GUI builds (master...2016_04_qt_out_of_tree_build) https://github.com/bitcoin/bitcoin/pull/7925
< GitHub197> bitcoin/master f604bf6 Wladimir J. van der Laan: Merge #7925: qt: Fix out-of-tree GUI builds...
< GitHub197> bitcoin/master f59dceb Wladimir J. van der Laan: qt: Fix out-of-tree GUI builds...
< GitHub197> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/351abf9e0355...f604bf63211f
< GitHub99> [bitcoin] laanwj opened pull request #7925: qt: Fix out-of-tree GUI builds (master...2016_04_qt_out_of_tree_build) https://github.com/bitcoin/bitcoin/pull/7925
< GitHub133> [bitcoin] laanwj closed pull request #7911: leveldb: integrate leveldb into our buildsystem (master...leveldb-integration) https://github.com/bitcoin/bitcoin/pull/7911
< GitHub139> bitcoin/master 351abf9 Wladimir J. van der Laan: Merge #7911: leveldb: integrate leveldb into our buildsystem...
< GitHub139> bitcoin/master a4625ac Cory Fields: leveldb: integrate leveldb into our buildsystem...
< GitHub139> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/90653bc91d39...351abf9e0355
< GitHub105> [bitcoin] laanwj closed pull request #7922: CBase58Data::SetString: cleanse the full vector (master...cleanse-fully) https://github.com/bitcoin/bitcoin/pull/7922
< GitHub186> bitcoin/master 90653bc Wladimir J. van der Laan: Merge #7922: CBase58Data::SetString: cleanse the full vector...
< GitHub186> bitcoin/master 5770449 Kaz Wesley: CBase58Data::SetString: cleanse the full vector...
< GitHub186> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/76176823ba6a...90653bc91d39
< GitHub59> bitcoin/master 7617682 Wladimir J. van der Laan: Merge #7919: Fix headers announcements edge case...
< GitHub157> [bitcoin] laanwj closed pull request #7919: Fix headers announcements edge case (master...fix-sendheaders-edge-case) https://github.com/bitcoin/bitcoin/pull/7919
< GitHub59> bitcoin/master 3a99fb2 Suhas Daftuar: Fix headers announcements edge case...
< GitHub59> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0c95ebce7e67...76176823ba6a
< GitHub90> [bitcoin] laanwj closed pull request #7816: [Wallet] slighly refactor GetOldestKeyPoolTime() (master...2016/04/wallet_oldest_key) https://github.com/bitcoin/bitcoin/pull/7816
< GitHub132> bitcoin/master 0c95ebc Wladimir J. van der Laan: Merge #7816: [Wallet] slighly refactor GetOldestKeyPoolTime()...
< GitHub132> bitcoin/master 9f7336b Jonas Schnelli: [Wallet] slightly refactor GetOldestKeyPoolTime()
< GitHub132> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/59ad56851a34...0c95ebce7e67
< GitHub172> [bitcoin] kazcw closed pull request #7923: Enable leveldb obfuscation for new databases (master...obfuscate) https://github.com/bitcoin/bitcoin/pull/7923
< GitHub185> [bitcoin] kazcw opened pull request #7923: Enable leveldb obfuscation for new databases (master...obfuscate) https://github.com/bitcoin/bitcoin/pull/7923
< GitHub71> [bitcoin] kazcw opened pull request #7922: CBase58Data::SetString: cleanse the full vector (master...cleanse-fully) https://github.com/bitcoin/bitcoin/pull/7922

2016-04-21

< luke-jr> hrm, I fixed some Travis-outside-of-"bitcoin" issues earleir this year
<@sipa> i would love to just enable travis on my own bitcoin fork repo
< airmac> anyone intrested in trading bitgold for bitcoin we can use escrow if you like
< Chris_Stewart_5> jl2012: Looks like you right, in sipa's pull request refactoring test cases he expects an OP_COUNT error https://github.com/sipa/bitcoin/blob/refactorscriptests_12/src/test/data/script_tests.json#L1097-L1101
< GitHub137> [bitcoin] MarcoFalke closed pull request #7912: Tests: Fix deserialization of reject messages (master...fix-mininode-reject) https://github.com/bitcoin/bitcoin/pull/7912
< GitHub39> bitcoin/master 59ad568 MarcoFalke: Merge #7912: Tests: Fix deserialization of reject messages...
< GitHub39> bitcoin/master 807fa47 Suhas Daftuar: Tests: Fix deserialization of reject messages...
< GitHub39> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/78d61aab233f...59ad56851a34
< GitHub188> [bitcoin] laanwj closed pull request #7921: [contrib] verify-commits: Add MarcoFalke fingerprint (master...Mf1604-contribMFfingerp) https://github.com/bitcoin/bitcoin/pull/7921
< GitHub77> bitcoin/master fa24329 MarcoFalke: [contrib] verify-commits: Add MarcoFalke fingerprint
< GitHub77> bitcoin/master 78d61aa Wladimir J. van der Laan: Merge #7921: [contrib] verify-commits: Add MarcoFalke fingerprint...
< GitHub77> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/3689ac463439...78d61aab233f
< GitHub84> [bitcoin] MarcoFalke opened pull request #7921: [contrib] verify-commits: Add MarcoFalke fingerprint (master...Mf1604-contribMFfingerp) https://github.com/bitcoin/bitcoin/pull/7921
< MarcoFalke> Ok, will add this to https://github.com/sipa/bitcoin/pull/79
< MarcoFalke> Basically https://github.com/bitcoin/bitcoin/pull/7918 would conflict with segwit (on purpose) to get rid of the wildcard import and other cleanup. Should I submit this to the segwit branch instead?
< jonasschnelli> His last commits where not listed as "verified" by github: https://github.com/bitcoin/bitcoin/pull/7918/commits
< jonasschnelli> Hmm... maybe you should add you key here first: https://github.com/bitcoin/bitcoin/blob/master/contrib/verify-commits/trusted-keys
< wumpus> MarcoFalke: I've just enabled commit access to bitcoin/bitcoin for you - to get you started, can you try to merge #7912 using the github-merge.py script? If you need any help setting it up let me know
< GitHub1> [bitcoin] laanwj closed pull request #7916: Explicitly pass CChainParams& to DisconnectTip() (master...global-params-cleanup) https://github.com/bitcoin/bitcoin/pull/7916
< GitHub119> bitcoin/master d0a6353 face: Pass CChainParams to DisconnectTip()
< GitHub119> bitcoin/master 176869f face: Explicitly pass CChainParams to ConnectBlock
< GitHub119> bitcoin/master 764d237 Jorge Timón: Globals: Explicitly pass const CChainParams& to UpdateTip()
< GitHub119> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/bafd075c5e6a...3689ac463439
< GitHub5> [bitcoin] sipa closed pull request #7913: Fix for incorrect locking in GetPubKey() (keystore.cpp) (master...getpubkey-locking-fix) https://github.com/bitcoin/bitcoin/pull/7913
< GitHub164> bitcoin/master bafd075 Pieter Wuille: Merge #7913: Fix for incorrect locking in GetPubKey() (keystore.cpp)...
< GitHub164> bitcoin/master 220f950 Yuri Zhykin: Fix for incorrect locking in GetPubKey() (keystore.cpp)
< GitHub164> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7daa3adb242d...bafd075c5e6a
< GitHub128> [bitcoin] sipa closed pull request #7868: net: Split DNS resolving functionality out of net structures (master...net-cleanup-resolve) https://github.com/bitcoin/bitcoin/pull/7868