2017-12-05

< BlueMatt> -rw------- 1 matt matt 6.5T Dec 4 19:45 /home/matt/.bitcoin/debug.log
< bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11824: Block ActivateBestChain to empty validationinterface queue (master...2017-12-11822-debug) https://github.com/bitcoin/bitcoin/pull/11824

2017-12-04

< bitcoin-git> [bitcoin] practicalswift closed pull request #11799: wallet: Add compile-time checking of (non-)locking assumptions for BlockUntilSyncedToCurrentChain() [wip] (master...BlockUntilSyncedToCurrentChain-compile-time-warnings) https://github.com/bitcoin/bitcoin/pull/11799
< gribble> https://github.com/bitcoin/bitcoin/issues/11823 | Shouldnt this be nOut? · Issue #11823 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11799 | wallet: Add compile-time checking of (non-)locking assumptions for BlockUntilSyncedToCurrentChain() [wip] by practicalswift · Pull Request #11799 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/9919 | UNIX sockets support for RPC by laanwj · Pull Request #9919 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/9979 | p2p: Bare minimum to support UNIX sockets by laanwj · Pull Request #9979 · bitcoin/bitcoin · GitHub
< GAit> bitcoin core rpc. Using a socket file rather than a port
< BlueMatt> achow101: can you try https://github.com/TheBlueMatt/bitcoin/tree/2017-12-11822-debug and see what debug log looks like?
< gribble> https://github.com/bitcoin/bitcoin/issues/11822 | Severe memory leak on current master · Issue #11822 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10773 | Shell script cleanups by practicalswift · Pull Request #10773 · bitcoin/bitcoin · GitHub
< BlueMatt> sipa: #11403 looks to have failed travis to to a bad iterator deref ( https://travis-ci.org/bitcoin/bitcoin/jobs/309801879#L2838 )
< gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub
< notabot_> RK_: bitcoin.org is the best place to start.
< notabot_> mmhhtt: try #bitcoin channel or reddit
< mmhhtt> #bitcoin-core-dev
< RK_> I want to know about bitcoin
< mmhhtt> Hello, Is there anyone knows to how can build a exchange market for other country? Is there any request from bitcoin company to me for making exc market?
< gribble> https://github.com/bitcoin/bitcoin/issues/11822 | Severe memory leak on current master · Issue #11822 · bitcoin/bitcoin · GitHub
< achow101> Varunram: bitcoin.conf, not gui
< gribble> https://github.com/bitcoin/bitcoin/issues/11788 | Bitcoin-Qt (Settings) reports incorrect "Size of database cache" · Issue #11788 · bitcoin/bitcoin · GitHub
< Randolf> These servers don't have any GUI stuff installed. So I won't be able to try bitcoin-qt on them. But I could at least try bitcoin-qt on Windows 10 to confirm whether the same problem occurs cross-platform.
< achow101> also, i'm running bitcoin-qt right now, not bitcoind
< xRavenheart> Is anyone able to first provide me with a clear architecture diagram of bitcoin?
< xRavenheart> E.g. For instance Bitcoin Core has optimizations 1,2 and Electrum has optimizations 3,4
< sipa> xRavenheart: you're welcome here to ask questions about bitcoin's design and operation
< Randolf> Dizzle: Ah, yes. I suggested that asking here may be appropriate since it might involve core development. I also suggested that they ask in the #bitcoin and ##altcoins channel.
< Dizzle> Randolf: he's here, rejoined. I think luke-jr was just suggesting he ask elsewhere, e.g. #bitcoin
< sipa> 02:47:32 < Randolf> xRavenheart: What's your school project about? Bitcoin development?
< Randolf> xRavenheart: What's your school project about? Bitcoin development?

2017-12-03

< gribble> https://github.com/bitcoin/bitcoin/issues/11799 | wallet: Add compile-time checking of (non-)locking assumptions for BlockUntilSyncedToCurrentChain() [wip] by practicalswift · Pull Request #11799 · bitcoin/bitcoin · GitHub

2017-12-02

< gribble> https://github.com/bitcoin/bitcoin/issues/11045 | Offering my Bitcoin fuzzers · Issue #11045 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] jnewbery opened pull request #11817: [tests] Change bip68-112-113-p2p to use BitcoinTestFramework (master...refactor_bip68-112-113-p2p) https://github.com/bitcoin/bitcoin/pull/11817
< webuser323> Just wondering if this is relevant bitcoin-core: https://github.com/google/oss-fuzz/
< jimpo> luke-jr: That makes sense conceptually, but I don't understand make tools well enough to understand why. From what is looks like here, https://github.com/bitcoin/bitcoin/blob/master/src/Makefile.test.include#L105, the test is linked against the LIBBITCOIN_SERVER sources, which includes init.cpp.
< luke-jr> jimpo: likely they're never linked together.. test_bitcoin_main would be linked into test_bitcoin, and init.cpp into bitcoind/bitcoin-qt

2017-12-01

