< bitcoin-git>
[bitcoin] laanwj closed pull request #12119: [wallet] use P2WPKH change output if any destination is P2WPKH or P2WSH (master...bech32-change) https://github.com/bitcoin/bitcoin/pull/12119
< bitcoin-git>
bitcoin/master 9594139 Wladimir J. van der Laan: Merge #12119: [wallet] use P2WPKH change output if any destination is P2WPKH or P2WSH...
< bitcoin-git>
bitcoin/master 596c446 Sjors Provoost: [wallet] use P2WPKH change output if any destination is P2WPKH or P2WSH...
< Randolf>
ProfMac: There is a #bitcoin-dev channel.
< bitcoin-git>
[bitcoin] kallewoof opened pull request #12257: [wallet] Use destination groups instead of coins in coin select (master...feature-addrgrouped-coinselect) https://github.com/bitcoin/bitcoin/pull/12257
< jojeyh>
hey trying to setup private regtest chain locally. running the command 'bitcoind -regtest -daemon' outputs usual phrase 'Bitcoin server starting.." but 'ps aux' returns no process running it
< bitcoin-git>
[bitcoin] ajtowns opened pull request #12252: Require all tests to follow naming convention (master...rename_tests_no_leeway) https://github.com/bitcoin/bitcoin/pull/12252
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #12251: initwallet: Do not translate highly technical addresstype help (master...Mf1801-walletNoTranslateInitHelp) https://github.com/bitcoin/bitcoin/pull/12251
< bitcoin-git>
[bitcoin] luke-jr opened pull request #12246: Bugfix: Only run bitcoin-tx tests when bitcoin-tx is enabled (master...separate_utils) https://github.com/bitcoin/bitcoin/pull/12246
< zelest>
I think I just had a quite clever idea... What about showing bitcoin addresses in certain colors? E.g, convert it to hex and pick the 6 values (like, 2 form the beginning, 2 from the middle, 2 from the last) and use it as RGB and color it..
< bitcoin-git>
[bitcoin] fanquake opened pull request #12241: [trivial][docs] Fix incorrect link in /test/ README.md (master...trivial-fix-util-link) https://github.com/bitcoin/bitcoin/pull/12241
< bitcoin-git>
[bitcoin] mryandao opened pull request #12240: changed fee to be in sats instead of btc (master...fix-getrawmempool-fee-representation) https://github.com/bitcoin/bitcoin/pull/12240
< gribble>
https://github.com/bitcoin/bitcoin/issues/12119 | [wallet] use P2WPKH change output if any destination is P2WPKH or P2WSH by Sjors · Pull Request #12119 · bitcoin/bitcoin · GitHub
2018-01-19
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #12231: rpc: Avoid KeyError in getpeerinfo bytes per msg (master...Mf1801-rpcPeerInfoKeyError) https://github.com/bitcoin/bitcoin/pull/12231
< bitcoin-git>
[bitcoin] mmgen closed pull request #12228: Allow wallet file to be a symlink, as was the case before v0.15.0 (master...wallet_symlink) https://github.com/bitcoin/bitcoin/pull/12228
< bitcoin-git>
[bitcoin] mmgen opened pull request #12228: Allow wallet file to be a symlink, as was the case before v0.15.0 (master...wallet_symlink) https://github.com/bitcoin/bitcoin/pull/12228
< bitcoin-git>
[bitcoin] ryanofsky opened pull request #12227: test_runner: Readable output if create_cache.py fails (master...pr/runcache) https://github.com/bitcoin/bitcoin/pull/12227
< wumpus>
jonasschnelli: I would have been ok with relative paths if they meant 'relative to datadir' as other relative paths in our options, but relative to current directory isn't really acceptable, that's simply a recipe for confusion, especially if provided in bitcoin.conf
< provoostenator>
On the nightly Ubuntu 18.04 build `sudo add-apt-repository ppa:bitcoin/bitcoin && sudo apt-get update` complains:
< instagibbs>
almost #bitcoin but not quite: in master is there any way to back out legacy addresses from (p2sh)-p2wpkh addresses from -cli or elsewhere?
< jojeyh>
in file "bitcoin/src/support/allocators/zeroafterfree.h"
< bitcoin-git>
[bitcoin] ryanofsky opened pull request #12211: Avoid potential null dereference in ReceiveCoinsDialog constructor (master...pr/nullrecv) https://github.com/bitcoin/bitcoin/pull/12211
< instagibbs>
Pritty_Kitty, this isn't a question for Bitcoin Core development though. maybe #bitcoin-dev
< Pritty_Kitty>
No no i am a developer asking technical questions about bitcoin. I have built php code to deserialize transactions and build a merkle tree. Now i am working on the witness tree.
< Randolf>
Pritty_Kitty: You seem to be asking a "how to use Bitcoin" type of question. You'll likely find that such questions are better suited for the #bitcoin channel as this one you're asking in now is specifically focused on Bitcoin core software development.
< sipa>
#bitcoin may be a better place
< meshcollider>
UnderDog_: I think you might be in the wrong channel, maybe try #bitcoin for general discussion on it, this channel is just for bitcoin core development
< gribble>
https://github.com/bitcoin/bitcoin/issues/12208 | GUI: Rephrase Bech32 checkbox texts, and enable it with legacy address default by luke-jr · Pull Request #12208 · bitcoin/bitcoin · GitHub
< jonasschnelli>
<bitcoin-git>[bitcoin] luke-jr opened pull request #12208: GUI: Rephrase Bech32 checkbox texts, and enable it with legacy address default
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #12177: trivial: fix address_type help text of getnewaddress and getrawchangeaddress (master...trivial1) https://github.com/bitcoin/bitcoin/pull/12177
< bitcoin-git>
bitcoin/master cad504b MarcoFalke: Merge #12177: trivial: fix address_type help text of getnewaddress and getrawchangeaddress...
< bitcoin-git>
bitcoin/master 5f911c5 mruddy: trivial: fix address_type help text of getnewaddress and getrawchangeaddress
< gribble>
https://github.com/bitcoin/bitcoin/issues/12119 | [wallet] use P2WPKH change output if any destination is P2WPKH or P2SH-P2WSH by Sjors · Pull Request #12119 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/12101 | Clamp walletpassphrase timeout to 2^30 seconds and check its bounds by achow101 · Pull Request #12101 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] laanwj opened pull request #12198: rpc: Add deprecation error for `getinfo` (master...2018_01_getinfo_deprecation_message) https://github.com/bitcoin/bitcoin/pull/12198
< bitcoin-git>
[bitcoin] laanwj opened pull request #12197: Log debug build status and warn when running benchmarks (master...2018_01_debug_in_log) https://github.com/bitcoin/bitcoin/pull/12197
< gmaxwell>
or B for bitcoin mainnet... so at least your log parsing commands don't break.
< gmaxwell>
like "bitcoin-mainnet"
< gmaxwell>
though I bet jonas was doing time ./bitcoin-cli gettxoutsetinfo :P
< gmaxwell>
e.g. you have a signer that knows how to sign for SBTC, and you haven't spent any coins since the fork.. you could use a bitcoin node to create the sweep transactions...
< bitcoin-git>
[bitcoin] fwolfst opened pull request #12192: Trivial: Issue 12190: Update http URL of MIT license to use https (master...12190-UPDATE_MIT_LINK_TO_HTTPS) https://github.com/bitcoin/bitcoin/pull/12192
< bitcoin-git>
[bitcoin] ericallam opened pull request #12189: [Qt] Display transaction fee with sat/vbyte value in SendCoinsDialog (master...sat_vbyte_fee_rate_in_qt) https://github.com/bitcoin/bitcoin/pull/12189
< CubicEarths>
luke-jr: It wouldn't only be miners. I really don't understand the thinking behind why everyone needs to run a node for Bitcoin to be secure. It seems like a diminishing returns situation. If 1 out 100 people in the work run a node, I just can't really envision what would could wrong that would be made better by 99 out of 100 running nodes
< bitcoin-git>
[bitcoin] jeffrade opened pull request #12187: [Docs] Updating benchmarkmarking.md with an updated sample output (master...benchmark_output) https://github.com/bitcoin/bitcoin/pull/12187