< echeveria>
similar to Travis, building Bitcoin Core, I men’s.
< echeveria>
they run mostly alright for this sort of target. I know a developer that has a dedicated Mac Mini build server for their binary distribution in a similar way to bitcoin core.
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #15247: qa: Use wallet to retrieve raw transactions (master...Mf1901-qaWalletRaw) https://github.com/bitcoin/bitcoin/pull/15247
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #15246: qa: Add tests for invalid message headers (master...Mf1901-qaMsgHeader) https://github.com/bitcoin/bitcoin/pull/15246
< bitcoin-git>
[bitcoin] instagibbs opened pull request #15245: remove deprecated mentions of signrawtransaction from fundraw help (master...fundraw_signraw) https://github.com/bitcoin/bitcoin/pull/15245
< gmaxwell>
I think it would be nice to even do more than what Bitcoin Core currently does.. but priorities, the sign/verify after generate is a pretty general protection at least.
< provoostenator>
Even devices that don't have an official sign message feature, Bitcoin Core could just have it sign a fake transaction.
< provoostenator>
"internally to bitcoin core is sign-after-generate" - I didn't know we did that, that seems smart.
< gmaxwell>
right. Well we can only go so far too. :) But the standard we've set internally to bitcoin core is sign-after-generate.
< gmaxwell>
Which is analogous to the process bitcoin uses internally when generating keys: it signs a message and verifies, to make sure that the generated address/key actually work.
< gmaxwell>
Corruption inside bitcoin is also a concern, but a strictly less serious one than corruption by humans or across application boundaries.
< provoostenator>
So we need something to replace xpub that has a better checksum? Or does that still data corruption risk? Because something goes wrong inside of Bitcoin Core during the import?
< gribble>
https://github.com/bitcoin/bitcoin/issues/14075 | Import watch only pubkeys to the keypool if private keys are disabled by achow101 · Pull Request #14075 · bitcoin/bitcoin · GitHub
< jnewbery>
2. We're looking for recommendations for residents. If you know anyone who wants to immerse themselves in Bitcoin/Lightning over summer and is excited about making a real contribution to the project, please send them our way
< jnewbery>
it's 2-3 weeks of seminars followed by 2 months of project work. We're expecting the residents to make really meaningful contributions to Bitcoin Core and other Bitcoin/Lightning projects while they're here
< gribble>
https://github.com/bitcoin/bitcoin/issues/15225 | GUI: Change the receive button to respond to keypool state changing by achow101 · Pull Request #15225 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/15225 | GUI: Change the receive button to respond to keypool state changing by achow101 · Pull Request #15225 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] instagibbs opened pull request #15244: gdb attaching to process during tests has non-sudo solution (master...gdb_ptrace) https://github.com/bitcoin/bitcoin/pull/15244
< gribble>
https://github.com/bitcoin/bitcoin/issues/15225 | GUI: Change the receive button to respond to keypool state changing by achow101 · Pull Request #15225 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] laanwj closed pull request #15223: Doc: add information about security to the JSON-RPC doc (master...2019-01-rpc-security) https://github.com/bitcoin/bitcoin/pull/15223
< luke-jr>
bitcoin-0.17.1/bin/bitcoin-qt: relocation error: bitcoin-0.17.1/bin/bitcoin-qt: symbol __chk_fail, version GLIBC_2.3.4 not defined in file libc.so.6 with link time reference
< bitcoin-git>
[bitcoin] jonasschnelli closed pull request #15196: [test]: Update all subprocess.check_output functions to be Python 3.4 compatible (master...cron-ci-fix) https://github.com/bitcoin/bitcoin/pull/15196
< bitcoin-git>
bitcoin/master fdf82ba Graham Krizek: Update all subprocess.check_output functions in CI scripts to be Python 3.4 compatible...
< bitcoin-git>
bitcoin/master 73a6bac Jonas Schnelli: Merge #15196: [test]: Update all subprocess.check_output functions to be Python 3.4 compatible...
< gribble>
https://github.com/bitcoin/bitcoin/issues/15196 | [test]: Update all subprocess.check_output functions to be Python 3.4 compatible by gkrizek · Pull Request #15196 · bitcoin/bitcoin · GitHub
< ryanofsky>
i know specifying --prefix lets bitcoin autoconf find the "config.site" file generated by depends
< dongcarl>
Question for people more knowledgeable about depends: in depends/README.md, it says that the way to use the results of calling `make` in depends for bitcoin is to do ./configure --prefix=`pwd`/depends/x86_64-w64-mingw32, but in our gitian descriptor we seem to use it like so: CONFIG_SITE=`pwd`/depends/x86_64-w64-mingw32/share/config.site ./configure --prefix=/. Is there a difference between the two?
< bitcoin-git>
[bitcoin] hebasto opened pull request #15236: scripts and tools: Make --setup command independent (master...20190123-gitian-build-setup) https://github.com/bitcoin/bitcoin/pull/15236
< bitcoin-git>
[bitcoin] ken2812221 reopened pull request #14922: [WIP] windows: Set _WIN32_WINNT to 0x0601 (Windows 7) (master...patch-1) https://github.com/bitcoin/bitcoin/pull/14922
< bitcoin-git>
[bitcoin] achow101 opened pull request #15235: Do not import private keys to wallets with private keys disabled (master...fix-noprivs-import) https://github.com/bitcoin/bitcoin/pull/15235
< bitcoin-git>
bitcoin/master 94167e2 Wladimir J. van der Laan: Merge #15208: Qt: remove macOS launch-at-startup when compiled with > macOS 10.11, fix memory missmanagement...
< wumpus>
hm "2019-01-22 22:23:51 [ghi] Received repository 'bitcoin/bitcoin', but no pool is configured for it."
< gkrizek>
wumpus is the bitcoin-git Nick registered (ie; needs a password)?
< wumpus>
gkrizek: I've removed the github service from #bitcoin-commits, right setting up an account on my server to run ghi, and sure an example could be helpful :)
< gkrizek>
I was thinking it might be nice to add it as a webhook now and have it post to the #bitcoin-commits channel. That way we can test it out and see how it compares to the GitHub Service before it's EOL.
< meshcollider>
jonasschnelli: weird, in your github settings on the Authorized OAuth Apps page, does AppVeyor have access to read org and team membership, and the bitcoin org?
< bitcoin-git>
[bitcoin] achow101 opened pull request #15225: GUI: Change the receive button to respond to keypool state changing (master...receive-button) https://github.com/bitcoin/bitcoin/pull/15225
< bitcoin-git>
[bitcoin] sipa opened pull request #15224: Add RNG strengthening (10ms once every minute) (master...201901_rand_strengthen) https://github.com/bitcoin/bitcoin/pull/15224
< bitcoin-git>
[bitcoin] harding opened pull request #15223: Doc: add information about security to the JSON-RPC doc (master...2019-01-rpc-security) https://github.com/bitcoin/bitcoin/pull/15223
< bitcoin-git>
bitcoin/master f0c9e1c Wladimir J. van der Laan: Merge #14906: refactor: Make explicit CMutableTransaction -> CTransaction conversion....
< bitcoin-git>
bitcoin/master 6be52d6 Wladimir J. van der Laan: Merge #15213: doc: Remove errant paste from walletcreatefundedpsbt for nLocktime replaceable...
< bitcoin-git>
[bitcoin] laanwj closed pull request #15213: doc: Remove errant paste from walletcreatefundedpsbt for nLocktime replaceable (master...wcfpsbt_paste_err) https://github.com/bitcoin/bitcoin/pull/15213
< bitcoin-git>
bitcoin/master 85f0ca9 Gregory Sanders: Remove errant past from walletcreatefundedpsbt for nLocktime replaceability
< gribble>
https://github.com/bitcoin/bitcoin/issues/15196 | [test]: Update all subprocess.check_output functions to be Python 3.4 compatible by gkrizek · Pull Request #15196 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] laanwj closed pull request #15209: zmq: log outbound message high water mark when reusing socket (master...zmq-always-log-high-water-mark) https://github.com/bitcoin/bitcoin/pull/15209
< bitcoin-git>
[bitcoin] hebasto opened pull request #15217: Wallet: Remove "-Wunused-variable" warning while build with "--disable-wallet" option (master...20190120-unused-variable-warning) https://github.com/bitcoin/bitcoin/pull/15217
< bitcoin-git>
[bitcoin] hebasto opened pull request #15216: Scripts and tools: Replace script name with a special parameter (master...20190120-improve-shell-ux) https://github.com/bitcoin/bitcoin/pull/15216
< bitcoin-git>
bitcoin/master 978682b Wladimir J. van der Laan: Merge #15194: Add comment describing fDisconnect behavior...
< bitcoin-git>
[bitcoin] practicalswift opened pull request #15215: rpc: Use the return value of GetProxy(...) in GetNetworksInfo(). Mark GetProxy(...) with [[nodiscard]]. (master...getnetworkinfo-getproxy) https://github.com/bitcoin/bitcoin/pull/15215
< bitcoin-git>
[bitcoin] practicalswift opened pull request #15214: Improve tests by checking for expected return values (master...check-return-values-in-tests) https://github.com/bitcoin/bitcoin/pull/15214
< bitcoin-git>
[bitcoin] instagibbs opened pull request #15213: Remove errant past from walletcreatefundedpsbt for nLocktime replaceable (master...wcfpsbt_paste_err) https://github.com/bitcoin/bitcoin/pull/15213
< bitcoin-git>
[bitcoin] instagibbs closed pull request #15212: Remove errant paste from walletcreatefundedpsbt meant for replaceable (master...wcfpsbt_paste_err) https://github.com/bitcoin/bitcoin/pull/15212
< bitcoin-git>
[bitcoin] instagibbs opened pull request #15212: Remove errant paste from walletcreatefundedpsbt meant for replaceable (master...wcfpsbt_paste_err) https://github.com/bitcoin/bitcoin/pull/15212
< booyah>
and have compiler(s) compiler bitcoin into that IR, and have identical IR from them
< dongcarl>
fanquake: For the part of completing reproducible builds of bitcoin with guix, I might write up some instrucitons to do so when I sort out the current sources of non-determinism (I think qt is the culprit right now)
< bitcoin-git>
[bitcoin] fanquake opened pull request #15209: zmq: log outbound message high water mark when reusing socket (master...zmq-always-log-high-water-mark) https://github.com/bitcoin/bitcoin/pull/15209
< bitcoin-git>
bitcoin/master fe60ee9 Wladimir J. van der Laan: Merge #15186: rpc: remove duplicate solvable field from getaddressinfo...
< bitcoin-git>
[bitcoin] laanwj closed pull request #15186: rpc: remove duplicate solvable field from getaddressinfo (master...duplicate-solvable-fields) https://github.com/bitcoin/bitcoin/pull/15186
< dufferzafar>
okay, is it bitcoin-help? i saw this channel mentioned on slack, so came here
< wumpus>
it's fine as long as you don't go arguing how bitcoin's P2P protocol works...
< wumpus>
I think you need to read up on how your tooling is used with other TCP protocols, it's not really different for bitcoin
< dufferzafar>
so, the ports 12192 & 12476 are the ones the two bitcoin processes (btc1 & btc2) are listening on
< dufferzafar>
i'm doing some network measurement experiments on bitcoin
< dufferzafar>
i have bitcoin daemons running on multiple machines
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #15197: Refactor and slightly stricter p2p message processing (master...2019/01/netmsg_1) https://github.com/bitcoin/bitcoin/pull/15197
< luke-jr>
Alixe: this is not "talk to devs", it is "talk about development", and your question is not about development. some of us are in #bitcoin too
< sipa>
#bitcoin
< Alixe>
So I think mining hash power can't do anything because full nodes enforce consensus rules. But some people think governments or corporates can buy a lot of nodes to affect Bitcoin with having majority of full nodes. Is it possible?
< bitcoin-git>
[bitcoin] gkrizek opened pull request #15196: Update all subprocess.check_output functions to be Python 3.4 compatible (master...cron-ci-fix) https://github.com/bitcoin/bitcoin/pull/15196
< gwillen>
just replacing it with some kind of simple fixed notice with a pointer to the COPYING file, without varying years or names other than "the Bitcoin developers" or what have you
< bitcoin-git>
[bitcoin] practicalswift opened pull request #15191: validation: Add missing cs_LastBlockFile locks in PruneAndFlush() and UnloadBlockIndex(). Add missing locking annotation for nLastBlockFile and fCheckForPruning. (master...cs_LastBlockFile) https://github.com/bitcoin/bitcoin/pull/15191
< sipa>
gwillen: IANAL but i believe those copyright statements per file (and much less the year indications) are almost certainly worthless, especially when attributing to "The Bitcoin Core developers", which is not a legal entity
< bitcoin-git>
[bitcoin] practicalswift opened pull request #15187: fees: Complete the removal of fee-estimation file read code for old versions (master...fee-estimation) https://github.com/bitcoin/bitcoin/pull/15187