< Provoostenator> (feel free to answer in #bitcoin instead)
< Provoostenator> Varunram: I suppose I can try it for a day. Which begs the question how: https://bitcoin.stackexchange.com/questions/51169/how-can-i-solo-mine-using-bitcoin-core
< gribble> https://github.com/bitcoin/bitcoin/issues/8994 | Testchains: Introduce custom chain whose constructor... by jtimon · Pull Request #8994 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/8994 | Testchains: Introduce custom chain whose constructor... by jtimon · Pull Request #8994 · bitcoin/bitcoin · GitHub
< Provoostenator> Tangentally related to testing the segwit branch. It looks like miners are no longer mining SegWit transactions on testnet. See my example in #bitcoin.
< bitcoin-git> bitcoin/master 00d25e9 Wladimir J. van der Laan: Merge #11804: [docs] Fixed outdated link with archive.is...
< bitcoin-git> bitcoin/master bf20a7d Tim Shimmin: [docs] Fixed outdated link with archive.is...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0d7e0a3289ba...00d25e90db06
< bitcoin-git> bitcoin/master 0d7e0a3 Wladimir J. van der Laan: Merge #11337: Fix code constness in CBlockIndex::GetAncestor() overloads...
< bitcoin-git> bitcoin/master b4058ed Dan Raviv: Fix code constness in CBlockIndex::GetAncestor() overloads...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/13e31dd6548d...0d7e0a3289ba
< wumpus> don't think Vision is still here but: https://github.com/bitcoin/bitcoin/pull/11809 should fix his issue
< gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub

2017-11-30

< meshcollider> why would this validator return true for an empty string: https://github.com/bitcoin/bitcoin/blob/master/src/qt/optionsdialog.cpp#L337
< wumpus> the code here https://github.com/bitcoin/bitcoin/blob/master/src/qt/optionsmodel.cpp#L231 for ProxyIP and ProxyPORT needs to catch the condition where the list is empty, or not long enough
< wumpus> run bitcoin-qt with -resetguisettings
< wumpus> (of bitcoin core)
< meshcollider> Vision: in that case, the options will be in the registry, under HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt iirc
< Vision> where are the proxy settings stored for bitcoin-qt? I cleared the proxy settings in the Options dialog, and now entering the settings dialog causes a crash. definitely a bug.
< bitcoin-git> bitcoin/master fbce66a MarcoFalke: Merge #10493: Use range-based for loops (C++11) when looping over map elements...
< bitcoin-git> bitcoin/master 680bc2c practicalswift: Use range-based for loops (C++11) when looping over map elements...
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/9e38d357447e...fbce66a98267
< gmaxwell> and in the short term apply some mitigations in bitcoin, like increasing the FD count (ugh but I really don't like counting on FD magnitude sniffing)
< bitcoin-git> [bitcoin] luke-jr opened pull request #11803: Bugfix: RPC/Wallet: Include HD key metadata in dumpwallet (master...bugfix_dumpwallet_hdkeypath) https://github.com/bitcoin/bitcoin/pull/11803
< gribble> https://github.com/bitcoin/bitcoin/issues/11785 | Prevent file-descriptor exhaustion from RPC layer by vii · Pull Request #11785 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11227 | WIP: switch to libevent for node socket handling by theuni · Pull Request #11227 · bitcoin/bitcoin · GitHub
< Dizzle> cfields: this abstraction on libevent or bitcoin core?
< gmaxwell> I believe bluematt wrote a very small patch to change bitcoin to poll. We could take, that and wrap it in ifdefs so we still select on windows, and call that sub-issue done.
< wumpus> Dizzle: I don't think it's awfully useful in bitcoin-cli anyhow though it's useful for testing (though OTOH, the patch also changed the RPC testing framework to be able to use UNIX sockets)
< Dizzle> BTW, if anyone's curious how Electrum implements message signatures on native segwit addrs, we just iterate through the possible address types until there's match: https://github.com/spesmilo/electrum/blob/66cce115ef93c913d65ef5c7d781c8065f79bbaf/lib/bitcoin.py#L632
< wumpus> Dizzle: do you need it to be in bitcoin-cli for that?
< gribble> https://github.com/bitcoin/bitcoin/issues/10279 | Add a CChainState class to validation.cpp to take another step towards clarifying internal interfaces by TheBlueMatt · Pull Request #10279 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11785 | Prevent file-descriptor exhaustion from RPC layer by vii · Pull Request #11785 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10279 | Add a CChainState class to validation.cpp to take another step towards clarifying internal interfaces by TheBlueMatt · Pull Request #10279 · bitcoin/bitcoin · GitHub
< aj> do people think the +1, +0, -1, concept nak/ack thing from https://github.com/bitcoin/bitcoin/pull/11426#issuecomment-334091207 is good btw?
< gmaxwell> Provoostenator: that can be resolved with a better perspective; bitcoin development is a distributed process, your effort is your contribution not the fact that it was merged, etc.
< gribble> https://github.com/bitcoin/bitcoin/issues/8994 | Testchains: Introduce custom chain whose constructor... by jtimon · Pull Request #8994 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11699 | [travis-ci] Only run linters on Pull Requests by jnewbery · Pull Request #11699 · bitcoin/bitcoin · GitHub
< jonasschnelli> Two topic proposals: 1) review "nits" reduction, 2) bitcoin core code signing assoc.
< gribble> https://github.com/bitcoin/bitcoin/issues/11415 | [RPC] Disallow using addresses in createmultisig by achow101 · Pull Request #11415 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10579 | [RPC] Split signrawtransaction into wallet and non-wallet RPC command by achow101 · Pull Request #10579 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10583 | [RPC] Split part of validateaddress into getaddressinfo by achow101 · Pull Request #10583 · bitcoin/bitcoin · GitHub
< gmaxwell> same reason sighash flags can fail valid in bitcoin: If I pick an out of range sighash flag I could forge signatures for your pubkeys.
< gmaxwell> prior to having the explicit versions we couldn't do that, which is why we never even merged the patch in elements, much less brought it to bitcoin.
< wumpus> using bitcoin keys for anything else than signing transactions continues to make me uneasy
< sipa> the original bitcoin core message signing doesn't have a bip either
< karelb> sipa: ad sign message - in trezor we changed v constant - https://github.com/bitcoin/bitcoin/issues/10542#issuecomment-316032523 - no BIP, no time :(
< gribble> https://github.com/bitcoin/bitcoin/issues/10757 | RPC: Introduce getblockstats to plot things by jtimon · Pull Request #10757 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/8994 | Testchains: Introduce custom chain whose constructor... by jtimon · Pull Request #8994 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10279 | Add a CChainState class to validation.cpp to take another step towards clarifying internal interfaces by TheBlueMatt · Pull Request #10279 · bitcoin/bitcoin · GitHub
< wumpus> 8 PRs have been tagged for https://github.com/bitcoin/bitcoin/projects/8
< wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag
< saint_> any idea why can't bitcoin core download the blockchain on a remote NAS drive ?
< wumpus> saint_: ask in #bitcoin please, will answer there
< gribble> https://github.com/bitcoin/bitcoin/issues/11796 | [tests] Functional test naming convention by ajtowns · Pull Request #11796 · bitcoin/bitcoin · GitHub
< andytoshi> #bitcoin please, this is just about software development
< wordsToLiveBy> I'm reading the bitcoin white paper, and in section 11 Satoshi gives the calculations for how you can prove with probability that an attacker can't outpace the combined processing power of the rest of the nodes, but I am not quite getting the math being used.
< gribble> https://github.com/bitcoin/bitcoin/issues/11796 | [tests] Functional test naming convention by ajtowns · Pull Request #11796 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11774 | [WIP] [tests] Rename functional tests by ajtowns · Pull Request #11774 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] laanwj closed pull request #11793: Docs: Bump OS X version to 10.13 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11793
< bitcoin-git> [bitcoin] laanwj closed pull request #9254: [depends] ZeroMQ 4.2.2 (master...zeromq-4-2-0) https://github.com/bitcoin/bitcoin/pull/9254
< bitcoin-git> [bitcoin] Varunram opened pull request #11793: Docs: Bump OS X version to 10.13 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11793

