< bitcoin-git>
[bitcoin] sipa opened pull request #13393: Enable double-SHA256-for-64-byte code on 32-bit x86 (master...201806_dsha256_i386) https://github.com/bitcoin/bitcoin/pull/13393
< wumpus>
cfields: seems it indeed passes in a severity, so it's possible to distinguish. I think it's fine to drop warnings for bitcoin-cli.
< wumpus>
cfields: we don't set up a logger at all in bitcoin-cli
< bitcoin-git>
[bitcoin] ken2812221 reopened pull request #13390: Tests: Ignore RemoteDisconnected and BadStatusLine when stopping node (master...stop_node) https://github.com/bitcoin/bitcoin/pull/13390
< bitcoin-git>
[bitcoin] ken2812221 closed pull request #13390: Tests: Ignore RemoteDisconnected and BadStatusLine when stopping node (master...stop_node) https://github.com/bitcoin/bitcoin/pull/13390
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13392: util: Make strprintf noexcept. Improve error message on format string error. (master...strprintf-noexcept) https://github.com/bitcoin/bitcoin/pull/13392
< jnewbery>
promag: seems like the bitcoin-cli stderr is not matching the expected string. See test_node.py L370. I suggest you put a breakpoint in there and see what cli_stderr is set to
< bitcoin-git>
[bitcoin] practicalswift closed pull request #13391: Make tinyformat noexcept: Use default error handling (assert(0 && reason)) on incorrect format strings (master...non-throwing-tinyformat) https://github.com/bitcoin/bitcoin/pull/13391
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13391: Make tinyformat noexcept: Use default error handling (assert(0 && reason)) on incorrect format strings (master...non-throwing-tinyformat) https://github.com/bitcoin/bitcoin/pull/13391
< bitcoin-git>
[bitcoin] ken2812221 opened pull request #13390: Tests: Ignore RemoteDisconnected and BadStatusLine when stopping node (master...stop_node) https://github.com/bitcoin/bitcoin/pull/13390
< wumpus>
"subprocess.CalledProcessError: Command '/Users/joao/Projects/bitcoin/src/bitcoin-cli' returned non-zero exit status 18."
< bitcoin-git>
[bitcoin] laanwj closed pull request #13191: Specialized double-SHA256 with 64 byte inputs with SSE4.1 and AVX2 (master...201709_dsha256_64) https://github.com/bitcoin/bitcoin/pull/13191
< bitcoin-git>
[bitcoin] laanwj closed pull request #13383: bench: Use non-throwing ParseDouble(...) instead of throwing boost::lexical_cast<double>(...) (master...remove-dependency-on-lexical_cast-which-is-boost-and-also-throws) https://github.com/bitcoin/bitcoin/pull/13383
< bitcoin-git>
bitcoin/master 2722a1f Wladimir J. van der Laan: Merge #13383: bench: Use non-throwing ParseDouble(...) instead of throwing boost::lexical_cast<double>(...)...
< bitcoin-git>
bitcoin/master f41d339 practicalswift: bench: Use non-throwing ParseDouble(...) instead of throwing boost::lexical_cast<double>(...)
< bitcoin-git>
[bitcoin] n2yen opened pull request #13389: Utils and libraries: Fix #13371 - move umask operation earlier in AppInit() (master...13371) https://github.com/bitcoin/bitcoin/pull/13389
< bitcoin-git>
[bitcoin] qmma70 opened pull request #13388: util: Implement boolean conversion and !operator for uint_* (master...uint_bool) https://github.com/bitcoin/bitcoin/pull/13388
< bitcoin-git>
[bitcoin] yuntai closed pull request #13365: RPC/REST/ZMQ, Wallet: Set label with importprivkey only requested (master...master) https://github.com/bitcoin/bitcoin/pull/13365
2018-06-03
< bitcoin-git>
[bitcoin] sipa opened pull request #13386: SHA256 implementations based on Intel SHA Extensions (master...201806_shani) https://github.com/bitcoin/bitcoin/pull/13386
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13385: build: Guard against accidental introduction of new Boost dependencies (master...lint-boost) https://github.com/bitcoin/bitcoin/pull/13385
< jonasschnelli>
Bech32 is currently available in most (all?) modern bitcoin software and a support of the bech32 keys proposal would be simple to implement
< sipa>
jonasschnelli: if you want a way to represent the current bitcoin core behaviour, it also needs P2PK
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #13384: qa: Remove polling loop from test_runner (master...Mf1806-qaTestRunnerConcurrentFuture) https://github.com/bitcoin/bitcoin/pull/13384
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13383: bench: Use non-throwing ParseDouble(...) instead of throwing boost::lexical_cast<double>(...) (master...remove-dependency-on-lexical_cast-which-is-boost-and-also-throws) https://github.com/bitcoin/bitcoin/pull/13383
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13382: util: Don't throw in GetTime{Millis,Micros}(). Mark as noexcept. (master...dont-throw-in-GetTimeMillis-and-GetTimeMicros) https://github.com/bitcoin/bitcoin/pull/13382
< bitcoin-git>
[bitcoin] marcoagner opened pull request #13381: [WIP] RPC: creates preserve parameter for importprivkey call (master...feature_preserve_labels_on_import) https://github.com/bitcoin/bitcoin/pull/13381
< jonasschnelli>
A4L be more specific in your question and use #bitcoin-dev (this channel is for Bitcoin Core development)
< A4L>
Php/python/linux bash: send.bitcoin(privatekey, publickey, amount); how to??
2018-06-02
< bitcoin-git>
[bitcoin] undercoverGod opened pull request #13375: utils and libraries: address check in update-translations.py (master...master) https://github.com/bitcoin/bitcoin/pull/13375
< bitcoin-git>
[bitcoin] kaplanmaxe opened pull request #13374: utils and libraries: checking for bitcoin address in translations (master...check-addr-translations) https://github.com/bitcoin/bitcoin/pull/13374
< bitcoin-git>
[bitcoin] eudisd opened pull request #13373: Qt: Update Wallet Encryption Titles To Better Describe Process (master...feature/bitcoin-#13245) https://github.com/bitcoin/bitcoin/pull/13373
< bitcoin-git>
[bitcoin] steverusso opened pull request #13372: Docs: Linked to 'Building on FreeBSD' in build-unix.md (master...link-to-building-on-freebsd) https://github.com/bitcoin/bitcoin/pull/13372
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #13367: qa: Increase includeconf test coverage (master...Mf1806-qaIncludeconf) https://github.com/bitcoin/bitcoin/pull/13367
< gmaxwell>
Beyond node-flavors for striping, another thing we might want more payload for is alternative ports for other transports. E.g. if later we define a bitcoin-over-udp we might want to signal the ports for that instead of sending two addr messages for the two endpoints. I'm not currently remembering any other service flag things where we've wanted other payload.
< bitcoin-git>
[bitcoin] giulio92 opened pull request #13366: Docs: Rename “OS X” to the newer “macOS” convention (master...osx-renaming) https://github.com/bitcoin/bitcoin/pull/13366
< bitcoin-git>
[bitcoin] yuntai opened pull request #13365: RPC/REST/ZMQ: Set label with importprivkey only requested. #13087 (master...master) https://github.com/bitcoin/bitcoin/pull/13365
< gribble>
https://github.com/bitcoin/bitcoin/issues/13294 | Fix compiler warnings emitted when compiling under stock OpenBSD 6.3 by practicalswift · Pull Request #13294 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] laanwj closed pull request #13355: Fix "gmake check" under OpenBSD 6.3 (probably *BSD): Avoid using GNU grep specific regexp handling (master...openbsd-gmake-check) https://github.com/bitcoin/bitcoin/pull/13355
< bitcoin-git>
bitcoin/master 0b1c0c4 Wladimir J. van der Laan: Merge #13355: Fix "gmake check" under OpenBSD 6.3 (probably *BSD): Avoid using GNU grep specific regexp handling...
< bitcoin-git>
bitcoin/master db56755 practicalswift: Fix "gmake check" under OpenBSD 6.3 (probably *BSD): Avoid using GNU grep specific regexp handling
< gribble>
https://github.com/bitcoin/bitcoin/issues/13355 | Fix "gmake check" under OpenBSD 6.3 (probably *BSD): Avoid using GNU grep specific regexp handling by practicalswift · Pull Request #13355 · bitcoin/bitcoin · GitHub
< kallewoof>
mryandao: Yeah, so even if RHEL 8 was released with C++14 support it wouldn't really matter cause its users would be running bitcoin core 0.3 or something, anyway...
< mryandao>
enterprise would be running the oldest version of bitcoin possible
< kallewoof>
I'm a bit surprised at the concerns with people running distros from 2007 not being able to run the latest & greatest version of bitcoin core. Does such a person actually exist?
< 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] jl2012 opened pull request #13360: [Policy] Reject SIGHASH_SINGLE with output out of bound (master...insecure_single) https://github.com/bitcoin/bitcoin/pull/13360
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #13359: wallet: Directly operate with CMutableTransaction (master...Mf1806-avoidTxConstuctor) https://github.com/bitcoin/bitcoin/pull/13359
< bitcoin-git>
[bitcoin] jl2012 opened pull request #13357: Accurately determine the use of SIGHASH_SINGLE in signing (master...signsingle) https://github.com/bitcoin/bitcoin/pull/13357
< bitcoin-git>
[bitcoin] practicalswift opened pull request #13355: Fix "gmake check" under OpenBSD 6.3 (probably *BSD): Avoid using GNU grep specific regexp handling (master...openbsd-gmake-check) https://github.com/bitcoin/bitcoin/pull/13355
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #13351: wallet: Prevent segfault when sending to unspendable witness (master...Mf1806-walletUnspendableWitnessIsMine) https://github.com/bitcoin/bitcoin/pull/13351
< bitcoin-git>
[bitcoin] lmanners opened pull request #13350: [tests] Add logging to provide anchor points when debugging failures. (master...testlogging) https://github.com/bitcoin/bitcoin/pull/13350
<@wumpus>
blocked from bitcoin and bitcoin-core orgs
< Arvidt>
The release notes for 0.16.1rc1 linked in the announcement email is pretty empty / in draft state (e.g. "0.16.x Example item"). I think it would be interesting for someone considering running RC version to have an overview what's new. https://github.com/bitcoin/bitcoin/blob/0.16/doc/release-notes.md
< bitcoin-git>
[bitcoin] achow101 closed pull request #13289: [Qt] Re-setup args after translator setup to translate help text (master...qt-help-translations) https://github.com/bitcoin/bitcoin/pull/13289
< bitcoin-git>
[bitcoin] promag opened pull request #13339: wallet: Replace %w by wallet name in -walletnotify script (master...2018-05-walletnotify) https://github.com/bitcoin/bitcoin/pull/13339
< bitcoin-git>
[bitcoin] laanwj closed pull request #13134: net: Add option `-enablebip61` to configure sending of BIP61 notifications (master...2018_05_optional_bip61) https://github.com/bitcoin/bitcoin/pull/13134
< bitcoin-git>
bitcoin/master 87fe292 Wladimir J. van der Laan: doc: Mention disabling BIP61 in bips.md
< bitcoin-git>
bitcoin/master 70d3541 Wladimir J. van der Laan: Merge #13134: net: Add option `-enablebip61` to configure sending of BIP61 notifications...
< bitcoin-git>
bitcoin/master fe16dd8 Wladimir J. van der Laan: net: Add option `-enablebip61` to configure sending of BIP61 notifications...
< wumpus>
even if you don't care about "use of Bitcoin Core as wallet" (like Trezor), it seems that other wallets would benefit from the same
< wumpus>
I've always been surprised how little the hardware wallets vendors care about this, they just carve out their little space with their own proprietary protocols and software, instead of starting some bitcoin HSM working group
< wumpus>
< mryandao> sounds like the painpoints alone warrant a workshop on integration of HSMs with Bitcoin <- I agree, it's something that could use more concentrated effort
< mryandao>
sounds like the painpoints alone warrant a workshop on integration of HSMs with Bitcoin
< wumpus>
we're not going to do low-level USB stuff in bitcoin core
< wumpus>
(simply "gpg2 bitcoin-win-0.16-build.assert.gpg" in your 0.16.1rc1 directory should do it)
< wumpus>
rm bitcoin-win-0.16-build.assert.sig && gpg2 --detach-sign bitcoin-win-0.16-build.assert or something like that
< bitcoin-git>
[bitcoin] laanwj closed pull request #13275: Qt: use [default wallet] as name for wallet with no name (master...2018/05/loadwallet_gui_name) https://github.com/bitcoin/bitcoin/pull/13275
< bitcoin-git>
bitcoin/master a315b79 Wladimir J. van der Laan: Merge #13275: Qt: use [default wallet] as name for wallet with no name...
< bitcoin-git>
bitcoin/master 2885c13 Jonas Schnelli: Qt: use [default wallet] as name for wallet with no name
< gribble>
https://github.com/bitcoin/bitcoin/issues/11658 | During IBD, when doing pruning, prune 10% extra to avoid pruning again soon after by luke-jr · Pull Request #11658 · bitcoin/bitcoin · GitHub
< mryandao>
oh, i just did an update today and it pains me to need to install that 100MB+ of libboost to compile bitcoin-core
2018-05-27
< jhfrontz>
Anyone know of a specific distro/release that supports the Gitian build of bitcoin core?
< jhfrontz>
So I re-installed Ubuntu 14.04.5 LTS and tried to do a Gitian build of Bitcoin Core. gitian-build.sh has the same issue as on Ubuntu 18.04 — it is trying to make some sort of modifications to /etc/sudoers (via dpkg) and is requesting an interactive resolution to a conflict — but that fails (presumably because stdin is internally redirected to /dev/null?).
< bitcoin-git>
[bitcoin] kallewoof closed pull request #12869: BIP-178: Extend WIF format with key type (master...importmulti-wif-extended) https://github.com/bitcoin/bitcoin/pull/12869
< bitcoin-git>
[bitcoin] glaksmono opened pull request #13322: Fixing texts in the "encrypt wallet" GUI process (master...bitcoin-gui-13245) https://github.com/bitcoin/bitcoin/pull/13322
< bitcoin-git>
[bitcoin] glaksmono closed pull request #13321: Fixing texts in the "encrypt wallet" GUI process (master...bitcoin-13245) https://github.com/bitcoin/bitcoin/pull/13321
< bitcoin-git>
[bitcoin] glaksmono opened pull request #13321: Fixing texts in the "encrypt wallet" GUI process (master...bitcoin-13245) https://github.com/bitcoin/bitcoin/pull/13321
< jhfrontz>
I'm trying to do a Gitian build of Bitcoin Core on a stock (just installed from a liveUSB) Ubuntu 18.04 distro using the instructions at https://github.com/bitcoin-core/docs/blob/master/gitian-building.md#initial-gitian-setup . I keep running into situations where gitian-build.sh (or one of the scripts it calls) need to do some sort of interactive edits (e.g.., asking for confirmation on a package installation/customization