2018-09-13

< kallewoof> jimpo: reading https://github.com/bitcoin/bips/pull/725#pullrequestreview-154741923 it looks like you're suggesting the proof of funds should be a (fakeish) transaction, and the messsage signing should not be. Am I understanding that right? If so, it seems like you could just do transaction in both cases to simplify the spec. I.e. for signing message, craft two txs with the latter spending the former and former using
< gribble> https://github.com/bitcoin/bitcoin/issues/14007 | tests: Run functional test on Windows and enable it on Appveyor by ken2812221 · Pull Request #14007 · bitcoin/bitcoin · GitHub

2018-09-12

< gmaxwell> I'm not aware of lightning watchtowers relaying bitcoin blocks.
< gmaxwell> I'm not opposed it it but skeptical that its all that useful for bitcoin in general. I suggested the generic because I could imagine more uses for that. (even if just test shims)
< Jmabsd> Where in Bitcoin's source code is the TxFee estimation logics for when planning to make a transaction?
< wumpus> I've added the list of pulls and authors to: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.17.0-Release-notes
< gribble> https://github.com/bitcoin/bitcoin/issues/13052 | trivial: Fix relevent typo by practicalswift · Pull Request #13052 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/12747 | Fix typos by practicalswift · Pull Request #12747 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/12393 | Fix a-vs-an typos by practicalswift · Pull Request #12393 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/12543 | Fix typos by practicalswift · Pull Request #12543 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13069 | docs: Fix typos by practicalswift · Pull Request #13069 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/12283 | Fix typos by practicalswift · Pull Request #12283 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14195 | fix export privkey der always compressed by fingera · Pull Request #14195 · bitcoin/bitcoin · GitHub
< kallewoof> reserve could have blinded inputs and outputs as well, or whatever else the bitcoin protocol is made to allow. As long as the spends are tangled up with the fake input (via SIGHASH_ALL or a mimblewimble kernel, or whatever), it doesn't matter."
< kallewoof> echeveria: To quote argument for a tx-like protocol: "It also works well with proof of reserve: the proof of reserve is a bitcoin transaction spending all the funds, but with an additional input (covered by SIGHASH_ALL) that points to a fake/invalid tx. This has the additional benefit of working in a forward compatible way with any future bitcoin extension, like confidential transactions or mimblewimble: your proof of
< kallewoof> Johnson Lau is suggesting reserving OP_MESSAGEONLY = 0xf0 as opcode for message signing, or alternatively "OP_RETURN msgXXX". It feels wasteful to take an opcode, but feedback would be nice: https://github.com/bitcoin/bips/pull/725#issuecomment-420421058
< gmaxwell> in any case, he came up before, he's some bitconnect promoter that claims the be one of the first bitcoin developers after satoshi and a bunch of other stuff that made no sense.

2018-09-11