2017-11-29

< bitcoin-git> [bitcoin] aaron-hanson opened pull request #11792: Trivial: fix comments for ZeroMQ bitcoind args (master...trivial-zeromq-arguments-comments) https://github.com/bitcoin/bitcoin/pull/11792
< jonasschnelli> Anyone up for a quick review: https://github.com/bitcoin/bitcoin/pull/11616/files?
< jimpo> leveldb docs say that DB is safe for concurrent access by multiple threads: https://github.com/bitcoin/bitcoin/blob/master/src/leveldb/include/leveldb/db.h#L42. Is it assumed that CDBWrapper is as well or no?
< bitcoin-git> [bitcoin] jnewbery opened pull request #11791: [tests] Rename NodeConn and NodeConnCB (master...rename_node_conn) https://github.com/bitcoin/bitcoin/pull/11791
< bitcoin-git> [bitcoin] eklitzke opened pull request #11790: Add pixmaps for testnet and regtest (master...pixmaps) https://github.com/bitcoin/bitcoin/pull/11790
< eck> are there pixmaps for bitcoin testnet? i'd like to create .desktop file for bitcoin-qt -testnet=1 that uses the green logo, instead of the orange one
< bitcoin-git> [bitcoin] jnewbery opened pull request #11789: [tests] [travis-ci] Combine logs on failure (master...pr11779.2) https://github.com/bitcoin/bitcoin/pull/11789
< bitcoincore-slac> Just wanted to let everyone who has committed code to bitcoin core that there are A LOT of shout-outs and appreciation to all of you the past few days on Slack, Twitter, etc. We know what you have done and continuing to do and can't thank you enough!
< gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid permanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub
< Murch> That question is better suited for Bitcoin.stackexchange.com than for this channel. However, the difficulty scales on a range of 2^256, so that scenario is pretty far-fetched.
< erichCompSci> Hello, I was wondering about the following problem. Miners in bitcoin verify transactions in the blockchain by hashing the previous blocks header, transaction data and a nonce value. However, the block is only considered a legitimate block
< gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid permanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] rawodb closed pull request #11787: Support for SegWit addresses, change addresses and UI request payment (master...pr/segwit_addresses_master) https://github.com/bitcoin/bitcoin/pull/11787
< BlueMatt> sipa: if you get particularly bored, I went down a way-too-deep rabbit hole reading mapBlocksUnlinked and pruning logic, and ended up with a few teaks to help my understanding and fix some tiny edge cases as I go....care to take a look at all but the top commit on https://github.com/TheBlueMatt/bitcoin/commits/2017-11-unlinked-blockx-fixes and tell me if its worth upstreaming?
< larafale> is UnspentTransactionOutputs only available throught REST ? I can also run that command throught bitcoin-cli I guess?
< gribble> https://github.com/bitcoin/bitcoin/issues/8549 | zmq: mempool notifications by jmcorgan · Pull Request #8549 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/9254 | [depends] ZeroMQ 4.2.2 by fanquake · Pull Request #9254 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11737 | Document partial validation in ConnectBlock() by sdaftuar · Pull Request #11737 · bitcoin/bitcoin · GitHub
< bitcoin-git> bitcoin/master 32c9b57 Wladimir J. van der Laan: Merge #11753: clarify abortrescan rpc use...
< bitcoin-git> bitcoin/master 8b2c733 Gregory Sanders: clarify abortrescan rpc use
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/46d1ebfcf854...32c9b570fcea
< gribble> https://github.com/bitcoin/bitcoin/issues/11785 | Prevent file-descriptor exhaustion from RPC layer by vii · Pull Request #11785 · bitcoin/bitcoin · GitHub
< aj> "<bitcoin-git> [bitcoin] vii opened pull request #11785: ..." came through earlier
< bitcoin-git> bitcoin/master e1a8ec5 Andras Elso: Fix: Open files read only if requested
< bitcoin-git> bitcoin/master e970396 Wladimir J. van der Laan: Merge #11747: Fix: Open files read only if requested...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/26efc220a13a...e97039605e0d
< wumpus> but ask in #bitcoin please this is not a help channel
< wumpus> #bitcoin please
< shadow_walker> should I use the bitcoincore.io or https://github.com/bitcoin/bitcoin
< shadow_walker> I need some help to create a bitcoin web wallet
< kallewoof> Running "bash bitcoin/contrib/gitian-build.sh" works fine so no biggie, just annoying.
< bitcoin-git> [bitcoin] vii opened pull request #11785: Prevent file-descriptor exhaustion from RPC layer (master...master) https://github.com/bitcoin/bitcoin/pull/11785
< bitcoin-git> [bitcoin] MoneyMakerLTD opened pull request #11784: Update README.md (master...master) https://github.com/bitcoin/bitcoin/pull/11784

