< 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...
< GitHub9>
bitcoin/master 7d325b9 Johnathan Corgan: zmq: point API link to 4.0 as that is what we are conforming to [Trivial]...
< wumpus>
e.g. blablablabla.onion:8333 -> seed.bitcoin.jonasschnelli.ch:8333 means a node with Tor can connect to the onion instead, the exit node cannot interfere
< michagogo>
You need the `bitcoin` repo (specifically the contrib/gitian-descriptors and depends dirs), your fork of the `gitian.sigs` repo so you can add to it, and the `devrandom/gitian-builder` repo.
< michagogo>
PRab: "bitcoin-builder" isn't a thing
2015-10-12
< PRab>
I cloned gitian-builder, but never bitcoin-builder.
< GitHub171>
[bitcoin] dexX7 opened 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
< GitHub99>
[bitcoin] TheBlueMatt opened pull request #6812: Update bluematt-key, the old one is long-since revoked (master...master) https://github.com/bitcoin/bitcoin/pull/6812
< GitHub81>
[bitcoin] jmcorgan opened 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
< btcdrak>
could you come to #bitcoin-dev for a few mins to discuss the mailing list policy?
< btcdrak>
meeting needs to cover policy of bitcoin-dev@ and the new list
< GitHub91>
bitcoin/0.11 cf33f19 Wladimir J. van der Laan: doc: Add Luke Dashjr to credits in release notes...
< nanotube>
hm, set up a twitterbot to tweet bitcoin-announce mailing list titles with links to full email body? :)
< jgarzik>
would prefer to keep non-tech discussion of my post on #bitcoin. if there are tech corrections, by all means, post here
< jcorgan>
guys, sorry for instigating this discussion thread. clearly this was the kind of thing happening on #bitcoin-dev that brought about the change to using this channel instead. can we go back to pull requests and releases?
< alpalp>
most of the children have moved out of /r/bitcoin anyway
< jcorgan>
i'm not sure there are any useful public venues for bitcoin related matters any more. i'd say post announcements on a read-only mailing list, say, bitcoin-core-announce, and let responsible people stay on top of announcements about software they run that handles their money.
< GitHub12>
[bitcoin] CodeShark opened pull request #6798: Clarification of unit test build instructions. (master...unit_test_readme_fix) https://github.com/bitcoin/bitcoin/pull/6798