< gribble> https://github.com/bitcoin/bitcoin/issues/14007 | tests: Run functional test on Windows and enable it on Appveyor by ken2812221 · Pull Request #14007 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14147 | net: Refactor ThreadSocketHandler by pstratem · Pull Request #14147 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< gribble> https://github.com/bitcoin/bitcoin/issues/13926 | [Tools] bitcoin-wallet-tool by jnewbery · Pull Request #13926 · bitcoin/bitcoin · GitHub
< gmaxwell> 10:48:20 < sipa> so either bitcoind or "bitcoin-qt -server" still need to automatically create a wallet
< sipa> so either bitcoind or "bitcoin-qt -server" still need to automatically create a wallet
< gribble> https://github.com/bitcoin/bitcoin/issues/13100 | gui: Add dynamic wallets support by promag · Pull Request #13100 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13756 | wallet: -avoidreuse feature for improved privacy by kallewoof · Pull Request #13756 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/9662 | Add createwallet "disableprivatekeys" option: a sane mode for watchonly-wallets by jonasschnelli · Pull Request #9662 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13059 | Dynamic wallet load / create / unload · Issue #13059 · bitcoin/bitcoin · GitHub
< BlueMatt> wumpus: there's a helluvalot more in rust-bitcoin than just primitives, but, ok, it *includes* primitives :p
< EucOcVrFfr2D> achow101: By the way, i found a duplicate test for the SIGNER role (still in functional/data/rpc_psbt.json), i opened a PR to remove it https://github.com/bitcoin/bitcoin/pull/14199
< EucOcVrFfr2D> The expected result in that test is equal to the input, the author @achow101 wanted to make sure bitcoind doesn't 'crash' on that scenario but it silently moves on. The scenario is when we're trying to sign a PSBT input but one of the requirement fails -> https://github.com/bitcoin/bips/blame/master/bip-0174.mediawiki#L342
< EucOcVrFfr2D> https://github.com/bitcoin/bitcoin/blob/v0.17.0rc3/test/functional/data/rpc_psbt.json#L90 the PSBT contains a PartiallySignedInput where RedeemScript=[OP_2, 029583bf39ae0a609747ad199addd634fa6108559d6c5cd39b4c2183f1ab96e07f, 02dab61ff49a14db6a7d02b0cd1fbb78fc4b18312b5b4e54dae4dba2fbfef536d7, OP_2, OP_CHECKMULTISIGVERIFY] and the ScriptPubKey=[OP_HASH160, 0fb9463421696b82c833af241c78c17ddbde4934, OP_EQUAL]
< wumpus> https://github.com/zw/bitcoin-gh-meta stopped updating?
< gribble> https://github.com/bitcoin/bitcoin/issues/14184 | Scripts and tools: increased timeout downloading by cisba · Pull Request #14184 · bitcoin/bitcoin · GitHub
< wumpus> dongcarl: multiple indices, like an sql database: https://github.com/bitcoin/bitcoin/blob/master/src/txmempool.h#L461
< fanquake> However I have been overly optimistic about removing Boost in the past, hah. https://github.com/bitcoin/bitcoin/issues/8875#issuecomment-280325296
< dongcarl> From https://github.com/bitcoin/bitcoin/pull/10299#issuecomment-298785082 it seems like sipa was going to "propose some other RNG changes first"
< wumpus> but for now, it's realistic to drop the dependency of bitcoind on openssl, but not the bitcoin-qt one
< gribble> https://github.com/bitcoin/bitcoin/issues/11622 | build: Add --disable-bip70 configure option by laanwj · Pull Request #11622 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10299 | Remove OpenSSL by sipa · Pull Request #10299 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/5885 | [WIP] Replace OpenSSL PRNG with built-in Fortuna implementation by sipa · Pull Request #5885 · bitcoin/bitcoin · GitHub
< warren> mryandao: the bigger risk is undiscovered bugs in the dependent libraries, this blew up several times in the past. Bitcoin devs found/reported/fixed many bugs in openssl and spent years to carefully write a replacement to get rid of openssl.
< warren> Yes it would be really nice to be able to use most of bitcoin core as libraries in other projects.
< warren> mryandao: multiple people here started years ago on the side of "This is crazy! We need to write a specification of what is Bitcoin." and a year or two of study later realize reimplmentations are too dangerous.
< dongcarl> wumpus and I talked about perhaps writing a standalone P2P bitcoin server in Rust that can FFI with bitcoind
< mryandao> anyone balsy enough to run parity-bitcoin?
< wumpus> rust-bitcoin is a library that implements some bitcoin primitives in rust, it's not meant as a replacement for bitcoin core, but something like python-bitcoinlib
< dongcarl> mryandao: rust-bitcoin isn't a rewrite yet, and BlueMatt isn't the only developer
< Jmabsd> achow101: did Bitcoin Core have any particular point with _not_ implementing an accounts abstraction - it's just Bitcoin Core wants to provide one single wallet balance, yes?
< achow101> Jmabsd: or really bip44 is bip32 with stuff added onto it. the original description of suggested derivations paths is very similar to core: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#the-default-wallet-layout
< Jmabsd> achow101: in other words, Bitcoin Core rolled it own thing.
< Jmabsd> achow101: so Bitcoin Core cut away the "coin" and the "account" derivation, and set purpose to 0 - that's pretty much it yes?
< Jmabsd> does Bitcoin Core do BIP 44 "m / purpose' / coin_type' / account' / change / address_index" form at all?
< Jmabsd> What is the structure of Bitcoin Core's HD wallet now (derivation paths); it's not going with BIP 44/49 today is it?
< kallewoof> achow101: is it, really? (easier to implement) In bitcoin core, I would add a BaseSignatureChecker that took a sighash and that's all. Just call VerifyScript with the inputs from the SignatureProof container.
< kallewoof> Several people on https://github.com/bitcoin/bips/pull/725 (Generic Signed Message Format) are suggesting I use a fake tx that the prover simply signs. I'm not sure what the benefits of doing this are, though..
< gribble> https://github.com/bitcoin/bitcoin/issues/14196 | [0.17][psbt] always drop the unnecessary utxo and convert non-witness utxo to witness when necessary by achow101 · Pull Request #14196 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< sipa> i think this may have been inadvertently fixed by https://github.com/bitcoin/bitcoin/pull/13723

2018-09-10

< gribble> https://github.com/bitcoin/bitcoin/issues/13482 | Remove boost::program_options dependency by ken2812221 · Pull Request #13482 · bitcoin/bitcoin · GitHub
< jarthur> Hey, I'm able to reproduce this on both Debian jessie and Debian stretch - https://github.com/bitcoin/bitcoin/issues/8749 - any of you run into it yet?
< dongcarl> Looking into libconsensus as well... I'm wondering if the API detailed in https://github.com/bitcoin/bitcoin/issues/6714 still holds... Seems like jtimon and NicolasDorier did a bunch of work that's been closed due to inactivity?
< echeveria> hey at least bitcoin doesn't make HTTP requests using raw sockets now.