2017-11-28

< gribble> https://github.com/bitcoin/bitcoin/issues/8469 | [POC] Introducing property based testing to Core by Christewart · Pull Request #8469 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/1337 | Quieter initial block download by rebroad · Pull Request #1337 · bitcoin/bitcoin · GitHub
< jonasschnelli> Masterboy: please answer in the #bitcoin channel
< sipa> Masterboy: #bitcoin
< jonasschnelli> blockchain: better use #bitcoin for this... off-topic here.
< blockchain> hi I have installed bitcoin-core 15.01 and want to use the replace by fee. but the "increase transaction fee" option is grey, how can i activate it ?
< gribble> https://github.com/bitcoin/bitcoin/issues/11781 | Add `-debuglogfile` option by laanwj · Pull Request #11781 · bitcoin/bitcoin · GitHub
< MarcoFalke> nanotube: https://github.com/nanotube/supybot-bitcoin-marketmonitor is only for the market, no?
< gribble> https://github.com/bitcoin/bitcoin/issues/3 | Encrypt wallet · Issue #3 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11783 | Fix shutdown in case of errors during initialization by laanwj · Pull Request #11783 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10286 | Call wallet notify callbacks in scheduler thread (without cs_main) by TheBlueMatt · Pull Request #10286 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11781 | Add `-debuglogfile` option by laanwj · Pull Request #11781 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11783 | Fix shutdown in case of errors during initialization by laanwj · Pull Request #11783 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] laanwj closed pull request #11287: DRY config header inclusion (master...refactor/dry-config) https://github.com/bitcoin/bitcoin/pull/11287
< bitcoin-git> [bitcoin] laanwj opened pull request #11783: Fix shutdown in case of errors during initialization (master...2017_11_notify_callbacks_shutdown_crash) https://github.com/bitcoin/bitcoin/pull/11783
< bitcoin-git> [bitcoin] laanwj opened pull request #11781: Add `-debuglogfile` option (master...2017_11_logfile) https://github.com/bitcoin/bitcoin/pull/11781
< gribble> https://github.com/bitcoin/bitcoin/issues/11457 | Introduce BanMan by theuni · Pull Request #11457 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11647 | 0.15: Backports by MarcoFalke · Pull Request #11647 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] fanquake closed pull request #9754: Change NULLFAIL => SIG_NULLFAIL. (master...feature/unify_sig_nullfail) https://github.com/bitcoin/bitcoin/pull/9754
< gribble> https://github.com/bitcoin/bitcoin/issues/9754 | Change NULLFAIL => SIG_NULLFAIL. by richardkiss · Pull Request #9754 · bitcoin/bitcoin · GitHub
< jonasschnelli> raheel_: this is the core dev channel, pleae use #bitcoin or #bitcoin-dev for your Q
< wumpus> raheel_, take this to #bitcoin
< wumpus> raheel_: #bitcoin
< bitcoin-git> [bitcoin] fanquake closed pull request #9859: Make TestBlockValidity optional in CreateNewBlock (master...tbv-optional) https://github.com/bitcoin/bitcoin/pull/9859
< wumpus> this is what we should avoid: https://github.com/bitcoin/bitcoin/pull/11747 the person posts a straightforward two-line fix for an actual issue, when well-meaning but overly zealous review comments get them to refactor things in a questionable way resulting in much more discussion and doubt of correctness
< bitcoin-git> [bitcoin] laanwj closed pull request #11722: Switched sync.{cpp,h} to std threading primitives. (master...tjps_sync_antiboost) https://github.com/bitcoin/bitcoin/pull/11722
< gribble> https://github.com/bitcoin/bitcoin/issues/11389 | Support having SegWit always active in regtest (sipa, ajtowns, jnewbery) by sipa · Pull Request #11389 · bitcoin/bitcoin · GitHub
< Varunram> rusty: aj: had the bugs few days back, turned out to be exactly what rusty specified, there'd be another .bitcoin directory somewhere. Once I changed home directories, it went well
< gmurf> any good places to learn how to use Bitcoin api

