< bitcoin-git>
[bitcoin] sipa opened pull request #11389: Support having SegWit always active in regtest (master...201709_itsalwayssegwitinregtestia) https://github.com/bitcoin/bitcoin/pull/11389
< bitcoin-git>
[bitcoin] sipa closed 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
< bitcoin-git>
bitcoin/master c6223b3 Pieter Wuille: Merge #11362: Remove nBlockMaxSize from miner opt struct as it is no longer used....
< bitcoin-git>
bitcoin/master 22fd04b Gregory Maxwell: Remove nBlockMaxSize from miner opt struct as it is no longer used.
< ossifrage>
gmaxwell, it doesn't seem to be IO or CPU bound, but I am using spinning rust, it seemed wasteful to eat up a large % of my ssd on bitcoin
< ossifrage>
gmaxwell, I had a 4G dbcache which was part of the reason the oom killer picked on bitcoin
< ossifrage>
That is really annoying chrome decided to eat up all the memory, but the oom killer took out bitcoin (while doing a reindex) and somehow the progress went from 99ish% to 85%, that is quite a bit of rollback
< gribble>
https://github.com/bitcoin/bitcoin/issues/7533 | RPC: sendrawtransaction: Allow the user to ignore/override specific rejections by luke-jr · Pull Request #7533 · bitcoin/bitcoin · GitHub
< wumpus>
importing keys in bitcoin core is considered advanced functionality anyhow
< kallewoof>
Someone wrote a post about that on reddit. One of the devs said two weeks I think. (LN is actually not bitcoin core, but a separate client entirely.)
< achow101>
I wonder if gavin made bitcoin xt or bitcoin classic releases signed with that key...
< kallewoof>
Would it be worth it to add a replay protection mechanism in Bitcoin where a NOP is replaced with <height> <blockhash> OP_CHECKBLOCKVERIFY which would fail if the hash of the block at the given height did not match <blockhash>? (It would probably require that <height> was less than <current height> - 100 to avoid nasty double spends at reorgs...)
< bitcoin-git>
[bitcoin] tomasvdw opened pull request #11376: Ensure backupwallet fails when attempting to backup to source file (master...core) https://github.com/bitcoin/bitcoin/pull/11376
< ThomasV>
well, p2pk is a bit different, because you do not create a bitcoin address for it
< 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....