2018-09-09

< gribble> https://github.com/bitcoin/bitcoin/issues/13200 | Process logs in a separate thread by jamesob · Pull Request #13200 · bitcoin/bitcoin · GitHub
< CubicEarth> In either case though, if blocks are to be retained until the pruning command is given by another service, it seems useful to have bitcoin have an option to not download more than some MBs or GBs worth of blocks

2018-09-08

< CubicEarth> but if lightning isn't started at same time, bitcoin will go ahead and fill all space it can find
< CubicEarth> it would be cool to have bitcoin not prune any blocks unless manually instructed, and yet also respect a storage limitation. So until manual pruning happened, it wouldn't download new blocks beyond some point.
< gmaxwell> this got answered hors ago in #bitcoin.
< Jmabsd> <crosspost from #bitcoin, please respond at #bitcoin, sorry for spam>Can I add witness data to a transaction input that is not necessarily segwit and where the witness data i'd add is unrelated to the output the input spends?</spam>
< gribble> https://github.com/bitcoin/bitcoin/issues/12775 | Integration of property based testing into Bitcoin Core by Christewart · Pull Request #12775 · bitcoin/bitcoin · GitHub

2018-09-07

< gribble> https://github.com/bitcoin/bitcoin/issues/14007 | tests: Run functional test on Windows and enable it on Appveyor by ken2812221 · Pull Request #14007 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14009 | Simple refactoring: Common code for decoding of hex "objects" by domob1812 · Pull Request #14009 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< _flow_> wumpus: jonasschnelli: regarding https://github.com/bitcoin/bitcoin/pull/13621 again: I looked into adding further tests for this, but the tests that I already re-enabled (https://github.com/bitcoin/bitcoin/pull/13621/files#diff-2a344479dbbded9df5d6a4abde2cd48cL60) are exaclty what my PR tries to fix. The issue the PR addresses was the reason those tests got disabled in the first place. Anything
< * wumpus> still remembers in the old bitcoin source, satoshi had remapped 'printf' with a macro, now that was confusing, but we should make a habit of switching around log function names that just adds to cognitive load
< fanquake> wumpus can you have a look at https://github.com/bitcoin-core/univalue/pull/11

2018-09-06

< MarcoFalke> We should put the minimum version into https://github.com/bitcoin-core/docs
< gribble> https://github.com/bitcoin/bitcoin/issues/12257 | [wallet] Use destination groups instead of coins in coin select by kallewoof · Pull Request #12257 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< BlueMatt> ah, right, the exploit-timeward-to-change-blocktime-and-fork-to-lock-it-in thing....I feel like thats something that needs more broad bitcoin-dev or whatever discussion, its not something to be discussed a technical planning meeting
< moneyball> * hardware wallet support in Bitcoin Core
< moneyball> * partially signed bitcoin transactions
< gmaxwell> Maybe people could think about rhavar's bustapay... I think it might be reasonable to support it in the bitcoin core wallet.
< gribble> https://github.com/bitcoin/bitcoin/issues/13869 | Filename and command line encoding issue on Windows · Issue #13869 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/10299 | Remove OpenSSL by sipa · Pull Request #10299 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14147 | net: Refactor ThreadSocketHandler by pstratem · Pull Request #14147 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/12775 | Integration of property based testing into Bitcoin Core by Christewart · Pull Request #12775 · bitcoin/bitcoin · GitHub
< wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircu
< wumpus> ok, https://github.com/bitcoin/bitcoin/milestone/33 has only release notes TODOs left, let's tag 0.17.0rc3 ?
< gribble> https://github.com/bitcoin/bitcoin/issues/13937 | HTTP Error 500: Internal Server Error
< gribble> https://github.com/bitcoin/bitcoin/issues/10102 | HTTP Error 500: Internal Server Error
< gribble> https://github.com/bitcoin/bitcoin/issues/14157 | [0.17] doc: merge upstream release-notes from bitcoin-core/bitcoin-devwiki by fanquake · Pull Request #14157 · bitcoin/bitcoin · GitHub

2018-09-04

