< bitcoin-git>
[bitcoin] jonasschnelli closed pull request #9130: Mention the new network toggle functionality in the tooltip. (master...20161111_disable_network_tooltip) https://github.com/bitcoin/bitcoin/pull/9130
< bitcoin-git>
bitcoin/master ac489b2 Jonas Schnelli: Merge #9130: Mention the new network toggle functionality in the tooltip....
< bitcoin-git>
bitcoin/master 1260c11 Pavel Janík: Mention the new network toggle functionality in the tooltip.
< bitcoin-git>
[bitcoin] jnewbery closed pull request #9203: [trivial] Fixes the RPC help text for waitforblockheight (master...waitforblockheightcomment) https://github.com/bitcoin/bitcoin/pull/9203
< bitcoin-git>
[bitcoin] jnewbery opened pull request #9203: [trivial] Fixes the RPC help text for waitforblockheight (master...waitforblockheightcomment) https://github.com/bitcoin/bitcoin/pull/9203
< wumpus>
this is not related to bitcoin core development, can you move this to #bitcoin?
< bitcoin-git>
[bitcoin] laanwj opened pull request #9202: bench: Add support for measuring CPU cycles (master...2016_11_bench_cpu_cycles) https://github.com/bitcoin/bitcoin/pull/9202
< bitcoin-git>
[bitcoin] gmaxwell opened pull request #9199: Always drop the least preferred HB peer when adding a new one. (master...remove_high_bandwidth_zombies) https://github.com/bitcoin/bitcoin/pull/9199
2016-11-21
< skyraider>
it might help to put on a client's shoes here. context was https://github.com/petertodd/python-bitcoinlib/pull/128 in which a blind retry python decorator was considered. turns out this can a) result in actually sending bitcoin multiple times, b) result in decisions made on stale read data (balance was just an example - really any bitcoind state subject to
< skyraider>
yes, sorry, shorthand for "try to send some bitcoin"
< skyraider>
uh, yeah, not bitcoin transaction. isolation as in the I from ACID.
< skyraider>
so 'read before you try to send lots of bitcoin' - alright. but if another RPC connection writes in the meantime, won't my read be stale, or is there transaction isolation somehow? is the recommended policy therefore 'only ever use a single RPC writer' ?
< instagibbs>
wumpus, I'm not an old timer, which is why I'm asking more basic account questions. It's always been deprecated in my Bitcoin lifetime :P
< bitcoin-git>
[bitcoin] laanwj closed pull request #9117: net: don't send feefilter messages before the version handshake is complete (master...feefilter-assert) https://github.com/bitcoin/bitcoin/pull/9117
< bitcoin-git>
bitcoin/master c390640 Wladimir J. van der Laan: Merge #9117: net: don't send feefilter messages before the version handshake is complete...
< bitcoin-git>
bitcoin/master 4662553 Cory Fields: net: don't send feefilter messages before the version handshake is complete
< bitcoin-git>
[bitcoin] laanwj closed pull request #9125: Make CBlock a vector of shared_ptr of CTransactions (master...sharedblock) https://github.com/bitcoin/bitcoin/pull/9125
< bitcoin-git>
bitcoin/master 1662b43 Pieter Wuille: Make CBlock::vtx a vector of shared_ptr<CTransaction>
< bitcoin-git>
bitcoin/master da60506 Pieter Wuille: Add deserializing constructors to CTransaction and CMutableTransaction
< bitcoin-git>
bitcoin/master 0e85204 Pieter Wuille: Add serialization for unique_ptr and shared_ptr
< bitcoin-git>
[bitcoin] instagibbs opened pull request #9194: Add flags to getrawtransaction and getblock to return non-segwit seri… (master...nonswserialrpc) https://github.com/bitcoin/bitcoin/pull/9194
< sipa>
it's probably a relatively good way to understand the design of bitcoin, but it's not that helpful to learn how the code works now
< luke-jr>
but in case he reads the log: I don't recommend reading the earliest code as a way to learn about Bitcoin. It was a mess, and included a lot of features later discarded (eg, built-in marketplace)
< meownow>
im currently reading through the first commit of the bitcoin source code onto github. seems a good way to familiarize myself with the core of the code base and what it does.
< luke-jr>
sipa: protocol changes need consensus. we can't force them on people. but it only takes good willed miners to use pro-Bitcoin policys.
< dermoth>
yeah and my apologies; I though I was in #bitcoin-dev (not -core-)
< sipa>
dermoth, rabidus: also, please take this to #bitcoin
< rabidus>
you would kill the "store of value" property of bitcoin
< dermoth>
I think after a certain number of bitcoin cycles (210k blocks) we could scavenge all unspent coins from the oldest 210k block, put them in a pool and let miners siphon 1/210000th of that pool every block. At that point the older part of the chain could be completely dropped as it would no longer have any use, and pooling the fund would ensure miners get a predictable reward.
< gribble>
https://github.com/bitcoin/bitcoin/issues/707 | Implement BIP 14 : separate protocol version from client version by gavinandresen · Pull Request #707 · bitcoin/bitcoin · GitHub
< wumpus>
many people only use their bitcoin wallet with wifi so could care less about bandwidth usage
< wumpus>
we're just nopt using BIP37 for the light wallet mode in bitcoin core. If you want to use it in your wallet go ahead.
< gmaxwell>
Chris_Stewart_5: besides, fetching blocks is 14kb/s ongoing (28kb/s perhaps soon)-- most people running bitcoin core can handle that without batting an eye.
< gmaxwell>
jonasschnelli: political discussion to ##bitcoin.
< shangzhou>
gmaxwell: i did some search this morning at baidu. Searched "c1726ccc50635795c942c7d7e51d979c4f83a3d17f8982e9d02a114a15fef419" only one result (a thread http://8btc.com/thread-41510-1-5.html) someone use Avast complain that bitcoin 0.13.1 win exe downloaded from bitcoin.org was blocked by the avast. Search something like "bitcoin 0.13.1 win exe" top one is
< BlueMatt>
-rw------- 1 matt matt 1.7T Nov 16 16:44 /home/matt/.bitcoin/debug.log
< bitcoin-git>
[bitcoin] laanwj closed pull request #9131: fNetworkActive is not protected by a lock, use an atomic (master...2016/11/net_toggle) https://github.com/bitcoin/bitcoin/pull/9131
< bitcoin-git>
bitcoin/master 079142b Jonas Schnelli: fNetworkActive is not protected by a lock, use an atomic
< bitcoin-git>
bitcoin/master 62af164 Wladimir J. van der Laan: Merge #9131: fNetworkActive is not protected by a lock, use an atomic...
< achow101>
Squidicuz: yes, bitcoincore.org is Bitcoin Core's site
< shinyg>
Maybe bitcoin is a software stack but Core is just software
< shinyg>
makes sense, how about is Bitcoin Core a Solution stack or software as some describe it/
< achow101>
they're trying to separate bitcoin core from bitcoin.org as bitcoin.org is for bitcoin in general whilst bitcoin core is a specific project
< sipa>
but bitcoin core has its own project website now
< shinyg>
so was there a specific reason why new releases stopped coming from bitcoin.org?
< achow101>
also, IIRC bitcoin.org and the bitcoin foundation are no longer related
< achow101>
shinyg: blockstream does not fund Bitcoin Core development at all. There are developers who work on Bitcoin Core who also have jobs at Blockstream. The people who actually partially fund development are the MIT DCI who actually pay some people to work on Core (wladimir, cory)
< shinyg>
I have recently expanded the Wikipedia article for Bitcoin Core by a factor of 10. Could someone spend just a few minutes to see if there are any major ommission or errors?
< shinyg>
Hi people, I was after a little assistance from those who know more about Bitcoin Core and those who support Wikipedia.
< bitcoin-git>
[bitcoin] ryanofsky opened pull request #9159: [qa] Wait for specific block announcement in p2p-compactblocks (master...cmpct-announce-wait) https://github.com/bitcoin/bitcoin/pull/9159
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #9156: Add compile and link options echo to configure (master...2016/11/configure) https://github.com/bitcoin/bitcoin/pull/9156
< gmaxwell>
okay, bitcoin's sha256 is 237.1 million bytes per second, openssl is 320.7 million bytes per second.. and the chacha is 358.6 million bytes per second. (openssl at slight disadvantage due to 8k vs 1m size, but it doesn't matter much)
< btcdrak>
gmaxwell: no no, we're not allowed to sign that, because it's Roger Ver's attempt to snub Bitcoin Core. Looks like a more watered down version of the first leak http://pastebin.com/cgkqcWBS.
< bitcoin-git>
[bitcoin] fanquake closed pull request #9154: Add recent checkpoints to remove CPU load during sync (master...f/new-checkpoints) https://github.com/bitcoin/bitcoin/pull/9154
< bitcoin-git>
[bitcoin] XertroV opened pull request #9154: Add recent checkpoints to remove CPU load during sync (master...f/new-checkpoints) https://github.com/bitcoin/bitcoin/pull/9154
< bitcoin-git>
[bitcoin] luke-jr opened pull request #9152: Wallet/RPC: sweepprivkeys method to scan UTXO set and send to local wallet (master...sweepprivkeys) https://github.com/bitcoin/bitcoin/pull/9152
< bitcoin-git>
[bitcoin] luke-jr closed pull request #9150: Qt: Make network disabled icon larger and 50% opaque (master...gui_netdisabled_icon_enlarge) https://github.com/bitcoin/bitcoin/pull/9150
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #9151: [qa] proxy_test: Calculate hardcoded port numbers (master...Mf1611-qaPort) https://github.com/bitcoin/bitcoin/pull/9151
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #9145: [qt] Make network disabled icon 50% opaque (master...Mf1611-qtNetworkIcon) https://github.com/bitcoin/bitcoin/pull/9145
< bitcoin-git>
[bitcoin] fanquake opened pull request #9144: [Trivial] Correct waitforblockheight example help text (master...rpc-commands) https://github.com/bitcoin/bitcoin/pull/9144
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #9143: Refactor ZapWalletTxes to avoid layer vialotions (master...2016/11/wallet_db_refactoring_1) https://github.com/bitcoin/bitcoin/pull/9143
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #9142: Move -salvagewallet, -zap(wtx) to where they belong (master...2016/11/wallet_init) https://github.com/bitcoin/bitcoin/pull/9142
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #9141: Remove unnecessary calls to CheckFinalTx (master...2016/11/istrusted) https://github.com/bitcoin/bitcoin/pull/9141
< bitcoin-git>
[bitcoin] luke-jr closed pull request #8388: [0.13] mining: Optimise for typical mining use with blockmaxsize (0.13...blockmaxsize_opti-0.13) https://github.com/bitcoin/bitcoin/pull/8388
< bitcoin-git>
[bitcoin] luke-jr closed pull request #7534: Minimal RPC & wallet support for CLTV-enabled multisig addresses (master...cltv_address) https://github.com/bitcoin/bitcoin/pull/7534
< bitcoin-git>
[bitcoin] luke-jr opened pull request #9140: Bugfix: Correctly replace generated headers and fail cleanly (master...bugfix_genheaders) https://github.com/bitcoin/bitcoin/pull/9140