< jcorgan>
somehow i had restored a snapshot of bitcoin dir that only had 183k blocks in it
< wumpus>
unbatched? hmm, doing a sqlite transaction per bitcoin transaction is certainly going to kill sqlite performance
< wumpus>
after running a while, bitcoin-shutoff is taking a long time in sqlite3_close - possibly due to the lack of checkpoints
< jgarzik>
wumpus, One concern with the current implementation is the 'ORDER BY' - a sort - in the CDBIterator class. Once fully sync'd to current bitcoin block height, failing to store in an always-sorted container may create lumpy bitcoind behavior whenever CDBIterator is used... maybe.
< GitHub65>
[bitcoin] giacecco opened pull request #6885: Instructions on how to make the Homebrew OpenSSL headers visible... (master...master) https://github.com/bitcoin/bitcoin/pull/6885
< BlueMatt>
sipa: indeed, not sure what phantomcircuit is seeing is unexpected or not, but the graphs in the ml related to https://github.com/bitcoin/bitcoin/issues/6876 are not expected at all
< phantomcircuit>
while true;do bitcoin-cli getblocktemplate > /dev/null;done
2015-10-23
< jgarzik>
cfields, a DNS seed can build a picture of bitcoin users etc.
< GitHub95>
[bitcoin] btcdrak opened pull request #6884: Backport #6566, median-past locktime, rebased against 0.11 (0.11...mpl-0.11) https://github.com/bitcoin/bitcoin/pull/6884
< GitHub65>
[bitcoin] petertodd opened pull request #6883: Add BIP65 CHECKLOCKTIMEVERIFY to release notes (master...cltv-release-notes-v0.12.0) https://github.com/bitcoin/bitcoin/pull/6883
< maaku>
I am leaving bitcoin core development for a while, not sure how long. If someone wants to take over pushing for #6312, #6564, and #6566 please contact me.
< GitHub0>
[bitcoin] sdaftuar opened pull request #6881: Debug: Add option for microsecond precision in debug.log (master...add-microsecond-timestamps) https://github.com/bitcoin/bitcoin/pull/6881
< GitHub54>
[bitcoin] gavinandresen closed pull request #6880: New -logtimerelative option to do millisec debug.log timestamps (master...millisec_debuglog) https://github.com/bitcoin/bitcoin/pull/6880
< GitHub199>
[bitcoin] gavinandresen opened pull request #6880: New -logtimerelative option to do millisec debug.log timestamps (master...millisec_debuglog) https://github.com/bitcoin/bitcoin/pull/6880
< GitHub136>
[bitcoin] laanwj opened pull request #6877: rpc: Add maxmempool and effective min fee to getmempoolinfo (master...2015_10_mempool_effective_fee) https://github.com/bitcoin/bitcoin/pull/6877
< jgarzik>
jcorgan, naming? 2015_sqlite branch should not include any leveldb naming in the bitcoin->sqlite path. it _does_ build leveldb. it _does not_ link leveldb to bitcoind.
< GitHub159>
[bitcoin] jgarzik opened pull request #6873: [cleanup] leveldbwrapper becomes more generic 'dbwrapper' module (master...2015_dbwrapper) https://github.com/bitcoin/bitcoin/pull/6873
2015-10-22
< GitHub51>
[bitcoin] TheBlueMatt opened pull request #6872: Remove UTXO cache entries when the tx they were added for is removed/does not enter mempool (master...limitucache) https://github.com/bitcoin/bitcoin/pull/6872
< sipa>
jonasschnelli: if only we didn't have this pesky economy thing that relies on bitcoin
< jonasschnelli>
sipa: that sounds perfect for our bitcoin <1.0 version. :)
< gmaxwell>
jonasschnelli: yes, testing bitcoin core using <alternative database> :P it shouldn't be that much work; presumably jeff will report back on that soon
< gavinandresen>
a bug bounty worked for the last leveldb corruption issue we had (if i recall correctly). I'm still holding some bitcoin in the core dev expenses fund
< jonasschnelli>
Luke-Jr: the idea would be to bundle bitcoin-qt/core on windows together with vbox and a tiny distro. This would eliminate some ugly platform dependents.
< jonasschnelli>
serious: what would be the overhead to run bitcoin-qt/core in a vm on windows?
< gmaxwell>
I believe more people have stopped running bitcoin core on windows than currently run it.
< gmaxwell>
jonasschnelli: I think it would be a bad idea, its a very widely used platform and dropping it would be a major move against the ability of people to independnantly run, audit, etc. the bitcoin system.
< maaku>
i thought gmaxwell was declaring sipa a risk to bitcoin there
< GitHub122>
[bitcoin] MarcoFalke closed pull request #6866: [trivial] fix white space in rpc help messages (master...MarcoFalke-2015-rpcWhitespace) https://github.com/bitcoin/bitcoin/pull/6866
< wumpus>
also bitcoin's databases are not an external interface, don't query them directly unless it's to write troubleshooting/recovery tools
< wumpus>
ok, it would not be strange if it is happening while running tar on the datadir that bitcoin was running in, those files are deleted and recreated all the time
< wumpus>
yes, that doesn't sound good. Were you tarring while bitcoin running?
< Luke-Jr>
perhaps relevant: tar: /home/usbarmory/.bitcoin.bak/chainstate/1463292.ldb: File shrank by 2020259 bytes; padding with zeros
< Luke-Jr>
wumpus: the leveldb in question is under ~/.bitcoin.bak
< Luke-Jr>
wumpus: if you in fact want such a corrupt bitcoin dir, I can probably get one for oyu
< Luke-Jr>
[08:13:52] <phantomcircuit> can confirm bitcoin core requires reindex on power failure under windows <-- I can confirm it requires reindex on power failure under Linux..
< GitHub36>
[bitcoin] MarcoFalke opened pull request #6866: [trivial] fix white space in rpc help messages (master...MarcoFalke-2015-rpcWhitespace) https://github.com/bitcoin/bitcoin/pull/6866
< gmaxwell>
You can use it in a softfork manner without updating. Actually the bitcoin protocol _used_ to relay extra data outside of transactions but that got removed.
< gmaxwell>
I'd previously gone around to miner software and p2pool and had them fix it, even before it had been brought up in bitcoin core.
< gmaxwell>
jgarzik: now that we've removed all the gratitious sleeps from the networking, nagle is almost certantly slowing our performance. Consider how chatting the bitcoin protocol is. It likely also makes the traffic more bursty, which isn't good for other users sharing the network.
< gmaxwell>
I'd like to see this go in https://github.com/bitcoin/bitcoin/pull/6622 I've had this in testing on several nodes (including one acting as a gateway to the outside world) for several others for over a month now.
< gmaxwell>
because outside of bitcoin core most software (but by no means all) in the ecosystem is developed by teams of one or two people, and shipped with little to no systematic testing.
< gmaxwell>
the problem is that it is not very reasonable to demand the entire bitcoin ecosystem cut cold to new code all at once.
< GitHub173>
[bitcoin] laanwj closed pull request #6722: Limit mempool by throwing away the cheapest txn and setting min relay fee to it (master...mempoollimit) https://github.com/bitcoin/bitcoin/pull/6722
< GitHub9>
bitcoin/master 9c9b66f Matt Corallo: Fix calling mempool directly, instead of pool, in ATMP
< GitHub9>
bitcoin/master 49b6fd5 Pieter Wuille: Add Mempool Expire function to remove old transactions...
< GitHub9>
bitcoin/master 78b82f4 Suhas Daftuar: Reverse the sort on the mempool's feerate index
< GitHub65>
[bitcoin] MarcoFalke opened pull request #6860: Drop minRelayTxFee to 1000 (master...MarcoFalke-2015-minRelayTxFeeDrop) https://github.com/bitcoin/bitcoin/pull/6860
< GitHub43>
bitcoin/0.11 0720324 Alex Morcos: Make fee aware of min relay in pruning.py RPC test...
< wumpus>
how openbsd, even with the recent release, still manages to package a BDB that is *older* than the 4.8 required to build bitcoin core
2015-10-19
< GitHub123>
[bitcoin] morcos opened pull request #6857: Require nLastBlockFile to be the highest numbered file. (master...nLastBlockFile) https://github.com/bitcoin/bitcoin/pull/6857
< GitHub130>
[bitcoin] morcos opened pull request #6856: Do not allow block file pruning during reindex. (master...noPruneDuringReindex) https://github.com/bitcoin/bitcoin/pull/6856
< GitHub124>
[bitcoin] CodeShark opened pull request #6853: Added fNoRetargeting field to Consensus::Params (master...fNoRetargeting) https://github.com/bitcoin/bitcoin/pull/6853
< GitHub199>
[bitcoin] laanwj closed pull request #6162: Use 512-bit arithmetic for difficulty retarget calculation. (master...regtest_consensus_fix) https://github.com/bitcoin/bitcoin/pull/6162
< GitHub21>
[bitcoin] luke-jr opened pull request #6851: Optimisation: Store transaction list order in memory rather than compute it every need (master...opti_txorder) https://github.com/bitcoin/bitcoin/pull/6851
< gmaxwell>
please don't do the rest submittx at all if its only bin, if it won't take hex it will be massively less used, and we'll just have more code to hang around and bloat the codebase; while people will continue to eschew bitcoin core and use some web api that actually gives an interface people expect. :-/
< dcousens>
Probably easiest to just specify the format to whatever the default is, and have `-json` or whatever on bitcoin-tx though
< dcousens>
I feel like most users might do something along the lines of 'bitcoin-tx ... | curl 'http://somepopularnode.com/tx' --data-raw -H "Content-Type:application/octet-stream"
< GitHub181>
[bitcoin] morcos closed pull request #6131: Do not use hard-coded AllowFree for free transactions. (master...fix-sendfree) https://github.com/bitcoin/bitcoin/pull/6131
< GitHub199>
[bitcoin] Michagogo opened pull request #6836: Bring historical release notes up to date (0.10...0.10-add-release-notes) https://github.com/bitcoin/bitcoin/pull/6836
< gmaxwell>
https://www.reddit.com/r/Bitcoin/comments/3ou1im/bitcoin_core_version_0111_released/cw0g8d0 someone should respond to "A cool example of how an attack can prompt developers to make Bitcoin better." with "This improvement was written years ago, but not activated because at the time it blocked most transactions. We've been waiting for wallets to upgrade; with the attacks going on, it didn't mak
< Luke-Jr>
there were no changes to bitcoin-cli in 0.11.1, right?
< nanotube>
https://bitcoin.org/en/download <- suggest that the "over 20GB" part toward the bottom should probably be updated to "over 50GB", or point to some resource that tracks blockchain size for future-proofness, to avoid giving misleading info.
< * michagogo>
checks if there's a release PR for bitcoin.org
< GitHub36>
[bitcoin] Michagogo opened pull request #6832: Bring historical release notes up to date (0.11...0.11-add-release-notes) https://github.com/bitcoin/bitcoin/pull/6832
< GitHub66>
[bitcoin] Michagogo opened pull request #6831: Bring historical release notes up to date (0.10...0.10-add-release-notes) https://github.com/bitcoin/bitcoin/pull/6831
< GitHub90>
[bitcoin] Michagogo opened pull request #6830: Add historical release notes for October 2015 bugfix releases (master...add-release-notes) https://github.com/bitcoin/bitcoin/pull/6830
< michagogo>
It would be nice to have this channel subscribed to the gitian.sigs repo the same way it is to bitcoin
< GitHub8>
[bitcoin] gmaxwell closed pull request #6792: Defaults UPNP to off when discovery is disabled. (master...upnp_off_on_ip) https://github.com/bitcoin/bitcoin/pull/6792
< GitHub38>
[bitcoin] theuni opened pull request #6819: WIP: force zeromq to work with static linking+mingw (master...zeromq-mingw) https://github.com/bitcoin/bitcoin/pull/6819
< GitHub120>
[bitcoin] laanwj closed pull request #6810: zmq: point API link to 4.0 as that is what we are conforming to (master...zmq-api-link) https://github.com/bitcoin/bitcoin/pull/6810
< GitHub9>
bitcoin/master a1d623d Wladimir J. van der Laan: Merge pull request #6810...