< leishman> is there a reason logs don't show up on https://botbot.me/freenode/bitcoin-core-dev/ anymore? Is there a bot user in this channel?
< sipa> but not general discussion on bitcoin or usage
< sipa> polydin: no, this channel is about development of bitcoin core
< echeveria> polydin: you're invited to message me privately, or ask me on #bitcoin any questions you have about getting started.
< echeveria> you should ask in #bitcoin.
< provoostenator> 13937 can be found here, though without PR comments: https://github.com/Sjors/bitcoin/commits/2018/08/best-header-tracking
< gribble> https://github.com/bitcoin/bitcoin/issues/13937 | HTTP Error 500: Internal Server Error
< as1nc> hello folks, beautiful day here in south of france, bitcoin is doing great, what else can we ask ? :) oh yeah, anyone has any tips on how I could guess what type of a addresses is used (p2sh, p2pkh..) given an xpub, ypub or zpub key ? is that even possible ?
< gribble> https://github.com/bitcoin/bitcoin/issues/12138 | Track best-possible-headers by TheBlueMatt · Pull Request #12138 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13937 | HTTP Error 500: Internal Server Error
< achow101> both gmail and protonmail show me "from: X via bitcoin-dev"

2018-09-03

< kanzure> sipa: apologies. mailing list is in moderation mode since someone figured out how to spoof emails from bitcoin developers. emails were delayed due to my travel.
< gmaxwell> Aside, AFAICT walletprocesspsbt doesn't even show the fees. nor does decodepsbt... so using bitcoin core rpc as your HSM doesn't even provide any security improvement from having the inputs present? or am I missing it?
< jonasschnelli> kanzure: is there an issue with the bitcoin-dev mailing? I sent an email 7h, but got nothing back from the list
< sipa> gmaxwell: well, right now, the implementation in bitcoin core isn't sufficient for non-wallet operation
< gmaxwell> I understand how the bitcoin protocol works. I'm surprised that there isn't any way to bypass checking the inputs.
< rafalcpp> sipa: seems parts of his code disappeared from git? or is github acting up. following parts of that discussion re 14090 and getting into places like https://github.com/bitcoin/bitcoin/pull/14090/files/9cc9bd700e92486189695ea1cb6edafd714cb33b and github says not found
< Salve> Why does bitcoin use sha-512?
< wumpus> bountysource supports bitcoin? TIL
< wumpus> despite all the rumors about toxicity in bitcoin development we have really very little drama compared to other large projects

2018-09-02

