< GitHub68>
[bitcoin] pstratem opened pull request #8142: Improve CWallet API with new GetAccountPubkey function. (master...2016-06-02-cwallet-getaccountpubkey) https://github.com/bitcoin/bitcoin/pull/8142
< GitHub38>
[bitcoin] jonasschnelli opened pull request #8138: Add maximal amount-of-transactions limit to checkblock/CVerifyDB (master...2016/06/verify_db) https://github.com/bitcoin/bitcoin/pull/8138
< GitHub10>
[bitcoin] pstratem opened pull request #8137: Improve CWallet API with new AccountMove function. (master...2016-06-02-cwallet-accountmove) https://github.com/bitcoin/bitcoin/pull/8137
< GitHub8>
[bitcoin] jonasschnelli opened pull request #8136: Log/report in 10% steps during VerifyDB (master...2016/06/init_checkblocks) https://github.com/bitcoin/bitcoin/pull/8136
< iniana>
When I restarted bitcoin core recently the verification of the previous 288 blocks was also that slow.
< wumpus>
bitcoin core makes heavy use of paralellism for verification
< GitHub85>
bitcoin/master ee1533e Jonas Schnelli: Merge #8129: Fix RPC console auto completer...
< GitHub50>
[bitcoin] jonasschnelli opened pull request #8135: [OSX] fix make deploy when compiling on OSX (master...2016/06/makedeploy) https://github.com/bitcoin/bitcoin/pull/8135
< GitHub19>
[bitcoin] sipa closed pull request #8082: Defer inserting into maprelay until just before relaying. (master...just_in_time_maprelay) https://github.com/bitcoin/bitcoin/pull/8082
< GitHub3>
bitcoin/master 01d8359 Pieter Wuille: Merge #8082: Defer inserting into maprelay until just before relaying....
< GitHub3>
bitcoin/master 4d8993b Gregory Maxwell: Defer inserting into maprelay until just before relaying....
< GitHub70>
[bitcoin] laanwj closed pull request #8080: Do not use mempool for GETDATA for tx accepted after the last mempool req. (master...nonmempool_getdata) https://github.com/bitcoin/bitcoin/pull/8080
< GitHub172>
bitcoin/master 862fd24 Wladimir J. van der Laan: Merge #8080: Do not use mempool for GETDATA for tx accepted after the last mempool req....
< GitHub172>
bitcoin/master 7e908c7 Gregory Maxwell: Do not use mempool for GETDATA for tx accepted after the last mempool req....
< GitHub73>
[bitcoin] sipa opened pull request #8123: Use std::atomic for fRequestShutdown and fReopenDebugLog (master...notsigbutatomic) https://github.com/bitcoin/bitcoin/pull/8123
< cfields_>
sipa: hmm, why not? It's cleanly separated from the rest of bitcoin, and knows nothing of transactions/blocks/etc. Seems abstract enough for the gui to deal with directly?
< gmaxwell>
"developers adding conman to bitcoin core"
< petertodd>
make it clear that the standard *describes* a subset of openssh's standard, and that bitcoin's use of it is identical and can reuse the existing code
< GitHub124>
[bitcoin] sdaftuar opened pull request #8104: Tests: add timeout to sync_blocks() and sync_mempools() (master...improve-rpc-sync) https://github.com/bitcoin/bitcoin/pull/8104
< GitHub160>
[bitcoin] sipa closed pull request #8102: Bugfix: use global ::fRelayTxes instead of CNode in version send (master...oopsrelay) https://github.com/bitcoin/bitcoin/pull/8102
< GitHub132>
bitcoin/master 425278d Pieter Wuille: Merge #8102: Bugfix: use global ::fRelayTxes instead of CNode in version send...
< GitHub132>
bitcoin/master 52b02ec Pieter Wuille: Use global ::fRelayTxes instead of CNode one
< GitHub39>
[bitcoin] sipa opened pull request #8102: Bugfix: use global ::fRelayTxes instead of CNode in version send (master...oopsrelay) https://github.com/bitcoin/bitcoin/pull/8102
< GitHub162>
[bitcoin] CodeShark opened pull request #8101: Disable mining on nonrelease branches. (master...disable_mining_on_nonrelease_branches) https://github.com/bitcoin/bitcoin/pull/8101
< GitHub121>
[bitcoin] sipa closed pull request #8049: Expose information on whether transaction relay is enabled in `getnetwork` (master...2016_05_rpc_relaytxes) https://github.com/bitcoin/bitcoin/pull/8049
< GitHub106>
bitcoin/master c028c7b Pieter Wuille: Merge #8049: Expose information on whether transaction relay is enabled in `getnetwork`...
< GitHub106>
bitcoin/master 1ab1dc3 Wladimir J. van der Laan: rpc: Add `relaytxes` flag to `getnetworkinfo`...
< GitHub106>
bitcoin/master 581ddff Wladimir J. van der Laan: net: Add fRelayTxes flag...
< GitHub60>
bitcoin/master 02ce2a3 Pavel Vasin: qt: askpassphrasedialog: Clear pass fields on accept...
< shesek>
anyone read Aviv Zohar's new paper? http://arxiv.org/abs/1605.07524 "Hijacking Bitcoin: Large-scale Network Attacks on Cryptocurrencies"
2016-05-25
< Gatornade>
nevermind, read the header. i'll go to #bitcoin
< Gatornade>
Hello, is this a good channel to ask one simple question about bitcoin core application?
< GitHub84>
[bitcoin] sipa closed pull request #7795: UpdateTip: log only one line at most per block (master...2016_04_block_warning_logging_inline) https://github.com/bitcoin/bitcoin/pull/7795
< GitHub111>
bitcoin/master f20d42e Wladimir J. van der Laan: UpdateTip: log only one line at most per block...
< GitHub111>
bitcoin/master 47a7cfb Pieter Wuille: Merge #7795: UpdateTip: log only one line at most per block...
< GitHub149>
[bitcoin] MarcoFalke closed pull request #8095: Test framework: only cleanup on successful test runs (master...nocleanup-on-failure) https://github.com/bitcoin/bitcoin/pull/8095
< GitHub22>
bitcoin/master 6700cc9 MarcoFalke: Merge #8095: Test framework: only cleanup on successful test runs...
< GitHub22>
bitcoin/master 1ad9339 Suhas Daftuar: Test framework: only cleanup on successful test runs
< GitHub164>
[bitcoin] MarcoFalke opened pull request #8098: [qa] test_framework: Append portseed to tmpdir (master...Mf1605-qatmpdir) https://github.com/bitcoin/bitcoin/pull/8098
< GitHub37>
[bitcoin] theuni opened pull request #8097: RFC: rpc: Remove dns argument for getaddednodeinfo (master...remove-getaddednodeinfo-dns) https://github.com/bitcoin/bitcoin/pull/8097
< GitHub85>
[bitcoin] sdaftuar opened pull request #8095: Test framework: only cleanup on successful test runs (master...nocleanup-on-failure) https://github.com/bitcoin/bitcoin/pull/8095
< tErik_mc>
On the other hand, i am keeping the 2nd/secondary instances with "connect=primary-bitcoin-core-ip-adrs" option, so that they can only use the local primary Bitcoin-Core Node as their main source node, in that way less data will be downloaded by the secondary instances, right ?
< tErik_mc>
i am specifying, localloop & port "addnode=127.0.0.1:8333" in bitcoin.conf for 2nd/secondary bitcoin-qt.exe , instead of 192.168.10.120 lan ip address.
< tErik_mc>
As the 1st bitcoin-qt is "primary" for me, so for any other secondary bitcoin-qt under my subnet/router, am i suppose to connect secondaries with the 1st one by using the "connect" options ?
< tErik_mc>
In 1st bitcoin-qt.exe process, i have enabled RPC, specified rpc user+pass, and port 8332, but inside network-tools i do not see 1st bitcoin-qt.exe process is listening on 8332, but it is listening on 8333 though.
< tErik_mc>
It seems, 2nd bitcoin-qt process is connecting with the 1st bitcoin-qt process, and to eligius node, but 1st one still not able create any TCP out to 5 other nodes !!! whats wrong ?
< tErik_mc>
Hi, i'm running two bitcoin-qt.exe with two different bitcoin.conf files & two different folders (…\Roaming\Bitcoin1\ & …\Roaming\Bitcoin2\) by supplying -conf & -datadir via commandline. in 1st conf i have specified 3 eligius miner ip-address as "addnode" lines, in 2nd conf file i have specified the same addnodes as 1st conf, and in 2nd conf i have also added these extra lines: connect=127.0.0.1:8333 connect=192.168.10.120:8333.
< GitHub147>
[bitcoin] jonasschnelli closed pull request #8042: [Qt] Don't allow to open the debug window during splashscreen & verification state (master...2016/05/qt_debug_win_splash) https://github.com/bitcoin/bitcoin/pull/8042
< GitHub12>
bitcoin/master 6929711 Jonas Schnelli: Merge #8042: [Qt] Don't allow to open the debug window during splashscreen & verification state...
< GitHub12>
bitcoin/master 276ce84 Jonas Schnelli: [Qt] Disable some menu items during splashscreen/verification state
< GitHub89>
[bitcoin] Christewart opened pull request #8090: Adding P2SH(p2pkh) script test case (master...add_p2sh_p2pkh_script_test) https://github.com/bitcoin/bitcoin/pull/8090
< Chris_Stewart_5>
Does Bitcoin Core's bip repo accept pull requests of implementations of things like OP_CLTV, OP_CSV in other programming languages?
< tErik_mc>
ye, my bitcoin-qt finally finished re-indexing & fully-synced, and now its using 3.25 GB, 508 MB , 502 MB, 3.42 GB (Private Bytes, Working Set, Private WS, Virtual Size) memory.
< btcdrak>
tErik_mc: anything not specific to Bitcoin Core development should be in #bticoin-dev
< btcdrak>
#bitcoin-dev
< tErik_mc>
For bitcoin-core related bitcoin-mining talk/discussion, which channel is more appropriate ?
< tErik_mc>
From 9:25am to now: (next day) 1:24am, bitcoin-qt.exe -dbcache=2816 has reached from "16 weeks behind" to "11 days behind" : 3.22 GB, 2.03 GB, 2.04GB, 3.41 GB (Private Bytes, Working Set, Private WS, Virtual Size) memory. But PB comes down often to 1.96 GB, WS & P-WS comes down to 1.65 GB.
< GitHub127>
[bitcoin] pstratem opened pull request #8088: Avoid recalculating vchKeyedNetGroup in eviction logic. (master...2016-05-22-efficient-keyed-eviction) https://github.com/bitcoin/bitcoin/pull/8088
< GitHub122>
[bitcoin] pstratem opened pull request #8087: Introduce CBlockchain and move CheckBlockHeader (master...2016-05-22-cblockchain) https://github.com/bitcoin/bitcoin/pull/8087
2016-05-22
< tErik_mc>
Since cpu is most of the time close to 25%, and since this i3 uP has 1-core with 4-hardware-threads (4-sub-core) , i guess bitcoin-core is using only 1 thread. i think i should find out how many threads it really using or just pass a param to use 3 threads.
< tErik_mc>
But bitcoin-qt, always remains very fast at "blkchain-verifying" stage, and then initially very fast in "re-indexing", but slowed down few mins later.
< tErik_mc>
i tried again, this time with " bitcoind.exe -dbcache=2816 " only, though it began at much slower (8 MB/s) i/o rate & less cpu % usage, but after few mins, it sometime even reached 220 MB/s i/o rate , but averaging at 40 MB/s , and cpu usage remaining steady at 25% level . so in this turn it seems, its similar as bitcoin-qt.
< tErik_mc>
i'm looking at https://en.bitcoin.it/wiki/Running_Bitcoin . so may be bitcoind.exe supports -debug=net -debug=alert parameters, instead of -debug=1 . trying again.
< tErik_mc>
But after specifying dbcache=5888, it seems, bitcoind is very slow at finishing "blockchain-verifying" stage . but bitcoin-qt was able to finish that stage with only 1792 dbcache param, at much faster with less time !
< tErik_mc>
i guess when it reaches re-indexing stage, then bitcoin-cli stop will work.
< tErik_mc>
i have by mistake (again) started, bitcoind, but this time with -dbcache=5888 (i pressed enter, before i could change it to 2816), now, bitcoin-cli stop is not working anymore, showing error code: -28 , error message: Verifying blocks…
< tErik_mc>
BitcoinD seems to work at slightly higher rate than bitcoin-qt, max 5 MB/s difference (i guess around 8% difference) . both are fast at block-verifying stage, when re-indexing stage "XX Weeks Behind" begins, then they are again same rate . and both slowed down after 10 or so minutes of re-indexing :(
< wumpus>
bitcoin-cli stop
< tErik_mc>
so for running bitcoind, i would 1st need to create+set the bitcoin.conf, and then run bitcoind and then bitcoin-cli, right ?
< tErik_mc>
i have assumed that, bitcoind requires passing bunch of params in commandline, as i dont have an example command, i was using bitcoin-qt.exe
< tErik_mc>
no other param was specified other than -dbcache param , i have not created bitcoin.conf either.
< tErik_mc>
no other than, -dbcache param, i haven't specific anything else, i have not created bitcoin.conf either.
< tErik_mc>
but bitcoin-qt seems to exceed what i'm specifying !