2017-11-27

< bitcoin-git> [bitcoin] MarcoFalke opened pull request #11779: qa: Combine logs on travis by default (master...Mf1711-travisQaLogs) https://github.com/bitcoin/bitcoin/pull/11779
< gribble> https://github.com/bitcoin/bitcoin/issues/2 | Long-term, safe, store-of-value · Issue #2 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11775: Move fee estimator into validationinterface/cscheduler thread (master...2017-09-background-feeest) https://github.com/bitcoin/bitcoin/pull/11775
< gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid permanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid permanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] jnewbery closed pull request #11047: [tests] rename functional tests (master...rename_functional_tests) https://github.com/bitcoin/bitcoin/pull/11047
< bitcoin-git> [bitcoin] jnewbery opened pull request #11771: [tests] Change invalidtxrequest to use BitcoinTestFramework (master...refactor_invalidtxrequest) https://github.com/bitcoin/bitcoin/pull/11771
< bitcoin-git> [bitcoin] joemphilips opened pull request #11770: [REST] add a rest endpoint for estimatesmartfee, docs, and test (master...rest_fee) https://github.com/bitcoin/bitcoin/pull/11770
< sipa> and it likely conflicts with how people actually use bitcoin in the real world now - where they expect a txid to be something you can track

2017-11-26

