< May 2026 >
Su Mo Tu We Th Fr Sa 12345678910111213141516
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31
2018-01-17
< 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
< bitcoin-git>
[bitcoin] NicolasDorier closed pull request #10947: [Wallet] Bare segwit scriptPubKey should not considered change by the wallet (master...importaddresssegwit) https://github.com/bitcoin/bitcoin/pull/10947
2018-01-14
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #12181: [TRIVIAL] Remove continue statement at the end of loop. (master...redundant_continue) https://github.com/bitcoin/bitcoin/pull/12181
< Victorsueca>
Cross-talk from #bitcoin here, I was wondering if there is any PR or plans to add hardware wallet support to Bitcoin Core
< bitcoin-git>
[bitcoin] kekimusmaximus opened pull request #12184: [TRIVIAL] Drop C headers in favour of C++-compatibility headers. (master...cpp11_includes) https://github.com/bitcoin/bitcoin/pull/12184
< bitcoin-git>
[bitcoin] kekimusmaximus opened pull request #12183: Make use of emplace_back in nonassociative containers. (master...use_emplace) https://github.com/bitcoin/bitcoin/pull/12183
< Arvidt>
Hi, what's the reason for the spike in bitcoin connections to my full node since yesterday? normally under 40, now up to 120. Many say they wher bitcoinj:0.14.5 and bitcore:1.1.0
< bitcoin-git>
[bitcoin] kekimusmaximus opened pull request #12181: [TRIVIAL] Remove continue statement at the end of loop. (master...redundant_continue) https://github.com/bitcoin/bitcoin/pull/12181
< bitcoin-git>
[bitcoin] mruddy opened 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] MarcoFalke closed pull request #12168: Trivial: Fix #include sys/fcntl.h to just fcntl.h (without sys/) (master...jasan/fcntl.h) https://github.com/bitcoin/bitcoin/pull/12168
< bitcoin-git>
bitcoin/master 648bdc8 Jan Sarenik: Trivial: Fix #include sys/fcntl.h to just fcntl.h (without sys/)...
< bitcoin-git>
bitcoin/master 45cf8a0 MarcoFalke: Merge #12168: Trivial: Fix #include sys/fcntl.h to just fcntl.h (without sys/)...
< CubicEarths>
surprisingly, Bitcoin Gold synced quickly using its own peers
< gmaxwell>
I guess its from people setting that option that lets them sync from bitcoin nodes or something, should probably submit a PR to them to remove that option.
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #12173: [Qt] Use flexible font size for QRCode image address (master...2018/01/fix_qr_font) https://github.com/bitcoin/bitcoin/pull/12173
< bitcoin-git>
[bitcoin] jtimon opened pull request #12172: Bugfix: RPC: savemempool: Don't save until LoadMempool() is finished (master...b16-bugfix-savemempool) https://github.com/bitcoin/bitcoin/pull/12172
< gribble>
https://github.com/bitcoin/bitcoin/issues/11739 | RFC: Enforce SCRIPT_VERIFY_P2SH and SCRIPT_VERIFY_WITNESS from genesis by sdaftuar · Pull Request #11739 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] kekimusmaximus opened pull request #12159: Use the character based overload for std::string::find. (master...use_char_overload_find) https://github.com/bitcoin/bitcoin/pull/12159
< gmaxwell>
luke-jr: AFAIK there is no common term for "someone attempted to 'pay me' by digging a hole in by back yard and leaving an envelope of money in it"... because outside of bitcoin no one is that @#$@# stupid. :)
< gmaxwell>
For example, a wallet could plausably not scan for any change outputs because it knows all that it creates. If I go find one of your prior change addresses and pay it there is no reason to think the wallet would ever see it. ... and in existing software (e.g. bitcoin core) the payment wouldn't show up even if it did see the funds.
< Chris_Stewart_5>
PSA: if anyone is interested in talking more about #12131 or #12132 there is a development channel that some work has been occurring in: #bitcoin-mast
< wumpus>
but a warning against 'malleating' addresses would make sense, I mean it's bad form and just because bitcoin core happens to accept it doesn't mean other wallets do
< morcos>
We can use the @bitcoin twitter handle maybe
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #12082: Adding test case for SINGLE|ANYONECANPAY hash type in tx_valid.json (master...add_tx_valid_singleanyonecanpay) https://github.com/bitcoin/bitcoin/pull/12082
< bitcoin-git>
bitcoin/master 0910cbe MarcoFalke: Merge #12082: Adding test case for SINGLE|ANYONECANPAY hash type in tx_valid.json...
< bitcoin-git>
bitcoin/master 18be3ab Chris Stewart: Adding test case for SINGLE|ANYONECANPAY hash type in tx_valid.json
< bitcoin-git>
[bitcoin] ryanofsky opened pull request #12150: Fix ListCoins test failure due to unset g_address_type, g_change_type (master...pr/listg) https://github.com/bitcoin/bitcoin/pull/12150
< provoostenator>
blueneon: that's not a good way to get familiar with the code in my experience. I somewhat selfishly suggest looking at random bitcoin core github issues and trying to help out in little bits.
< blueneon>
Hi there, I've made a fork/clone of the bitcoin coin in order for me to play around and get familiar. All went well after updating chainparams.cpp etc and I created new genesis and merkle etc -the code compiles and runs. However it crashes and debug.log says: ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=8)
< provoostenator>
After I copy the wallet over to a 0.15 node and restart, it throws "Error loading wallet.dat: Wallet requires newer version of Bitcoin Core". I only added a legacy address.
< provoostenator>
sipa: I'm a bit confused as to how to interpret scenario 1 in your gist. At least in the test I wrote, if you restore from a backup then any addresses that were generated after that backup would only reappear if you remember the correct sequence of legacy/p2sh-segwit/bech32 choices: https://github.com/bitcoin/bitcoin/pull/12152
< JayBerg>
i have 20+ years of c++ for fintech.. and would love to contribute to bitcoin-core.. I just cant seem to find the time. however, half my time is for outside consulting gigs to pay bills, so if there are any bounties or paid consulting gigs that will allow me to contribute. im all ears.. otherwise, i should be able to contribute starting mid-Feburary (after Super Bowl)
< JayBerg>
i appeciate the issues tracker, and will take a look… its just that i spend all day coding QT for bitcoin/blockchain and have lots of code an insight that can help if there are big blocking issues etc. jay at protoblock dot com
< bitcoin-git>
[bitcoin] Sjors opened pull request #12134: [WIP] Build previous releases and run functional tests (master...previous-release) https://github.com/bitcoin/bitcoin/pull/12134
< gribble>
https://github.com/bitcoin/bitcoin/issues/10595 | Bugfix: RPC/Mining: Use pre-segwit sigops and limits, when working with non-segwit GBT clients by luke-jr · Pull Request #10595 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] sdaftuar opened pull request #12133: [qa] Fix rare failure in p2p-segwit.py (master...2018-01-fix-p2p-segwit) https://github.com/bitcoin/bitcoin/pull/12133
< gribble>
https://github.com/bitcoin/bitcoin/issues/11389 | Support having SegWit always active in regtest (sipa, ajtowns, jnewbery) by sipa · Pull Request #11389 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] jtimon opened pull request #12128: Refactor: One CBaseChainParams should be enough (master...b16-baseparams-nohierarchy) https://github.com/bitcoin/bitcoin/pull/12128
< Randolf>
With the help of folks in the NetBSD community, I can now compile bitcoind (and friends) in NetBSD 7.0 after making a few minor changes to 2 files. I also added one "doc" file which provides build instructions. Since I'm new to GitHub and this is my first contribution to bitcoin, I want to make
< Chris_Stewart_5>
Does the bitcoin core software dump txs back into the mempool when a chain is clearly orphaned?
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #12120: Add dev guideline limiting auto usage. (master...2018-01-auto-devnotes) https://github.com/bitcoin/bitcoin/pull/12120
< bitcoin-git>
[bitcoin] Sjors opened pull request #12119: [wallet] use bech32 change address if all destinations are bech32 (master...bech32-change) https://github.com/bitcoin/bitcoin/pull/12119
< bitcoin-git>
[bitcoin] sdaftuar opened pull request #12118: Sort mempool by min(feerate, ancestor_feerate) (master...2018-01-fix-mempool-score) https://github.com/bitcoin/bitcoin/pull/12118
< ossifrage>
still no love building bitcoin-qt with -flto: ./libtool: line 1720: 18164 Segmentation fault (core dumped) /usr/bin/gcc-ranlib .libs/libsecp256k1.a
< achow101>
for general help, go to #bitcoin
< achow101>
Schwineigel: this channel is for Bitcoin Core development, not for helping users
< bitcoin-git>
[bitcoin] jackycjh opened pull request #12112: Docs: Remove the ending slashes from RPC URI format. (master...docs/multi-wallet_RPC_interface_correction) https://github.com/bitcoin/bitcoin/pull/12112
2018-01-07
< bitcoin-git>
[bitcoin] donaloconnor opened pull request #12108: [Refactor] Remove unused fQuit var from checkqueue.h (master...20180107_checkqueue_ref) https://github.com/bitcoin/bitcoin/pull/12108
< bambum>
btw. I can´t post on #bitcoin :Cannot send to channel
< bambum>
Hi, I have a question related to bitcoin-qt - when someone expose some of my privat keys from one wallet, can he somehow generate the other privat keys I use with the same wallet ?
< provoostenator>
lisey: here's some possibilities: https://github.com/bitcoin/bitcoin/labels/good%20first%20issue If you don't know C++, I would just start with making very small changes that only touch a few lines of code. Also, just browse through the Github issues...