< bitcoin-git>
[bitcoin] instagibbs opened pull request #9262: Don't consider coins available if too many ancestors in mempool (master...toolong) https://github.com/bitcoin/bitcoin/pull/9262
< bitcoin-git>
[bitcoin] morcos opened pull request #9261: Add unstored orphans with rejected parents to recentRejects (master...orphanRejects) https://github.com/bitcoin/bitcoin/pull/9261
< gribble>
https://github.com/bitcoin/bitcoin/issues/8498 | Optimization: Minimize the number of times it is checked that no money... by jtimon · Pull Request #8498 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/9260 | Mrs Peacock in The Library with The Candlestick (killed main.{h,cpp}) by TheBlueMatt · Pull Request #9260 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #9260: Mrs Peacock in The Library with The Candlestick (killed main.{h,cpp}) (master...net_processing_file) https://github.com/bitcoin/bitcoin/pull/9260
< bitcoin-git>
bitcoin/master c1a5227 Pieter Wuille: Merge #9253: Fix calculation of number of bound sockets to use...
< bitcoin-git>
[bitcoin] sipa closed pull request #9253: Fix calculation of number of bound sockets to use (master...2016-11-nbind) https://github.com/bitcoin/bitcoin/pull/9253
< bitcoin-git>
bitcoin/master 9e1f468 Matt Corallo: Fix calculation of number of bound sockets to use
< bitcoin-git>
[bitcoin] laanwj opened pull request #9255: qt: layoutAboutToChange signal is called layoutAboutToBeChanged (master...2016_12_qt_signals_warnings) https://github.com/bitcoin/bitcoin/pull/9255
< luke-jr>
rebroad: seek clarification in #bitcoin, not here
< rebroad>
I have attempted to seek clarification previously on a clear and concise definition of "altcoin" and raised an issue both on the bitcoin project and for bitcoin.org to address this
< luke-jr>
general & meta=#bitcoin ; bitcoin development=#bitcoin-dev ; Core dev=#bitcoin-core-dev ; wiki=#bitcoin-wiki ; trading=#bitcoin-otc ; far future dev & hardforks = #bitcoin-wizards ; mining=#bitcoin-mining ; altcoins=##altcoin-dev
< rebroad>
or #bitcoin-dev I'd have thought, since development is the key desire to talk about
< luke-jr>
#bitcoin is as meta as I know of
< wumpus>
this is also not the meta-channel "what to discuss in #bitcoin-core-dev"
< wumpus>
"Bitcoin Core development discussion and commit log"
< sipa>
(in this specific channel; there is #bitcoin-wizards for example for exotic ideas that may or may not make it into bitcoin some day)
< rebroad>
sipa, it is drifting occaionally OT but comes back to bitcoin often enough :)
< rebroad>
sipa, speaking of that. dash has more nodes than bitcoin due to that I think
< wumpus>
rebroad: exactly, IRC is much more in the spirit of bitcoin, though not decentralized it is a generic internet protocol that everyone can write clients for, some of better quality than others, but interoperability is key
< rebroad>
perhaps rather than using PGP keys we could use bitcoin address keys
< gmaxwell>
probably we should have some webform on bitcoin-core.org that does gpg in the browser.
< achow101>
and sometimes they mark it as a bitcoin miner
< Victorsueca>
kaspersky is marking bitcoin-qt as coin stealing malware
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #9253: Fix calculation of number of bound sockets to use (master...2016-11-nbind) https://github.com/bitcoin/bitcoin/pull/9253
< bitcoin-git>
[bitcoin] sipa closed pull request #9244: Trivial refactor: Remove extern keyword from function declarations (master...no-extern-funcdecl) https://github.com/bitcoin/bitcoin/pull/9244
< bitcoin-git>
bitcoin/master 72ae6f8 Pieter Wuille: Merge #9244: Trivial refactor: Remove extern keyword from function declarations...
< bitcoin-git>
bitcoin/master 446a8f9 Karl-Johan Alm: Trivial refactor: Remove extern keyword from function declarations, as they are extern by default.
< bitcoin-git>
[bitcoin] sdaftuar opened pull request #9252: Release cs_main before calling ProcessNewBlock (cmpctblock handling) (master...cb-lock) https://github.com/bitcoin/bitcoin/pull/9252
< bitcoin-git>
[bitcoin] wodry closed pull request #9249: Improvement of documentation of command line parameter 'whitelist' (master...patch-1) https://github.com/bitcoin/bitcoin/pull/9249
< bitcoin-git>
[bitcoin] wodry opened pull request #9251: Improvement of documentation of command line parameter 'whitelist' (master...patch-3) https://github.com/bitcoin/bitcoin/pull/9251
< bitcoin-git>
[bitcoin] wodry opened pull request #9249: Improvement of documentation of command line parameter 'whitelist' (master...patch-1) https://github.com/bitcoin/bitcoin/pull/9249
< bitcoin-git>
bitcoin/0.13 94531b5 Wladimir J. van der Laan: torcontrol: Explicitly request RSA1024 private key...
< bitcoin-git>
[bitcoin] gmaxwell opened pull request #9246: Developer docs about existing subtrees. (master...devdocs_for_subtrees) https://github.com/bitcoin/bitcoin/pull/9246
< bitcoin-git>
[bitcoin] luke-jr opened pull request #9245: Drop IO priority to idle while reading blocks for getblock requests (master...ionice) https://github.com/bitcoin/bitcoin/pull/9245
< bitcoin-git>
[bitcoin] gmaxwell opened pull request #9236: Fix races for strMiscWarning and fLargeWork*Found, make QT runawayException use GetWarnings (master...strMiscraceless) https://github.com/bitcoin/bitcoin/pull/9236
< bitcoin-git>
[bitcoin] kallewoof opened pull request #9235: Refactor: Removes all uses of `using namespace` in all source files. (master...no-using-ns2) https://github.com/bitcoin/bitcoin/pull/9235
< bitcoin-git>
[bitcoin] pstratem opened pull request #9227: Make nWalletDBUpdated atomic to avoid a potential race. (master...2016-11-26-nwalletdbupdated-race) https://github.com/bitcoin/bitcoin/pull/9227
< parsimony_>
hi Bitcoin Core devs and affiliated parties... has anyone with some reputation considered offering the big-blockists a method of saving face while coming around to support Segwit?
< layman01>
'because bitcoin not designed that way' is an empty answer too
< BlueMatt>
layman01: there are lots of answers depending on what your actual use-case is....problem is youre asking for a solution to a specific question to which there is no answer.....maybe go to #bitcoin and try again except start by stating waht, exactly youre trying to do
< gmaxwell>
layman01: CT's memo data doesn't add any other data at all. (also, even if it did: CT isn't part of Bitcoin-- though the memo data wouldn't have made sense if it added data, so I wouldn't have done it if it did)
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #9100: tx_valid: re-order inputs to how they are encoded (master...testorder) https://github.com/bitcoin/bitcoin/pull/9100
< bitcoin-git>
bitcoin/master 5262a15 Daniel Cousens: tx_valid: re-order inputs to how they are encoded
< bitcoin-git>
bitcoin/master 97ec6e5 MarcoFalke: Merge #9100: tx_valid: re-order inputs to how they are encoded...
< bitcoin-git>
[bitcoin] fanquake closed pull request #8983: WIP: Log block height and size when received (master...ShowBlockHeightAndSizeWhenReceived) https://github.com/bitcoin/bitcoin/pull/8983
< bitcoin-git>
[bitcoin] laanwj opened pull request #9219: doc: Improve windows build instructions using Linux subsystem (master...2016_11_windows_build_update) https://github.com/bitcoin/bitcoin/pull/9219
< bitcoin-git>
[bitcoin] laanwj closed pull request #9189: Always add default_witness_commitment with GBT client support (master...alwayscommit) https://github.com/bitcoin/bitcoin/pull/9189
< bitcoin-git>
bitcoin/master d932159 Wladimir J. van der Laan: Merge #9189: Always add default_witness_commitment with GBT client support...
< bitcoin-git>
bitcoin/master 95f4a03 Suhas Daftuar: [qa] Test getblocktemplate default_witness_commitment
< bitcoin-git>
bitcoin/master ad04d1c Pieter Wuille: Always add default_witness_commitment with GBT client support
< gmaxwell>
bitcoin358: add more fees later in the chain and enjoy giving them to miners running Bitcoin Core, since it will happily notice those fees later in the chain.
< rusty>
gmaxwell: it's your fault I now have 'while sleep 10; do bitcoin-cli getblocktemplate | awk '/"fee"/ { FEES += $2 } /"height"/ { HEIGHT = $2 } END { print HEIGHT,FEES }'; done' running in a terminal here, BTW.
< bitcoin-git>
[bitcoin] sipa closed pull request #9199: Always drop the least preferred HB peer when adding a new one. (master...remove_high_bandwidth_zombies) https://github.com/bitcoin/bitcoin/pull/9199
< bitcoin-git>
bitcoin/master 407d923 Pieter Wuille: Merge #9199: Always drop the least preferred HB peer when adding a new one....
< bitcoin-git>
bitcoin/master ca8549d Gregory Maxwell: Always drop the least preferred HB peer when adding a new one....
< cfields>
BlueMatt: i suppose we're looking at this from different sides. I originally rewrote the net layer and tried to plug it into bitcoin. I didn't like the result. I started instead trying to rip bitcoin out of our net layer, and that's where we are now. The next step would be to split the resulting CConnman into high and low levels. That's next.
< BlueMatt>
cfields: bitcoin-specific hacks like what?
< cfields>
BlueMatt: for context, I first wrote a completely low-level, no-bitcoin network layer. Plugging that into bitcoin proved to require a bunch of bitcoin-specific hacks. In the end, I didn't think it was an improvement over what we had.
< BlueMatt>
cfields: well I dont think you mean that tighter-integration is needed between bitcoin logic and libevent/async
< sipa>
CConnman is exactly the bitcoin specific thing
< BlueMatt>
sipa: CConnman should be a networking library, not a bitcoin networking library
< BlueMatt>
sipa: the way i see it: processing of messages and the peer handling is already well-separated, or at least somewhat separated...we currently have bitcoin-specific and general-networking code intermixed in a bunch of places, and that also needs to be separated
< brhood9_>
Is there any way that you all could help me figure out what is going on with my bitcoin transaction? I have asked and looked and read everywhere. The transaction that you need to look at is this one.
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #9139: Change sync_blocks to pick smarter maxheight (on top of #9196) (master...sync-height) https://github.com/bitcoin/bitcoin/pull/9139
< bitcoin-git>
bitcoin/master 0de7fd3 MarcoFalke: Merge #9139: Change sync_blocks to pick smarter maxheight (on top of #9196)...
< bitcoin-git>
bitcoin/master 1126c85 Russell Yanofsky: [qa] Change sync_blocks to pick smarter maxheight...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #9139: Change sync_blocks to pick smarter maxheight (on top of #9196) (master...sync-height) https://github.com/bitcoin/bitcoin/pull/9139
< BlueMatt>
so I could PR relay-compact-block-before-full-validation (https://github.com/TheBlueMatt/bitcoin/commits/2016-11-compact-fast-relay) but now I'm kinda thinking I dont want to do that prior to there being multithreaded ProcessMessages with some smarts to respond to getblocktxn without a lock for the latest block...thoughts?