< archaeal> laptop - you do realize you're in #bitcoin-core-dev, right? Maybe try #bitcoin
< laptop> how profitable is it to mine bitcoin or alternative bitcoins in a pool like litecoin is it really worth your time
< achow101> you could use something else to broadcast, e.g. https://github.com/laanwj/bitcoin-submittx
< Randolf> jl2012: This channel is focused on the software development aspects of bitcoin core. What you've raised seems to be a usability question, which is much more likely to be served well on the #bitcoin channel. That's why I suggested that you ask there.
< Randolf> jl2012: Well, why don't you ask in the #bitcoin channel? Maybe it's already supported (I don't know).
< Randolf> jl2012: You seem to be asking a question about useability rather than about development. Have you tried asking your question in the #bitcoin channel?
< bitcoin-git> bitcoin/master a892218 MarcoFalke: Merge #11683: tests: Remove unused mininode functions {ser,deser}_int_vector(...). Remove unused imports....
< bitcoin-git> bitcoin/master f522fb7 practicalswift: tests: Remove unused mininode functions deser_int_vector(f) and ser_int_vector(l)
< bitcoin-git> bitcoin/master 0f3b752 practicalswift: Remove unused imports
< bitcoin-git> [bitcoin] MarcoFalke pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/a933cb14c75b...a89221873a3e

2017-11-25

< bitcoin-git> [bitcoin] fanquake closed pull request #11761: [WIP] [docs] initial QT documentation (master...qt-docs) https://github.com/bitcoin/bitcoin/pull/11761
< bitcoin-git> [bitcoin] aaron-hanson opened pull request #11765: [REST] added blockhash api, tests and documentation (master...rest-blockhash-endpoint) https://github.com/bitcoin/bitcoin/pull/11765

2017-11-24

< bitcoin-git> [bitcoin] practicalswift opened pull request #11762: Avoid locking mutexes that are already held by the same thread (master...remove-double-locks) https://github.com/bitcoin/bitcoin/pull/11762
< bitcoin-git> [bitcoin] Sjors opened pull request #11761: [docs] initial QT documentation (master...qt-docs) https://github.com/bitcoin/bitcoin/pull/11761

2017-11-23

< gribble> https://github.com/bitcoin/bitcoin/issues/11720 | iOS Deployment Target for RPC · Issue #11720 · bitcoin/bitcoin · GitHub
< Provoostenator> @jonasschnelli me too, but I think a more realistic scenario is more people running Bitcoin Core nodes and connecting their favorite wallet to it.
< jonasschnelli> I'd like to see more users using Bitcoin Core as a wallet
< jonasschnelli> The current bitcoin wallets do loose one of the primary elements Bitcoin can defeat "Trusted third parties are security holes".
< jonasschnelli> b) you add a script to your bitcoin core machine that would server over TLS (an RPC proxy)
< gribble> https://github.com/bitcoin/bitcoin/issues/10794 | Add simple light-client mode (RPC only) by jonasschnelli · Pull Request #10794 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] ldm5180 opened pull request #11760: [crypto] Refactor HMAC_SHA to eliminate code duplication (master...generic-hmac_sha) https://github.com/bitcoin/bitcoin/pull/11760
< jonasschnelli> Provoostenator: please review https://github.com/bitcoin/bitcoin/pull/10794 (its a stepping stone for GUI sep.)
< gribble> https://github.com/bitcoin/bitcoin/issues/11667 | Add scripts to dumpwallet RPC by MeshCollider · Pull Request #11667 · bitcoin/bitcoin · GitHub
< jonasschnelli> I think long term we should not expect that private keys are on the same machine then bitcoin core runs (at least not with the current one process design)
< wumpus> here, a PR by first-time contributor that gets a lot of review instantly: https://github.com/bitcoin/bitcoin/pull/11747
< Provoostenator> Has Google Summer of Code ever done Bitcoin Core projects? https://developers.google.com/open-source/gsoc/
< wumpus> bitcoin isn't really a good project for first time open source contributors in that regard, some projects just merge everything effectively instantly, but we cannot have a policy like that, not for first contributors ither
< Provoostenator> I'd like to propose adding a project Onboarding to this list: https://github.com/bitcoin/bitcoin/projects
< wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag
< gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub

2017-11-22

< jonasschnelli> cluelessperson: this is also a handy resource (seems up to date): https://en.bitcoin.it/wiki/Protocol_documentation
< sipa> cluelessperson: bitcoin.org developer documentation is pretty good
< bitcoin-git> [bitcoin] practicalswift opened pull request #11754: Add missing cs_wallet locks when accessing m_last_block_processed (master...missing-m_last_block_processed-locks) https://github.com/bitcoin/bitcoin/pull/11754
< bitcoin-git> [bitcoin] practicalswift closed pull request #11749: wallet: Set m_last_block_processed to nullptr in SetNull() (master...m_last_block_processed) https://github.com/bitcoin/bitcoin/pull/11749
< bitcoin-git> [bitcoin] practicalswift closed pull request #11749: wallet: Set m_last_block_processed to nullptr in SetNull() (master...m_last_block_processed) https://github.com/bitcoin/bitcoin/pull/11749
< bitcoin-git> [bitcoin] instagibbs opened pull request #11753: clarify abortrescan rpc use (master...abortrescanclarity) https://github.com/bitcoin/bitcoin/pull/11753
< bitcoin-git> [bitcoin] jamesob closed pull request #11751: Use override in CCoinsView* subclasses (master...add-override-coins) https://github.com/bitcoin/bitcoin/pull/11751
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11743: qa: Add multiwallet prefix test (master...Mf1711-qaMultiwallet) https://github.com/bitcoin/bitcoin/pull/11743
< jeffrade> promag: So this is nothing that will live in the repo, e.g. bitcoin/test/functional/ ?
< jeffrade> I posted a question yesterday on https://github.com/bitcoin/bitcoin/issues/3172 I need some clarification.
< bitcoin-git> [bitcoin] practicalswift opened pull request #11749: Set m_last_block_processed to nullptr in SetNull() (master...m_last_block_processed) https://github.com/bitcoin/bitcoin/pull/11749
< gribble> https://github.com/bitcoin/bitcoin/issues/9849 | Qt: Network Watch tool by luke-jr · Pull Request #9849 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/5896 | [Qt][PoC] introduce "core-pulse" by jonasschnelli · Pull Request #5896 · bitcoin/bitcoin · GitHub
< jonasschnelli> Would adding block size(s) and weight to the block index be completely wrong? https://github.com/bitcoin/bitcoin/compare/master...jonasschnelli:2017/11/blockindex_size?expand=1
< gribble> https://github.com/bitcoin/bitcoin/issues/11708 | Add P2SH-P2WSH support to signrawtransaction and listunspent RPC by MeshCollider · Pull Request #11708 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] sipa closed pull request #11746: trivial: Fix unsuccessful typo (master...unsuccesful) https://github.com/bitcoin/bitcoin/pull/11746
< bitcoin-git> bitcoin/master 5ea932a Pieter Wuille: Merge #11746: trivial: Fix unsuccessful typo...
< bitcoin-git> bitcoin/master d2ea2bc practicalswift: trivial: Fix unsuccessful typo
< bitcoin-git> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d4267a3ab271...5ea932a51083
< bitcoin-git> [bitcoin] merehap opened pull request #11748: [Tests] Adding unit tests for GetDifficulty in blockchain.cpp. (master...blockchain_unittests) https://github.com/bitcoin/bitcoin/pull/11748

