< gmaxwell>
But we do not couple soft-forks to bitcoin core major releases.
< davec>
I brought it up over in bitcoin-dev, but I'll put it here too for visibility. As of block 583930 on testnet, the CLTV soft fork is active although there is a lot of hash power still mining under the pre-CLTV rules.
< GitHub40>
[bitcoin] laanwj closed pull request #6938: build: If both Qt4 and Qt5 are installed, use Qt5 (master...2015_11_prefer_qt5) https://github.com/bitcoin/bitcoin/pull/6938
< GitHub145>
bitcoin/master 193f7b5 Wladimir J. van der Laan: Merge pull request #6938...
< GitHub120>
[bitcoin] laanwj opened pull request #6938: build: If both Qt4 and Qt5 are installed, use Qt5 (master...2015_11_prefer_qt5) https://github.com/bitcoin/bitcoin/pull/6938
< GitHub126>
[bitcoin] laanwj closed pull request #6905: Use constants and minor fixes by luke-jr (master...lukejr-constants-no-mergeConf) https://github.com/bitcoin/bitcoin/pull/6905
< GitHub158>
bitcoin/master 5f9260f Luke Dashjr: Bugfix: If genproclimit is omitted to RPC setgenerate, don't change it; also show correct default in getmininginfo
< GitHub158>
bitcoin/master 420a82f Luke Dashjr: Bugfix: Describe dblogsize option correctly (it refers to the wallet database, not memory pool)
< GitHub158>
bitcoin/master caa3d42 Luke Dashjr: Bugfix: RPC: blockchain: Display correct defaults in help for verifychain method
< Eliel_>
It looks like the curl example in the help text you get with "bitcoin-cli help" does not work as is. It has the address list doubly JSON encoded while bitcoind doesn't expect two layers of JSON as input.
< GitHub76>
[bitcoin] laanwj opened pull request #6926: tests: Initialize networking on windows (master...2015_10_tests_networking_init) https://github.com/bitcoin/bitcoin/pull/6926
< GitHub69>
[bitcoin] Diapolo opened pull request #6921: [Trivial] remove unneeded spaces from init.cpp (master...trivial_typo_space) https://github.com/bitcoin/bitcoin/pull/6921
< GitHub48>
[bitcoin] Diapolo opened pull request #6920: remove unneded include from rpcserver.cpp and rpcclient.cpp (master...univalue) https://github.com/bitcoin/bitcoin/pull/6920
< GitHub195>
[bitcoin] laanwj opened pull request #6919: Backport chainstate obfuscation to 0.11 (0.11...2015_10_backport_chainstate_obfuscation) https://github.com/bitcoin/bitcoin/pull/6919
< belcher>
oh damn this channel, didnt realise, ask in #bitcoin
< diegoviola>
will bitcoin core implement SPV like electrum and seeds?
2015-10-30
< GitHub146>
[bitcoin] laanwj closed pull request #6906: Reject invalid pubkeys when reading ckey items from the wallet. (master...ckey_pubkey_check) https://github.com/bitcoin/bitcoin/pull/6906
< GitHub164>
bitcoin/master 48b5b84 Wladimir J. van der Laan: Merge pull request #6906...
< GitHub164>
bitcoin/master 30d9662 Gregory Maxwell: Reject invalid pubkeys when reading ckey items from the wallet....
< gmaxwell>
I expect most of the work related to my NBD suggestion will be discovering that all filesystems are broken, and being unable to get results against bitcoin until the file systems are fixed. :(
< GitHub21>
[bitcoin] laanwj opened pull request #6917: leveldb: Win32WritableFile without memory mapping (master...2015_10_leveldb_win_nomap) https://github.com/bitcoin/bitcoin/pull/6917
< GitHub118>
[bitcoin] sipa closed pull request #6916: Remove BIP30 enforcement, as it is impossible to trigger since BIP34 (master...nobip30) https://github.com/bitcoin/bitcoin/pull/6916
< GitHub92>
[bitcoin] sipa opened pull request #6916: Remove BIP30 enforcement, as it is impossible to trigger since BIP34 (master...nobip30) https://github.com/bitcoin/bitcoin/pull/6916
< wumpus>
and not sure bitcoin core should be resilient to motherboard-bends-while-application-is-running crashes :-)
< wumpus>
cfields: what would be the best way to include the windows determinism postprocessing in the gitian build (in https://github.com/bitcoin/bitcoin/pull/6900) - call it from the descriptor or 'make'?
< GitHub7>
[bitcoin] sdaftuar opened pull request #6915: [Mempool] Improve removal of invalid transactions after reorgs (master...fix-reorg-handling) https://github.com/bitcoin/bitcoin/pull/6915
< GitHub139>
[bitcoin] sipa opened pull request #6914: [WIP] Add pre-allocated vector type and use it for CScript (master...prevector) https://github.com/bitcoin/bitcoin/pull/6914
< gmaxwell>
Seperate subject; https://github.com/bitcoin/bitcoin/pull/6902 I feel that changes like this make the software more opaque. Now to understand whats being done there you must read two places instead of one. If you only look at policy.h you will likely erroniously believe it applies to p2sh somehow.
< gmaxwell>
warren: it's all ugly, bitcoin core is currently not intended for system level operation.
< gmaxwell>
warren: what happens if a second datadir is specified to bitcoin-cli?
< warren>
Would it be bad if the system-level systemd service were named something like bitcoinsys.service, with a selinux context bitcoinsys_t, and a bitcoin-cli wrapper named something like /usr/bin/bitcoinsys_cli that only adds the --datadir /path/to/system/datadir/
< gmaxwell>
warren: as far as selinux policy, I think it's unfortunate that you cannot confine bitcoin core to have no access outside of its own directory.
< gmaxwell>
warren: this channel should be for bitcoin core exclusive discussion.
< GitHub7>
[bitcoin] MarcoFalke reopened pull request #6905: Use constants and minor fixes by luke-jr (master...lukejr-constants-no-mergeConf) https://github.com/bitcoin/bitcoin/pull/6905
< GitHub107>
[bitcoin] jtimon opened pull request #6908: Chainparams: DRY: Make qt/guiutil.cpp fit BIP70 chain name strings (master...chainparams-bip70-0.12.99) https://github.com/bitcoin/bitcoin/pull/6908
< GitHub71>
[bitcoin] jtimon opened pull request #6907: Chainparams: Use a regular factory for creating chainparams (master...chainparams-factory-0.12.99) https://github.com/bitcoin/bitcoin/pull/6907
< wumpus>
right it's the minimum *per KB*, all fees in bitcoin core are per kB
< sipa>
but it was somehow part of the wider bitcoin irc meeting, which took place in #bitcoin-dev an hour ago
< wumpus>
this channel has a very narrow scope: code changes to the bitcoin core project
< MarcoFalke>
Do those channels have different scopes? I remember bitcoin-dev is deprecated?
< jgarzik>
already covered in #bitcoin-dev meeting
< GitHub171>
[bitcoin] MarcoFalke closed pull request #6905: Use constants and minor fixes by luke-jr (master...lukejr-constants-no-mergeConf) https://github.com/bitcoin/bitcoin/pull/6905
< GitHub81>
[bitcoin] gmaxwell opened pull request #6906: Reject invalid pubkeys when reading ckey items from the wallet. (master...ckey_pubkey_check) https://github.com/bitcoin/bitcoin/pull/6906
< GitHub129>
[bitcoin] MarcoFalke opened pull request #6905: Use constants and minor fixes by luke-jr (master...lukejr-constants-no-mergeConf) https://github.com/bitcoin/bitcoin/pull/6905
< GitHub33>
[bitcoin] dajohi opened pull request #6902: policy: Add new constant MAX_STANDARD_MULTISIG_KEYS (master...multisig_keys) https://github.com/bitcoin/bitcoin/pull/6902
< wumpus>
majority plays no role in bitcoin - if *your* node forks from the block chain, that's a risk to you
< mcelrath>
Is bitcoin anymore consensus-dependent on leveldb? If we swap it out with sqlite or lmdb, will it still be consensus critical? (and can it be made non-consensus critical?)
< dcousens>
I can put bitcoin-qt on a old gaming rig if necessary, have to dust it off a little but, if its worth it
< CodeShark>
I don't really fricking care, personally - I don't really run a bunch of bitcoin core instances on windows - I'm just repeating what I've heard from others
< wumpus>
I don't want to hear "leveldb is broken on windows" every day, this is not tea time with bitcoin-dev, we should be constructive here
< Luke-Jr>
dcousens: #bitcoin maybe?
< bsm117532>
Quick git question...I did a push -f to overwrite my previous commit, because I like having clean histories. I could have also made a second commit on this PR. Does anyone care? Would github have squashed them anyway? (Re: https://github.com/bitcoin/bitcoin/pull/6899 )
< bsm117532>
That's a very hard problem that I don't think bitcoin can solve by choice of db.
< sipa>
bsm117532: jeff has a branch with bitcoin core running on sqlite3
< sipa>
if we need to change something to our leveldb tree, the correct way is submit it as a PR to the bitcoin/leveldb repo, and then bitcoin core can update to a new version
< bsm117532>
AFAICT, when I clone bitcoin, I don't get the bitcoin/leveldb repo. I get bitcoin/src/leveldb which is entirely separate. Am I wrong about that?
< gmaxwell>
aj: rethinking this resulted in coming up with the seggregated witness approach thats in elements alpha, and which may be possible to soft-fork into bitcoin.
< gmaxwell>
aj: well they're one in the same in Bitcoin Core; these changes are accomplished via validation flags. To make them non-standard we add the new restrictions to the set of flags used to verify transactions going into the mempool.
< GitHub73>
[bitcoin] sipa closed pull request #6776: Support -checkmempool=N, which runs checks once every N transactions (master...fraccheck) https://github.com/bitcoin/bitcoin/pull/6776
< GitHub163>
[bitcoin] giacecco closed pull request #6885: Instructions on how to make the Homebrew OpenSSL headers visible... (master...master) https://github.com/bitcoin/bitcoin/pull/6885
< GitHub176>
[bitcoin] Diapolo opened pull request #6893: forward-declare univalue in rpcclient + remove include in rpcserver.cpp (master...univalue) https://github.com/bitcoin/bitcoin/pull/6893
< wumpus>
2GB should certainly be enough. See e.g. https://github.com/bitcoin/bitcoin/issues/6658 , worst contender main.cpp uses 1.2MB while compiling (on gcc 4.8). Adding swap may help though, linux' memory management works better if swap is enabled even if you don't need the extra memory
2015-10-26
< GitHub108>
[bitcoin] laanwj closed pull request #6881: Debug: Add option for microsecond precision in debug.log (master...add-microsecond-timestamps) https://github.com/bitcoin/bitcoin/pull/6881
< GitHub138>
bitcoin/master 7bbc7c3 Suhas Daftuar: Add option for microsecond precision in debug.log
< GitHub138>
bitcoin/master 2b62551 Wladimir J. van der Laan: Merge pull request #6881...
< GitHub52>
bitcoin/master 143d173 Eric Lombrozo: Use BOOST_CHECK_MESSAGE() rather than BOOST_CHECK() in alerts_tests.cpp and initialize strMiscWarning before calling PartitionCheck()."
< gmaxwell>
(a failure to make this optimization is part of what contributes to miners mining on other miners work without validating-- they go and 'optimize' at a layer higher than Bitcoin, and as a resut complex details like validation go out the window. :) )
< GitHub175>
[bitcoin] jonasschnelli opened pull request #6889: fix locking issue with new mempool limiting (master...2015/10/fix_mempool_lock) https://github.com/bitcoin/bitcoin/pull/6889
< GitHub161>
[bitcoin] laanwj closed pull request #6566: BIP-113: Mempool-only median time-past as endpoint for lock-time calculations (master...medianpasttimelock) https://github.com/bitcoin/bitcoin/pull/6566
< GitHub168>
bitcoin/master ff057f4 Wladimir J. van der Laan: Merge pull request #6566...
< GitHub168>
bitcoin/master dea8d21 Mark Friedenbach: Enable policy enforcing GetMedianTimePast as the end point of lock-time constraints...
< GitHub168>
bitcoin/master 9d55050 Mark Friedenbach: Add rules--presently disabled--for using GetMedianTimePast as endpoint for lock-time calculations...
< GitHub173>
[bitcoin] laanwj closed pull request #6813: Support gathering code coverage data for RPC tests with lcov (master...btc-test-lcov-rpc) https://github.com/bitcoin/bitcoin/pull/6813
< GitHub137>
bitcoin/master 8e3a27b dexX7: Require Python for RPC tests, when using lcov...
< GitHub137>
bitcoin/master d425877 dexX7: Remove coverage and test related files, when cleaning up...
< GitHub137>
bitcoin/master 4d2a926 dexX7: Ignore coverage data related and temporary test files