< fanquake> wumpus If that guy (who you just banned) is going to carry on, I'm inclined to close that PR. https://github.com/bitcoin/bitcoin/pull/14090#issuecomment-417929318
< as1nc> switching to #bitcoin right now :)
< wumpus> as1nc: would be better to ask in #bitcoin, this channel is for bitcoin core development
< wumpus> bitcoin core ofc
< as1nc> wumpus, did you send the coin within bitcoin core, or another wallet ?
< as1nc> yeah i understand, but i'm bulding a service for user to accpet bitcoin via web interface providing only their extended public keys, and I really want to provide a testnet api
< as1nc> so hard to test stuff on bitcoin :)
< gribble> https://github.com/bitcoin/bitcoin/issues/14129 | Trivial: update clang thread-safety docs url by Empact · Pull Request #14129 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14090 | windows: show progress bar in task bar by alexeyneu · Pull Request #14090 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14091 | Minor style enhancement in documentation by fedsten · Pull Request #14091 · bitcoin/bitcoin · GitHub
< gmaxwell> (and before anyone things "but bitcoin traffic doesn't really need to be tamper protected" -- it's important to authenticate encrypted data or you can use targeted tampering to extract small amounts of data from encrypted links by tampering and observing what happens)
< gmaxwell> (in fact, bitcoin core computes the hash incrementaly)

2018-09-01

< gmaxwell> there should be no particular reason that someone couldn't run a fully functional bitcoin node using a few tens of MB of ram... though obviously not one with the lowest possible latency.
< gribble> https://github.com/bitcoin/bitcoin/issues/14100 | doc: Change documentation for =0 for non-boolean options by laanwj · Pull Request #14100 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14105 | util: Report parse errors in configuration file by laanwj · Pull Request #14105 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< gribble> https://github.com/bitcoin/bitcoin/issues/14121 | Index for BIP 157 block filters by jimpo · Pull Request #14121 · bitcoin/bitcoin · GitHub

2018-08-31

< gmaxwell> a long time back I did post something about bosting fingerprint comparison security via cut-and-choose: https://en.bitcoin.it/wiki/User:Gmaxwell/visual_fingerprint_comparison
< dongcarl> Have there been any thoughts put into an identicon/visual hash representation of Bitcoin addresses for improved user experience? Would that be useful in any way?

2018-08-30

< echeveria> "The receiver is responsible in making sure the "partial transaction" returned by the sender was changed correctly (it should assume the connection has been MITM'd and act accordingly), resign its original inputs and propagates this transaction over the bitcoin network. The client must be aware that the server can reorder inputs and outputs."
< gribble> https://github.com/bitcoin/bitcoin/issues/14090 | [windows] progress bar in task bar by alexeyneu · Pull Request #14090 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14089 | CryptGenRandom is deprecated by fingera · Pull Request #14089 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13878 | utils: Add fstream wrapper to allow to pass unicode filename on Windows by ken2812221 · Pull Request #13878 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< gribble> https://github.com/bitcoin/bitcoin/issues/13866 | utils: Use _wfopen and _wfreopen on Windows by ken2812221 · Pull Request #13866 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< gribble> https://github.com/bitcoin/bitcoin/issues/14019 | Import pubkeys when importing p2sh with importmulti by achow101 · Pull Request #14019 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14046 | net: Refactor message parsing (CNetMessage), adds flexibility by jonasschnelli · Pull Request #14046 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13846 | Move src/tinyformat.h to src/tinyformat/tinyformat.h by Empact · Pull Request #13846 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< gribble> https://github.com/bitcoin/bitcoin/issues/13845 | Include tinyformat as a subtree by Empact · Pull Request #13845 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< gribble> https://github.com/bitcoin/bitcoin/issues/13846 | Move src/tinyformat.h to src/tinyformat/tinyformat.h by Empact · Pull Request #13846 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14096 | Add reference documentation for descriptors language by sipa · Pull Request #14096 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14114 | scantxoutset help about descriptors refers to TODO document · Issue #14114 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< gribble> https://github.com/bitcoin/bitcoin/issues/14100 | doc: Change documentation for =0 for non-boolean options by laanwj · Pull Request #14100 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13243 | Make reusable base class for auxiliary indices by jimpo · Pull Request #13243 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13033 | Build txindex in parallel with validation by jimpo · Pull Request #13033 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14048 | 0.16.2 binary gives error after latest compiled client has run · Issue #14048 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/12391 | TODO for release notes 0.17.0 · Issue #12391 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13194 | Remove template matching and pseudo opcodes by sipa · Pull Request #13194 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14104 | 0.17.2rc issue (standardness change for bare multisig) · Issue #14104 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14109 | ibd memory usage up in 0.17 · Issue #14109 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14109 | ibd memory usage up in 0.17 · Issue #14109 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14048 | 0.16.2 binary gives error after latest compiled client has run · Issue #14048 · bitcoin/bitcoin · GitHub
< 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 provoostenator
< wumpus> midnightmagic: yes, it is, at git@github.com:zw/bitcoin-gh-meta.git
< gribble> https://github.com/bitcoin/bitcoin/issues/12391 | TODO for release notes 0.17.0 · Issue #12391 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14037 | Add README.md to linux release tarballs by hebasto · Pull Request #14037 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] practicalswift opened pull request #14108: tests: Add missing locking annotations and locks (master...mapOrphanTransactions-is-guarded-by-g_cs_orphans) https://github.com/bitcoin/bitcoin/pull/14108
< gribble> https://github.com/bitcoin/bitcoin/issues/14107 | wallet: Remove unused function GetLabelDestination by practicalswift · Pull Request #14107 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #13825: [wallet] Kill accounts (master...kill_accounts) https://github.com/bitcoin/bitcoin/pull/13825
< bitcoin-git> bitcoin/master 07033a8 Wladimir J. van der Laan: Merge #13825: [wallet] Kill accounts...
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #14107: wallet: Remove unused function GetLabelDestination (master...deadc0de) https://github.com/bitcoin/bitcoin/pull/14107
< bitcoin-git> bitcoin/master c9c32e6 John Newbery: [wallet] Kill accounts...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/6c7cfc8da68a...07033a8f9197
< bitcoin-git> [bitcoin] practicalswift opened pull request #14107: wallet: Remove unused function GetLabelDestination (master...deadc0de) https://github.com/bitcoin/bitcoin/pull/14107
< bitcoin-git> [bitcoin] ken2812221 closed pull request #13515: travis: avoid timeout without saving caches, also enable all qt (master...travis_qt) https://github.com/bitcoin/bitcoin/pull/13515
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #13126: util: Add Clang thread safety annotations for variables guarded by cs_args (master...guarded-by-cs_args) https://github.com/bitcoin/bitcoin/pull/13126
< bitcoin-git> bitcoin/master 1e29379 practicalswift: Fix potential deadlock
< bitcoin-git> bitcoin/master db5e9d3 practicalswift: Add missing locks (cs_args)
< bitcoin-git> bitcoin/master d58dc9f practicalswift: Add lock annotations (cs_args)
< bitcoin-git> [bitcoin] MarcoFalke pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/be301a577776...6c7cfc8da68a
< bitcoin-git> [bitcoin] laanwj closed pull request #14106: 0.17 (master...0.17) https://github.com/bitcoin/bitcoin/pull/14106
< bitcoin-git> [bitcoin] mkjekk opened pull request #14106: 0.17 (master...0.17) https://github.com/bitcoin/bitcoin/pull/14106
< bitcoin-git> [bitcoin] laanwj opened pull request #14105: util: Report parse errors in configuration file (master...2018_08_parse_error_reporting) https://github.com/bitcoin/bitcoin/pull/14105
< wumpus> so in my case this would be https://ci.appveyor.com/api/projects/DrahtBot/bitcoin/buildcache , hope it worked
< gribble> https://github.com/bitcoin/bitcoin/issues/14007 | tests: Run functional test on Windows by ken2812221 · Pull Request #14007 · bitcoin/bitcoin · GitHub
< wumpus> "nodebuglogfile" work at all in bitcoin.conf?
< gribble> https://github.com/bitcoin/bitcoin/issues/14100 | doc: Change documentation for =0 for non-boolean options by laanwj · Pull Request #14100 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] laanwj closed pull request #14103: docs: Fix broken Doxygen comments (master...doxygen-cleanups) https://github.com/bitcoin/bitcoin/pull/14103
< bitcoin-git> bitcoin/master be301a5 Wladimir J. van der Laan: Merge #14103: docs: Fix broken Doxygen comments...
< bitcoin-git> bitcoin/master 0e534d4 practicalswift: Fix incorrect Doxygen comments
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/4e9a6f87b7d2...be301a577776
< bitcoin-git> [bitcoin] practicalswift opened pull request #14103: Fix broken Doxygen comments (master...doxygen-cleanups) https://github.com/bitcoin/bitcoin/pull/14103
< gribble> https://github.com/bitcoin/bitcoin/issues/13825 | [wallet] Kill accounts by jnewbery · Pull Request #13825 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] fingera opened pull request #14102: export der always compressed (master...3-export-der) https://github.com/bitcoin/bitcoin/pull/14102

2018-08-29

< promag> I mean, specific to development of bitcoin-core
< promag> reza: this channel is bitcoin-core specific
< reza> I had an idea for a Bitcoin wallet, i’d like to hear your thoughts about it.
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #14083: bench: Fix thread sanitizer issue in AssembleBlock benchmark (master...Mf1808-benchAssembleBlockThread) https://github.com/bitcoin/bitcoin/pull/14083
< gribble> https://github.com/bitcoin/bitcoin/issues/14096 | Add reference documentation for descriptors language by sipa · Pull Request #14096 · bitcoin/bitcoin · GitHubAsset 1Asset 1
< jonasschnelli> there is currently an extra round for the 4bytes length: https://github.com/bitcoin/bitcoin/pull/14050/files#diff-58a94ae53d4f04a57e9dc33014a679eaR70
< sipa> that would defeat the purpose of not being recognizable as bitcoin traffic
< jonasschnelli> Also, the v2 handshake doesn't reveal "bitcoin traffic" (not very DPI resistant though)
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #14101: qa: Use named args in validation acceptance tests (master...Mf1808-qaNamedArgsAcceptance) https://github.com/bitcoin/bitcoin/pull/14101
< leishman> I added an update to the wiki with a note about the txindex db migration: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/0.17.0-Release-notes#how-to-upgrade
< bitcoin-git> [bitcoin] ryanofsky closed pull request #9381: Remove CWalletTx merging logic from AddToWallet (master...pr/atw-nomerge) https://github.com/bitcoin/bitcoin/pull/9381
< bitcoin-git> [bitcoin] laanwj closed pull request #14097: validation: Log FormatStateMessage on ConnectBlock error in ConnectTip (master...Mf1808-validationLogError) https://github.com/bitcoin/bitcoin/pull/14097
< bitcoin-git> bitcoin/master 4e9a6f8 Wladimir J. van der Laan: Merge #14097: validation: Log FormatStateMessage on ConnectBlock error in ConnectTip...
< bitcoin-git> bitcoin/master fa309dc MarcoFalke: validation: Log FormatStateMessage on ConnectBlock error in ConnectTip
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/888acefa5ee1...4e9a6f87b7d2
< bitcoin-git> [bitcoin] laanwj closed pull request #13792: tx pool: Avoid passing redundant hash into addUnchecked (scripted-diff) (master...Mf1808-constTxPoolEntries) https://github.com/bitcoin/bitcoin/pull/13792
< bitcoin-git> bitcoin/master fa58777 MarcoFalke: scripted-diff: Remove unused first argument to addUnchecked...
< bitcoin-git> bitcoin/master fe5c497 MarcoFalke: tx pool: Use the entry's hash instead of the one passed to addUnchecked
< bitcoin-git> bitcoin/master ddd395f MarcoFalke: Mark CTxMemPoolEntry members that should not be modified const
< bitcoin-git> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/1361f8babcc1...888acefa5ee1
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #14020: Add tests for RPC help (master...2018-08-test-help) https://github.com/bitcoin/bitcoin/pull/14020
< bitcoin-git> bitcoin/master 6af6d9b João Barbosa: test: Add tests for RPC help
< bitcoin-git> bitcoin/master 1361f8b MarcoFalke: Merge #14020: Add tests for RPC help...
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b0eb8f7ed43e...1361f8babcc1
< gribble> https://github.com/bitcoin/bitcoin/issues/13845 | Include tinyformat as a subtree by Empact · Pull Request #13845 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13846 | Move src/tinyformat.h to src/tinyformat/tinyformat.h by Empact · Pull Request #13846 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] laanwj closed pull request #14028: Explicitly initialize prevector _union (master...prevector-explicit-initialization) https://github.com/bitcoin/bitcoin/pull/14028
< bitcoin-git> bitcoin/master b0eb8f7 Wladimir J. van der Laan: Merge #14028: Explicitly initialize prevector _union...
< bitcoin-git> bitcoin/master 1d9aa00 Ben Woosley: Explicitly initialize prevector _union
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5924dadc2f2d...b0eb8f7ed43e
< bitcoin-git> [bitcoin] laanwj closed pull request #13671: Remove the boost/algorithm/string/case_conv.hpp dependency (master...patch/remove_boost_case_conv.hpp) https://github.com/bitcoin/bitcoin/pull/13671
< bitcoin-git> bitcoin/master b193d5a 251: Removes the Boost case_conv.hpp dependency....
< bitcoin-git> bitcoin/master 7a208d9 251: Implements custom tolower and toupper functions....
< bitcoin-git> bitcoin/master e2ba043 251: Implements ParseNetwork unit test....
< bitcoin-git> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/2ddce35abcb8...5924dadc2f2d
< bitcoin-git> [bitcoin] laanwj closed pull request #13862: utils: drop boost::interprocess::file_lock (master...custom-filelock) https://github.com/bitcoin/bitcoin/pull/13862
< bitcoin-git> bitcoin/master 2ddce35 Wladimir J. van der Laan: Merge #13862: utils: drop boost::interprocess::file_lock...
< bitcoin-git> bitcoin/master 1661a47 Chun Kuan Lee: add unicode compatible file_lock for Windows...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/13887f41f229...2ddce35abcb8
< bitcoin-git> [bitcoin] laanwj opened pull request #14100: doc: Change documentation for =0 for non-boolean options (master...2018_08_nodoc) https://github.com/bitcoin/bitcoin/pull/14100
< bitcoin-git> [bitcoin] osbc closed pull request #14099: Dev (master...dev) https://github.com/bitcoin/bitcoin/pull/14099
< bitcoin-git> [bitcoin] osbc opened pull request #14099: Dev (master...dev) https://github.com/bitcoin/bitcoin/pull/14099
< wumpus> yessss @ bitcoin-git
< bitcoin-git> [bitcoin] osbc closed pull request #14098: Dev (master...dev) https://github.com/bitcoin/bitcoin/pull/14098
< bitcoin-git> [bitcoin] osbc opened pull request #14098: Dev (master...dev) https://github.com/bitcoin/bitcoin/pull/14098
< leishman_> I see in jimpos PR here (https://github.com/bitcoin/bitcoin/pull/13033) that it was tested. What kind of migration times did others see?

2018-08-28

< gribble> https://github.com/bitcoin/bitcoin/issues/13825 | [wallet] Kill accounts by jnewbery · Pull Request #13825 · bitcoin/bitcoin · GitHub
< gmaxwell> But say, for example, we decide we want to have a HEADERS2 message coded as value 27 in bitcoin core. We're going to negoiate its activation with something like SENDHEADERS. Say another implementation BitcoinConnectUnlimitedClassic (BCUX) wants to use 27 for XHEADERS. An implementation could support talking to both kinds of peers just by assigning the meaning of 27 based on the negoation.
< waxwing> sipa, what's going on here? why would someone be adding both witness and non-witness utxo fields in the same input (bip174)? https://github.com/bitcoin/bitcoin/blob/master/src/script/sign.cpp#L256-L259
< gribble> https://github.com/bitcoin/bitcoin/issues/14087 | Remove unnecessary G_TRANSLATION_FUN nullptr assignment by promag · Pull Request #14087 · bitcoin/bitcoin · GitHub
< wumpus> (re: bitcoin P2P specifically: do we ever get *unexpected* big messages?)

2018-08-27

< jonasschnelli> gmaxwell: I can't follow your comment here: https://github.com/bitcoin/bitcoin/pull/14049#discussion_r213027446
< gribble> https://github.com/bitcoin/bitcoin/issues/13825 | [wallet] Kill accounts by jnewbery · Pull Request #13825 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/14023 | Remove accounts rpcs by jnewbery · Pull Request #14023 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/6 | Treat wallet as a generic keystore · Issue #6 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/6 | Treat wallet as a generic keystore · Issue #6 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/5 | Make the version number the protocol version and not the client version · Issue #5 · bitcoin/bitcoin · GitHub
< Jmabsd> *actually*, the hex string printer does NOT reverse the hex positions (https://github.com/bitcoin/bitcoin/blob/eb7daf4d600eeb631427c018a984a77a34aca66e/src/utilstrencodings.h#L121 - see here there's no reversing of the order of the bits in the byte) - and the reversing logic applied on the whole per-structure level is reversing byte order only, never bit order (ref. https://github.com/bitcoin/bitcoin/blob/eb7daf4d600eeb631427c018a984a77a34aca66e/sr
< Jmabsd> wait, in the Bitcoin PoW 32bit floating point structure "deserializer" at https://github.com/bitcoin/bitcoin/blob/eb7daf4d600eeb631427c018a984a77a34aca66e/src/arith_uint256.cpp#L209
< ossifrage> looking at: pmap -x $(pidof bitcoin-qt) | grep .ldb | awk '{if($3 == 0){print}}' shows that many of the ldb files aren't using any RSS memory (after being up for almost a month)

2018-08-26

< gmaxwell> in bitcoin we're seeing an increase of hundreds of meg.
< Chris_Stewart_5> jimpo: These test vectors seem to be a dead link https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki#appendix-c-test-vectors
< instagibbs> Chris_Stewart_5, merged two hours ago, didnt see that https://github.com/bitcoin/bitcoin/pull/12254
< instagibbs> Chris_Stewart_5, https://github.com/bitcoin/bitcoin/pull/13144
< gribble> https://github.com/bitcoin/bitcoin/issues/13023 | Fix some concurrency issues in ActivateBestChain() by skeees · Pull Request #13023 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13937 | Track best-possible-headers (TheBlueMatt) by Sjors · Pull Request #13937 · bitcoin/bitcoin · GitHub
< provoostenator> Any volunteer for making a PR based on this commit? https://github.com/bitcoin/bitcoin/commit/a9db3dada0119c183d16627805e90c4dbca05c6a
< luke-jr> hopefully I won't "damage" my mainnet .bitcoin trying this.. :x
< gribble> https://github.com/bitcoin/bitcoin/issues/12495 | Increase LevelDB max_open_files by eklitzke · Pull Request #12495 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/12495 | Increase LevelDB max_open_files by eklitzke · Pull Request #12495 · bitcoin/bitcoin · GitHub
< wumpus> luke-jr: the only reason that the change to num files was acceptable is because leveldb, at least the version in our tree, doesn't actually keep more files open (on platforms with mmap) see also https://github.com/bitcoin/bitcoin/pull/12495#issuecomment-377228329
< luke-jr> was there a point to https://github.com/bitcoin-core/leveldb/pull/19 considering we limit leveldb to 1000 open files anyway?

2018-08-25

< jamesob> (for those following along at home: https://github.com/bitcoin/bitcoin/pull/13925/files)
< Jmabsd> > sipa, right and when getting a disassembly printout in Bitcoin Core and related tools, those 20B:s are printed in normal order
< Jmabsd> What about pubkey hashes (20B), pubkeys (32B) and signatures (64B) - are those printed in normal or reverse byte order? so, I have a P2SH pubkey script, say. in there is a 20B hash of my redeemscript, right. when I use Bitcoin Core's script disassembly function, will it print that hash in byte or normal order? i mean there is an outer extent to what Core prints in reverse order - for instance, binary transaction dumps (in hex) are in
< Jmabsd> wait, so Bitcoin has the tendency to print (256 & 160bit) hashes in *reverse* order, right - block hashes, transaction hashes and merkle root hashes.

2018-08-24

< gribble> https://github.com/bitcoin/bitcoin/issues/2802 | Add an address-based transaction index by sipa · Pull Request #2802 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13243 | Make reusable base class for auxiliary indices by jimpo · Pull Request #13243 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/13033 | Build txindex in parallel with validation by jimpo · Pull Request #13033 · bitcoin/bitcoin · GitHub
< BlueMatt> of which there are many, any I generally dont trust most bitcoin libraries...for obvious reasons
< BlueMatt> sipa: well its either that or we have to pass a flag into signrawtransaction (and any equivalent APIs in any bitcoin library anywhere)
< BlueMatt> at least rust-bitcoin currently doesnt
< BlueMatt> and doesnt-need-to-be-backwards-compatible APIs (eg rust-bitcoin's deserializer) can *only* handle it that way
< gribble> https://github.com/bitcoin/bitcoin/issues/13033 | Build txindex in parallel with validation by jimpo · Pull Request #13033 · bitcoin/bitcoin · GitHub
< as1nc> jonasschnelli, yes but i really want to incite people to txindex their chain so they can benefit the full spectrum of bitcoin capabilities. lightning for exemple require a txindexed chain right ?