2017-11-21

< bitcoin-git> [bitcoin] fanquake closed pull request #11735: [refactor] Remove magic numbers from HMAC SHA256 (master...eliminate_magic_numbers) https://github.com/bitcoin/bitcoin/pull/11735
< aj> meshcollider: mainnet bitcoin.conf and network.conf live in the same directory :(
< meshcollider> Or would having them both called bitcoin.conf be confusing
< aj> meshcollider: i'm not sure if there's a use case... atm, you could have standard settings in bitcoin.conf and special settings in network.conf (mainnet addnode's say), and switch either independently via command line options. that just seems a bit more flexible and maybe natural to me?
< aj> meshcollider: i worry about that too. current behaviour is that bitcoin.conf is loaded first and network.conf second (so bitcoin.conf can specify the network), and any setting in bitcoin.conf overrides any setting in network.conf
< aj> meshcollider: yeah: patch makes bitcoind load two config files, .bitcoin/bitcoin.conf and .bitcoin/testnet3/network.conf; -conf lets you choose a different name for the first one, -netconf a different name for the second one
< gribble> https://github.com/bitcoin/bitcoin/issues/10996 | Add per-network config file network.conf by ajtowns · Pull Request #10996 · bitcoin/bitcoin · GitHub
< andytoshi> Chris_Stewart_5: #bitcoin-mining will probably be more helpful, or #bitcoin. this channel is specifically about software development of Bitcoin Core
< bitcoin-git> [bitcoin] Elbandi opened pull request #11747: Fix: Open files read only if requested (master...fix11745) https://github.com/bitcoin/bitcoin/pull/11747
< bitcoin-git> [bitcoin] practicalswift opened pull request #11746: trivial: Fix unsuccessful typo (master...unsuccesful) https://github.com/bitcoin/bitcoin/pull/11746
< bitcoin-git> [bitcoin] practicalswift opened pull request #11744: net: Add missing locks in net.{cpp,h} (master...missing-net-locks) https://github.com/bitcoin/bitcoin/pull/11744
< gribble> https://github.com/bitcoin/bitcoin/issues/11047 | [tests] rename functional tests by jnewbery · Pull Request #11047 · bitcoin/bitcoin · GitHub
< wumpus> also it'd make no sense, we'd have to distinguish which daemon is logging for each line - if you really want to dump all your bitcoin logging to one place, you can already use -printtoconsole w/ some log aggregation like systemd
< gribble> https://github.com/bitcoin/bitcoin/issues/10996 | Add per-network config file network.conf by ajtowns · Pull Request #10996 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #11743: qa: Add multiwallet prefix test (master...Mf1711-qaMultiwallet) https://github.com/bitcoin/bitcoin/pull/11743
< wumpus> also if you just want to test w/ bitcoin and times there's setmocktime
< Sentineo> so if I set my time to 2015 would I invalidate blocks? It sounds like bitcoin-core would take the blockchain (and other nodes) as the source of time
< bitcoin-git> [bitcoin] laanwj closed pull request #11738: Fix sendrawtransaction hang when sending a tx already in mempool (master...2017-11-fix-sendraw-block) https://github.com/bitcoin/bitcoin/pull/11738
< bitcoin-git> bitcoin/master d4267a3 Wladimir J. van der Laan: Merge #11738: Fix sendrawtransaction hang when sending a tx already in mempool...
< bitcoin-git> bitcoin/master d9340ce Matt Corallo: Fix sendrawtransaction hang when sending a tx already in mempool
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/901ba3e38194...d4267a3ab271
< fanquake> JeffSlentz Also read through https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md & https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md . They explain how the development process works, and preferred code styles etc.
< fanquake> JeffSlentz Checkout the "good first issue" label on repo. https://github.com/bitcoin/bitcoin/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
< Randolf> JeffSlentz: If not, then there may be other options for you, but you'll probably need to ask about those possibilities in the #bitcoin channel.
< JeffSlentz> Hey, as a recent grad with not much experience with the Bitcoin Core project, are there any suggestions for contributing?
< Murch> morcos: I was just looking at fee rate estimation. I'm surprised that the Bitcoin Core estimate is still on 170 for second block target when the network has been clearing the mempool of <40 for four days.

2017-11-20

< bitcoin-git> [bitcoin] eklitzke opened pull request #11741: Add -logdir option to control where debug.log lives (master...logdir) https://github.com/bitcoin/bitcoin/pull/11741
< HisMajesty_> Everything ECDSA Public Key (Bitcoin Compatible): 1N2EWy7LroJVFYXtmYZryh7W9eV3k6qajd exists since Mon Oct 02 2017 23:48:19 GMT-0700 (Pacific Daylight Time)
< HisMajesty_> Hello Bitcoin Core Developers
< bitcoin-git> [bitcoin] jonasschnelli opened pull request #11740: Implement BIP159 NODE_NETWORK_LIMITED (pruned peers) *signalling only* (master...2017/11/NNL_signaling) https://github.com/bitcoin/bitcoin/pull/11740
< bitcoin-git> [bitcoin] sdaftuar opened pull request #11739: RFC: Enforce SCRIPT_VERIFY_P2SH and SCRIPT_VERIFY_WITNESS from genesis (master...2017-09-p2sh-segwit-from-genesis) https://github.com/bitcoin/bitcoin/pull/11739
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11714: [tests] Test that mempool rejects coinbase transactions (master...test-mempool-rejects-coinbase) https://github.com/bitcoin/bitcoin/pull/11714
< bitcoin-git> bitcoin/master 901ba3e MarcoFalke: Merge #11714: [tests] Test that mempool rejects coinbase transactions...
< bitcoin-git> bitcoin/master 65e91f5 James O'Beirne: [tests] Test that mempool rejects coinbase transactions
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7a43fbb959c3...901ba3e38194
< bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11738: Fix sendrawtransaction hang when sending a tx already in mempool (master...2017-11-fix-sendraw-block) https://github.com/bitcoin/bitcoin/pull/11738
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #11729: [docs] links to code style guides (master...docs-style-guide-links) https://github.com/bitcoin/bitcoin/pull/11729
< bitcoin-git> bitcoin/master 7a43fbb MarcoFalke: Merge #11729: [docs] links to code style guides...
< bitcoin-git> bitcoin/master fe27a72 Sjors Provoost: [docs] links to code style guides
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/7293d064133a...7a43fbb959c3
< bitcoin-git> [bitcoin] sdaftuar opened pull request #11737: Document partial validation in ConnectBlock() (master...2017-11-comment-validation) https://github.com/bitcoin/bitcoin/pull/11737
< bitcoin-git> [bitcoin] ldm5180 opened pull request #11735: [refactor] Remove magic numbers from HMAC SHA256 (master...eliminate_magic_numbers) https://github.com/bitcoin/bitcoin/pull/11735
< Provoostenator> I'm looking at the multiwallet GUI PR now, since it's in this list: https://github.com/bitcoin/bitcoin/projects/8
< bitcoin-git> [bitcoin] practicalswift opened pull request #11734: rpc: Work around Clang thread safety analysis quirks (master...clang-thread-safety-quirks) https://github.com/bitcoin/bitcoin/pull/11734
< bitcoin-git> [bitcoin] Sjors closed pull request #11730: WIP [RPC] [Wallet] walletdowngrade command (which can remove HD) (master...wallet-downgrade) https://github.com/bitcoin/bitcoin/pull/11730
< bitcoin-git> [bitcoin] practicalswift opened pull request #11733: Remove redundant locks (master...redundant-locks) https://github.com/bitcoin/bitcoin/pull/11733
< gribble> https://github.com/bitcoin/bitcoin/issues/7165 | build: Enable C++11 in build, require C++11 compiler by laanwj · Pull Request #7165 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/11732 | RFC: bump GCC requirement to 4.8 · Issue #11732 · bitcoin/bitcoin · GitHub
< wumpus> is anyone building bitcoin core using g++ 4.7? if so, please weigh in here #11732
< bitcoin-git> [bitcoin] laanwj closed pull request #11110: [script] Avoid implicit casts from bool to CScriptNum (master...implicit-casts-from-bool-to-cscriptnum) https://github.com/bitcoin/bitcoin/pull/11110
< bitcoin-git> [bitcoin] laanwj closed pull request #11662: [0.15] Sanity-check script sizes in bitcoin-tx (0.15...bitcoin-tx-script-sizes-0.14) https://github.com/bitcoin/bitcoin/pull/11662

2017-11-19

< sipa> that doesn't look like bitcoin core
< bitcoin-git> [bitcoin] Sjors opened pull request #11730: WIP [RPC] [Wallet] walletdowngrade command (which can remove HD) (master...wallet-downgrade) https://github.com/bitcoin/bitcoin/pull/11730
< bitcoin-git> [bitcoin] Sjors opened pull request #11729: [docs] links to code style guides (master...docs-style-guide-links) https://github.com/bitcoin/bitcoin/pull/11729
< gribble> https://github.com/bitcoin/bitcoin/issues/9195 | Debug console needs a little documentation on usage · Issue #9195 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] laanwj closed pull request #11698: [Docs] [Qt] RPC-Console nested commands documentation (master...doc-rpc-console) https://github.com/bitcoin/bitcoin/pull/11698