< GitHub121>
[bitcoin] jonasschnelli opened pull request #8324: [Wallet] keep HD seed during salvagewallet (master...2016/07/hd_salvage) https://github.com/bitcoin/bitcoin/pull/8324
< GitHub29>
[bitcoin] jonasschnelli closed pull request #8205: [Wallet] add HD keypath to CKeyMetadata, report over validateaddress (master...2016/06/hd_metadata) https://github.com/bitcoin/bitcoin/pull/8205
< GitHub108>
[bitcoin] jonasschnelli opened pull request #8323: Add HD keypath to CKeyMetadata, report metadata in validateaddress (master...2016/07/hd_013) https://github.com/bitcoin/bitcoin/pull/8323
< gmaxwell>
cfields: I've found that a lot of people would like to play with it are actually thrown off by setting an option. It's not so intutive for GUI users. I think this would greatly increase testnet usage to have builds that work more like bitcoin/altcoin installs.
< gmaxwell>
Matt has announced his new relaynetwork work that uses UDP and FEC, http://bluematt.bitcoin.ninja/2016/07/07/relay-networks/ the current not really fully cooked software gets worldwide block propagation 99% of the time in less than 100ms over the fiber-path distances.
<@wumpus>
in any case, to conclude this topic: https://github.com/bitcoin/bitcoin/milestone/20 is an accurate reflection of what has to be done before rc1? (apart from the release notes issue)
< zooko>
Hey Core Devs: here's another patch we've been working on for Zcash which you might want upstream in Bitcoin Core: https://github.com/zcash/zcash/issues/915
< GitHub155>
[bitcoin] yurizhykin opened pull request #8313: Use std::move() instead of copying/removing in TxMemPool (master...tx-delete) https://github.com/bitcoin/bitcoin/pull/8313
< bsm1175321>
Does there exist any UTXO set commitment implementation as a patch/PR to bitcoin? I'm interested in running some benchmarks and comparisons of ways we might do it.
< GitHub19>
[bitcoin] MarcoFalke opened pull request #8302: [Qt] Disable some menu items during splashscreen/verification state (0.12...Mf1607-012qtDebugSplash) https://github.com/bitcoin/bitcoin/pull/8302
2016-07-02
< gmaxwell>
The primary, nearly exclusive, argument provided to why someone won't overpower the network (e.g. briefly) is becaues there isn't much that they can do with it. They can't just blank-check write themselve an extra 100,000 Bitcoin. They can DOS attack and double spend their own payments.
< gmaxwell>
yes, including the one built into bitcoin's p2p protocol, though thats several layers of irrelevance down the line. (also an attacker who can influence that one is already too powerful)
< CubicEarth>
gmaxwell: Thinking about your 'carving a block of marble' analogy for forks, and thinking about the nature of Bitcoin, I tend to think that anything can be accomplished with a 'soft-fork', such as effectively raising the coin limit, etc. I see it like a nested-universe scenario, but in the marble analogy... take the statue of David. Say we find ourselves disappointed that Michelangelo didn't give David
2016-07-01
< CubicEarth>
gmaxwell: well I'm pretty sure the rise of ETH was hurting the bitcoin price to some extent. I think this event was a decoupling, where Bitcoin shakes the monkey off its back.
< gmaxwell>
which adversely impacted the bitcoin price even though many of us have been pointing out the related risks and distinguishing bitcoin on the basis of them for some time.
< gmaxwell>
midnightmagic: I don't think that matters that much, but right now bitcoin "xt" is only not totally partitioned due to inbound connections from core to XT, but part of segwit is that segwit capable nodes will strongly prefer to connect out to only non-segwit nodes (because they must in order to get blocks once segwit is activated)-- the result will be making that partition complete.
< gmaxwell>
signature validation is, and bitcoin core runs that in paralle... but normally almost all of the signatures in a block are already validated before it shows up.
< bsm1175321>
Ok I think I understand. A wallet bitcoin.conf really should have 3 possible values then: non-segwit, segwit, and segwit-in-p2sh.
<@wumpus>
though of course it's not entirely certain whether the reported problems were due to this change, or another change, or a change in the general usage of bitcoin not directly related to a change in our wallet
<@wumpus>
though at some point the 'exclude these coins and do the selection again' list would become very long, and is less suited for non-boolean properties like input size (https://github.com/bitcoin/bitcoin/issues/7664)
< gmaxwell>
it ended up that way because they had multiple unconfirmed few-bitcoin outputs, and then a 1 bitcoin output and were making many not huge payments... so it decided to keep reusing the change because it considered them all equal.
< GitHub129>
[bitcoin] laanwj closed pull request #8285: windows: Add testnet link to installer (master...2016_06_testnet_link_windows) https://github.com/bitcoin/bitcoin/pull/8285
< GitHub68>
bitcoin/master da50997 Wladimir J. van der Laan: Merge #8285: windows: Add testnet link to installer...
< GitHub68>
bitcoin/master 975a41d Wladimir J. van der Laan: windows: Add testnet icon for testnet link...
< gmaxwell>
I don't think its of major importance, but "Bitcoin XT" recently started making only outbound connections to other XT nodes. In combination with segwit, I believe this will partition them. Because they are such a small number of nodes I don't think it warrents much attention, but something to be aware of.
< gmaxwell>
wumpus: I agree in principle except for the fact that a LOT of people have copied the "example config" from the bitcoin wiki and are setting all kinds of crazy things. :)
< GitHub96>
[bitcoin] jmcorgan closed pull request #8284: Backport remaining commits for out-of-tree builds from master to 0.12 branch (0.12...build-oot-0.12) https://github.com/bitcoin/bitcoin/pull/8284
< GitHub64>
[bitcoin] luke-jr opened pull request #8293: Bugfix: Allow building libbitcoinconsensus without any univalue (master...sys_univalue_opt) https://github.com/bitcoin/bitcoin/pull/8293
2016-06-29
< GitHub73>
[bitcoin] MarcoFalke opened pull request #8291: [util] CopyrightHolders: Check for untranslated substitution (master...Mf1607-utilCopy) https://github.com/bitcoin/bitcoin/pull/8291
< GitHub20>
[bitcoin] EthanHeilman opened pull request #8282: net: Feeler connections to increase online addrs in the tried table. (master...feelers3) https://github.com/bitcoin/bitcoin/pull/8282
< GitHub142>
[bitcoin] laanwj opened pull request #8281: qt: Remove client name from debug window (master...2016_06_qt_remove_client_name) https://github.com/bitcoin/bitcoin/pull/8281
< GitHub17>
[bitcoin] sdaftuar opened pull request #8280: Tests: Increase sync_blocks() timeouts in pruning.py (master...fix-pruning-test) https://github.com/bitcoin/bitcoin/pull/8280
< GitHub152>
[bitcoin] laanwj closed pull request #8261: The bit field is shown only when status is "started" (master...20160625_sw_getblockchaininfo_bit) https://github.com/bitcoin/bitcoin/pull/8261
< GitHub19>
bitcoin/master 3685e0c Wladimir J. van der Laan: Merge #8261: The bit field is shown only when status is "started"...
< GitHub19>
bitcoin/master 2129fce Pavel Janík: The bit field is shown only when status is "started"
< GitHub195>
[bitcoin] sipa opened pull request #8272: Make the dummy argument to getaddednodeinfo optional (master...optionaladdnodedummy) https://github.com/bitcoin/bitcoin/pull/8272
< GitHub49>
[bitcoin] laanwj closed pull request #8240: doc: Mention Windows XP end of support in release notes (master...2016_06_windows_xp) https://github.com/bitcoin/bitcoin/pull/8240
< GitHub121>
bitcoin/master 63fbdbc Wladimir J. van der Laan: Merge #8240: doc: Mention Windows XP end of support in release notes...
< GitHub121>
bitcoin/master b0be3a0 Wladimir J. van der Laan: doc: Mention Windows XP end of support in release notes...
< gmaxwell>
probably depends on the hardware, on my laptop I think it's IO. on systems with faster IO, I think its cpu inside leveldb code... at least with default dbcache. with dbcache cranked, its likely cpu elsewhere in bitcoin.
< GitHub136>
[bitcoin] paveljanik opened pull request #8261: The bit field is shown only when status is "started" (master...20160625_sw_getblockchaininfo_bit) https://github.com/bitcoin/bitcoin/pull/8261
< Lauda>
gmaxwell all that is required is "dbcache=3000" in bitcoin.conf right (since mine is practically empty) and I want to run another reindex over night?
< GitHub139>
[bitcoin] fanquake opened pull request #8252: [trivial] Add aarch64 to depends .gitignore (master...depends-aarch-gitignore) https://github.com/bitcoin/bitcoin/pull/8252
2016-06-23
< gmaxwell>
There is a cellphone game called spaceteam where you have to call out instructions for other people to punch in to jointly fly a fictional spacecraft. Manually setting consensus normative flags in bitcoin makes me think of spaceteam.
< gmaxwell>
I can tell you that a lot of bitcoin services have no reorg handling at all. :(
< gmaxwell>
jtimon: yes, and a seperate network that used just that and was otherwise the same as bitcoin testnet
< gmaxwell>
Bitcoin tx fees were too high for them, so they only use bitcoin for periodic commitments and they use testnet as a messaging flooding network.
< gmaxwell>
And the release cycle distinction we make for bitcoin is that consensus consistency changes are base, mandatory, functionality-- not software features (though sometimes some features must ride along with them)
<@wumpus>
re: launching testnet it would be useful if the windows installer created a Bitcoin Core (Testnet) link in the menu too, which does nothing but launch bitcoin-qt with -testnet flag. I have no idea how to do that though
<@wumpus>
it may be the windows machine I'm testing on is just crappy, I also had a strange issue with ldb files: https://github.com/bitcoin/bitcoin/issues/8250 .. possible that the disk is just very slow due to other processes interfering