< Dizzle> ty
< Dizzle> happy holidays, devs
< luke-jr> sipa: it could change in the future
< gmaxwell> sipa: I think we're more likely to remove GBT entirely in favor of e.g. Betterhash (which always knows the coinbase size exactly when it makes the template) than significantly change how GBT works relative to space reserved.
< gmaxwell> er luke-jr ^
< bitcoin-git> [bitcoin] laanwj opened pull request #15033: doc: Add historical release notes for 0.17.1 (master...2018_12_relnot_0.17.1) https://github.com/bitcoin/bitcoin/pull/15033
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to 0.17: https://github.com/bitcoin/bitcoin/commit/fd616d8d08c61daf13671fbb744c74eb23980901
< bitcoin-git> bitcoin/0.17 fd616d8 Wladimir J. van der Laan: doc: Clean out release notes post-0.17.1...
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f8a3ab3b29fe...df73c23f5fac
< bitcoin-git> bitcoin/master 488563e Wladimir J. van der Laan: doc: Add historical release notes for 0.17.1
< bitcoin-git> bitcoin/master df73c23 Wladimir J. van der Laan: Merge #15033: doc: Add historical release notes for 0.17.1...
< bitcoin-git> [bitcoin] laanwj closed pull request #15033: doc: Add historical release notes for 0.17.1 (master...2018_12_relnot_0.17.1) https://github.com/bitcoin/bitcoin/pull/15033
< gmaxwell> \O/ Merry christmas.
< wumpus> \o/
< meshcollider> Merry Christmas :D
< Guest14218> I just want to drop two ideas here, what would make a difference in the future of bitcoin and crypto in general. 1. Solving real world problems through mining, like miners being tied to BOINC projects, so all the computing power is put to good use. 2. Wallets with AI budgeting, that takes care of your money for you, learns your expenses, auto-allocates budgets for economies, has investment schemes for low, medium and hig
< Guest14218> These 2 will give bitcoin and crypto the edge it needs over banks.
< sipa> Guest14218: try #bitcoin or bitcoin.stackexchange.com
< Guest14218> thanks
< jimmysong> question about neutrino: is there a way to get the input script pubkeys with a network message?
< jimmysong> if not, would it make sense to make those available with the block download to make sure the filter hash matches?
< jimmysong> the client can also validate the script part of every transaction input
< jimmysong> this is getting input script pubkeys for all the transactions for a given block
< andytoshi> is there a url for the optech "cpfp best practices"
< achow101> andytoshi: I don't think that exists yet, but when it does, it should be here: https://github.com/bitcoinops/scaling-book/blob/master/1.fee_bumping/fee_bumping.md#child-pays-for-parent
< harding> jimmysong: when a node is validating a newly received block, it gets the prevout scripts (what I think you're calling input script pubkeys) from its utxo set. After the block has be verified, the now-spent UTXOs are purged from the set and the node no longer has fast access to them, so it can't provide the info you want. Furthermore, for a third party to verify that the prevout hasn't been tampered requires getting the whole
< harding> transaction that contained that prevout to check its txid against the outpoint (txid:vout). Since the max size of a tx is almost the max size of a block, that means you might need to download data equal to as many blocks as a block can have inputs (~16,000 maybe, times 4MB, or ~64GB), making this method impractical in pathological cases.
< jimmysong> i guess i have to wait for a cfilter coinbase commitment then?
< jimmysong> it would be nice to be able to verify a specific hash
< jimmysong> though now that i think about it, you're not giving away much info by requesting *every* transaction from the inputs to a block
< jimmysong> anyway, harding, there's no chance of putting that data in some sort of block store, is there?