< June 2025 >
Su Mo Tu We Th Fr Sa 1234567891011121314
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30
2017-09-20
< bitcoin-git>
[bitcoin] laanwj closed pull request #11132: Document assumptions that are being made to avoid NULL pointer dereferences (master...document-non-nullptr-assumptions) https://github.com/bitcoin/bitcoin/pull/11132
< bitcoin-git>
bitcoin/master 551d7bf Wladimir J. van der Laan: Merge #11132: Document assumptions that are being made to avoid NULL pointer dereferences...
< bitcoin-git>
bitcoin/master fdc3293 practicalswift: Document assumptions that are being made to avoid NULL pointer dereferences
< BlueMatt>
https://github.com/bitcoin/bitcoin/issues/11373 should just be closed with "Your filesystem permissions have been set to prevent bitcoind from accessing its datadir, which prevents it from starting" (unless someone wants to change it to a "we need a better error message for this bug" issue)
< Guest81071>
how can i develop or contribute to bitcoin
< Guest81071>
can i get any useful ideas to implement to develop bitcoin
< kallewoof>
Reading the OP_RETURNTRUE discussion on bitcoin-dev it struck me that if we bump segwit script version at some point, old nodes will all accept the tx without looking, and new nodes will use the new script to verify. A miner running old version could mine txs with invalid scripts and old nodes would accept this block while new nodes would not. This would become a hardfork, no?
< kallewoof>
I don't really wanna waste anyone's time, but I've been trying to figure out the gitian build process lately and am having issues. I was following https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md and everything was fine down to "Getting and building the inputs". For one I had to cd into ../bitcoin/ for there to be a contrib/gitian-build.sh file (not mentioned, but no biggie),
< bitcoin-git>
[bitcoin] esotericnonsense opened pull request #11366: Trivial: RPC/getblockchaininfo: pruneheight is only present in pruned mode (master...2017-09-getblockchaininfo-docs) https://github.com/bitcoin/bitcoin/pull/11366
< bitcoin-git>
[bitcoin] gmaxwell opened pull request #11362: Remove nBlockMaxSize from miner opt struct as it is no longer used. (master...2017_09_rm_nBlockMaxSize) https://github.com/bitcoin/bitcoin/pull/11362
< gmaxwell>
goatpig: if something like that went on for weeks it would be doubtful if bitcoin would continue to exist at the end of such an event, regardless tweaking forward assumevalid wouldn't be a high priority. ... losing it entirely isn't that big of a deal.
< achow101>
sheldonthomas: that will work. don't forget to remove that after you start Bitcoin Core otherwise you will be resetting those settings on every start
< sheldonthomas>
Am going to add resetguisettings to my bitcoin.conf will that suffice?
< sheldonthomas>
Just noticed I have another plist called org.bitcoinfoundation.Bitcoin-Qt.plist should I remove that?
< bitcoin-git>
[bitcoin] esotericnonsense opened pull request #11359: Add a pruning 'high water mark' to reduce the frequency of pruning events (master...2017-09-add-pruning-hwm) https://github.com/bitcoin/bitcoin/pull/11359
< gmaxwell>
esotericnonsense: consider this, right now the chainstate on disk is 2.8gb adding the dbcache to the interval on syncing with defaults would end up with you needing to have 4GB free to sync bitcoin instead of 3.5.
< BashCo>
achow101: -resetguisettings worked. Unfortunately I did that before looking for the plist file. :( I found the file though, called `org.bitcoin.Bitcoin-Qt.plist`.
< 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
< esotericnonsense>
on linux it lives in .config/Bitcoin/Bitcoin-Qt.conf for me
< BashCo>
removing the bitcoin.conf was the first thing I tried but no luck. my mac os 10.12 system didn't have any issues at all. It's still syncing, then I'll try the older system again. Bet -resetguisettings will fix it.
< luke-jr>
jl2012: nCustomFeeRadio isn't in bitcoin.conf …
< achow101>
BashCo: can you pastebin the contents of ~/Library/Preferences/bitcoin-qt.plist (or something like that I think)
< gribble>
https://github.com/bitcoin/bitcoin/issues/11332 | Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) by jonasschnelli · Pull Request #11332 · bitcoin/bitcoin · GitHub
< jl2012>
BashCo: try removing bitcoin.conf. Should be fine
< meshcollider>
Machine_Ex98: I already told you that this channel is for bitcoin core development, read the channel name and description, go to #bitcoin channel
< meshcollider>
Take it to #bitcoin
< meshcollider>
Machine_Ex98: That's offtopic in this channel, this channel is only for bitcoin core development
< CryptAxe>
You don't have to ask on every channel.. And that's a companies API not the API of Bitcoin itself
< Machine_Ex98>
We currently offer Bitcoin withdrawals and deposits on our website. Blockchain API is used to handle all operations.
2017-09-16
< bitcoin-git>
[bitcoin] danra opened pull request #11354: Coins DB: Improve handling of FRESH child with non-DIRTY parent in CCoinsViewCa… (master...fix/batch-write-clean-parent-fresh-child) https://github.com/bitcoin/bitcoin/pull/11354
< bitcoin-git>
[bitcoin] danra opened pull request #11353: Small refactor of CCoinsViewCache::BatchWrite() (master...refactor/coins-view-cache-batch-write) https://github.com/bitcoin/bitcoin/pull/11353
< bitcoin-git>
[bitcoin] laanwj closed pull request #11333: Use std::nth_element instead of std::sort to calculate median time past (master...improve/median-time-past) https://github.com/bitcoin/bitcoin/pull/11333
< bitcoin-git>
[bitcoin] laanwj closed pull request #11196: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with -lto (master...fix-memory-clense) https://github.com/bitcoin/bitcoin/pull/11196
< bitcoin-git>
bitcoin/master e278f86 Wladimir J. van der Laan: Merge #11196: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with -lto...
< bitcoin-git>
bitcoin/master 1444c2e Adam Langley: Switch memory_cleanse implementation to BoringSSL's to ensure memory clearing even with link-time optimization....
< bitcoin-git>
[bitcoin] laanwj closed pull request #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt) (master...2017/09/qsettings_1) https://github.com/bitcoin/bitcoin/pull/11332
< bitcoin-git>
bitcoin/master 09627b1 Wladimir J. van der Laan: Merge #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (achow101, TheBlueMatt)...
< bitcoin-git>
bitcoin/master cdaf3a1 Matt Corallo: Fix Qt 0.14.2->0.15.0 segfault if "total at least" is selected...
< gmaxwell>
your inside jokes might confuse people. :P fwiw, on an up to date debian testing system, which was QT4 only, you can parallel install QT5, but it seems bitcoin-qt still builds using QT4 even with QT5 'installed'.
< gmaxwell>
Even if notepad is wrong (would be interesting to find out!) that still doesn't excuse bitcoin-- losing notepad is less serious then your wallet. :)
< gmaxwell>
jonasschnelli: I explained before. If you increase your resolution, position there. Shut down bitcoin. Reduce resolution. You will be in this state.
< achow101>
yes, from bitcoin.org
< luke-jr>
bane5000: #bitcoin please
< luke-jr>
bane5000: you mean prune=10000 ? note that user issues should be in #bitcoin though
< bane5000>
i've restarted the bitcoin-qt, however, the old blocks do not seem to be disappearing, as my harddrive space has not been reduced
< bane5000>
so i've enabled pruning on my core wallet (by creating bitcoin.conf in ~/.bitcoin/) and adding pruning=10000
< bitcoin-git>
[bitcoin] achow101 opened pull request #11334: Remove custom fee radio group and remove nCustomFeeRadio setting (master...rm-nCustomFeeRadio) https://github.com/bitcoin/bitcoin/pull/11334
< tloriato>
sipa in which cases does the bitcoin wallet changes the i from the path?
< tloriato>
oh, one more thing, sorry! bitcoin core uses m/0'/0'/k' for derivation path
< tloriato>
Hello! I was looking for how I could import a BIP32 Extended Key into the Bitcoin Core wallet? I've tried the RPC Documentation but got no luck there.
< bitcoin-git>
[bitcoin] danra opened pull request #11333: Use `std::nth_element` instead of `std::sort` to calculate median time past (master...improve/median-time-past) https://github.com/bitcoin/bitcoin/pull/11333
< esotericnonsense>
from #bitcoin: dingus | TYPO at the very top of https://bitcoin.org/en/release/v0.15.0 "14 October 2017" <- It's not October, yet, I hope
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #11332: Fix possible crash with invalid nCustomFeeRadio in QSettings (master...2017/09/qsettings_1) https://github.com/bitcoin/bitcoin/pull/11332
< harrymm>
aww. should i have told gdb to load symbols from the symbols downloaded? it says it's reading them from bitcoin-qt (which doesn't have them)
< wumpus>
can you pastebin the output of: <gmaxwell> harrymm: can you get a backtrace from it? gdb -c corefile ./path-to/bitcoin-qt then "thread apply all bt full"
< gmaxwell>
harrymm: can you get a backtrace from it? gdb -c corefile ./path-to/bitcoin-qt then "thread apply all bt full"
< achow101>
if anyone sees any issue remotely like #11171, please get the GUI settings (from windows registry or from ~/.config/Bitcoin/Bitcoin-Qt.conf) before doing -resetguisettings
< bitcoin-git>
[bitcoin] danra opened pull request #11330: Trivial: Fix comments for DEFAULT_WHITELIST[FORCE]RELAY (master...patch-10) https://github.com/bitcoin/bitcoin/pull/11330
< NicolasDorier>
so actually I did not tried https://github.com/bitcoin/bitcoin/pull/11126 yet. But the path of the locks is different from the PR so I guess this is different error.
< bitcoin-git>
bitcoin/master 96d91b7 Wladimir J. van der Laan: contrib: Ignore historical release notes for whitespace check...
< earlz>
How exactly do you debug the bitcoin-qt on 64bit windows? I know the gitian builds produce both the binaries and debug symbols, but not sure what the best way to debug a crash is
< bitcoin-git>
[bitcoin] MeshCollider opened pull request #11326: Fix crash on shutdown with invalid wallet (master...201709_shutdown_crash) https://github.com/bitcoin/bitcoin/pull/11326
< NicolasDorier>
mmh I doubt the bug comes from bitcoin core actually
< NicolasDorier>
Running bitcoin-core-0.15.0/test.rc3 on one of my server, getting "2017-09-14 06:55:48 socket send error The operation completed successfully. (0)" in logs _without_ debug=net. Then the connection drop to the peer. My peer is a NBitcoin peer, and I could not reproduce the error on the same 0.15.0/test.rc3 running on my machine.
< gmaxwell>
(I think expecting them to be well behaved is a bad idea, someone will spin up three pool daemons, they'll run in a fairly tight loop and prevent bitcoin from processing blocks, and wonder why they're getting orphan blocks)
< harding>
BashCo: that's an argument about what it is or is not possible to enforce. I think the important point is about what contributors to the Bitcoin Core project, mainly developers, choose to do regarding interactive communication.
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #11308: [qa] zapwallettxes: Wait up to 3s for mempool reload (master...Mf1709-qaZap3s) https://github.com/bitcoin/bitcoin/pull/11308
< bitcoin-git>
bitcoin/master 8df48b3 MarcoFalke: Merge #11308: [qa] zapwallettxes: Wait up to 3s for mempool reload...
< bitcoin-git>
bitcoin/master fadd0c1 MarcoFalke: [qa] zapwallettxes: Wait up to 3s for mempool reload
< harding>
BashCo: as I said above, I think the desire is not to get all Bitcoin users on the same platform; merely to get all developers on the same platform.
< BashCo>
gmaxwell's meetup vid covering 0.15 was really popular. a 'sunday talk show' circuit covering various bitcoin media outlets could get a great response, but I understand it has the negative effect of placing devs on pedestals and creating PR spokesmen.
< BashCo>
yeah fair enough. The Bitcoin community also has ambiguously defined boundaries. Lucky for Core, a large contingent of those communities support Core. That's why I think it's short sighted to pressure those communities to disband in favor of inferior platforms.
< luke-jr>
BashCo: I don't agree. The latter is simply the Bitcoin community.
< OdaNobunaga>
It's been suggested (today on the slack) to rebrand the slack into something not connected to core, for example "bitcoincommunity" or something like that (the bitcoin subdomain of slack is already taken)
< BlueMatt>
I absolutely agree there is some value in it, but some active steps should be taken to a) make clear this is not somehow a community related to bitcoin core (the technical project) and b) try to enforce lack of splitbrain
< achow101>
s/the community/any bitcoin related discussion community/
< BlueMatt>
while I understand the migration from Reddit and IRC to some extent, pushing folks towards Slack has, in large part, simply added yet another disconnected venue for Bitcoin discussion, creating yet another fork of the community whcih does not sufficiently communicate with other parts
< BlueMatt>
and the "splitbrain community" issues greg raised are also critical here - as the Bitcoin community grows Bitcoin becomes harder to change, and thats good, but it should not do so needlessly simply because parts of the community do not sufficiently communicate with other parts
< bitcoin-git>
[bitcoin] dooglus opened pull request #11320: Include the wallet name in log messages relating to wallets (master...wallet_name_in_log) https://github.com/bitcoin/bitcoin/pull/11320