< GitHub189>
[bitcoin] jtimon opened pull request #8077: Consensus: Decouple from chainparams.o and timedata.o (master...0.12-consensus-chainparams) https://github.com/bitcoin/bitcoin/pull/8077
< GitHub105>
[bitcoin] sdaftuar opened pull request #8076: VerifyDB: don't check blocks that have been pruned (master...pruning-checkblocks) https://github.com/bitcoin/bitcoin/pull/8076
< GitHub58>
[bitcoin] gmaxwell closed pull request #7093: Address mempool information leak and resource wasting attacks. (master...mempool_infoleak) https://github.com/bitcoin/bitcoin/pull/7093
< GitHub27>
[bitcoin] MarcoFalke closed pull request #8072: travis: 'make check' in parallel and verbose (master...Mf1605-travisMakeCheck) https://github.com/bitcoin/bitcoin/pull/8072
< GitHub114>
bitcoin/master 1b87e5b MarcoFalke: Merge #8072: travis: 'make check' in parallel and verbose...
< GitHub114>
bitcoin/master 401ae65 Cory Fields: travis: 'make check' in parallel and verbose...
< GitHub20>
[bitcoin] gmaxwell closed pull request #7082: Do not absolutely protect local peers and make eviction more aggressive. (master...evict_more) https://github.com/bitcoin/bitcoin/pull/7082
< tErik_mc>
Quick Scan (with Comodo Internet Security) was already done twice by now, nothing fishy so far. By the way, i did not allow Comodo to use Cloud scanning inside the bitcoin folders, if for some reason it uploads wallet.dat or something into cloud. i kknow, it uploads file-hashes into cloud for analysis, and on positive detection it also uploads the file into their cloud.
< tErik_mc>
And i know the list of APPD which installed this/such malware . i installed Python27, OpenBazaar, Bitcoin, NetBalancer, etc.
< tErik_mc>
if i shutdown bitcoin-qt, and delete the existing wallet.dat file, and restart bitcoing-qt, then would it create a completely new wallet (with fresh new private keys & pubkeys) ?
< phantomcircuit>
#bitcoin
< tErik_mc>
So, i'm trying to make sure, that bitcoin default wallet is using fresh new priv.keys.
< tErik_mc>
yes, new wallet address. but i need to explain why i'm asking for this. I found out, after installing few apps related to Openbazaar & Bitcoin, suddenly my C:\Users\ folder became a "Shared" folder, and previously it was not. Then i disabled bunch of wifi related services in this computer. i wasn't using wifi. its using wired connection now, when i setup openbazaar & bitcoin. but before these it was using wifi.
< phantomcircuit>
#bitcoin
< tErik_mc>
Please point me to an article or help me with creating a wallet in this bitcoin-qt.
< tErik_mc>
s / e.bitcoin.it / en.bitcoin.it /
< tErik_mc>
bitcoin-qt sometimes trying to connect with TCP 9051 !!! is that the Tor proxy controller port ?
< tErik_mc>
i see, then i will create it on my own. i need to use the bitcoin-core, also to accept bitcoin in my own wallet, so how would i exactly create wallet ? i'm still confused after reading this: https://e.bitcoin.it/wiki/Running_Bitcoin
< tErik_mc>
I looked again now, according to ComodoInternetSecurity, bitcoin-qt.exe has 8 TCP OUT connections, but other apps are shoing it has TOTAL 14 connections, etc.
< gmaxwell>
tErik_mc: no, there is no need for a bitcoin.conf usually. it will never make it on its own. if you need one, you must create it.
< tErik_mc>
i do not see existance of bitcoin.conf inside any of these folders ! C:\Program Files\Bitcoin\ or C:\Users\WINDOWS-USERNAME\AppData\Roaming\Bitcoin\
< tErik_mc>
And pls display in https://bitcoin.org/en/download webpage, that bitcoin-core needs inbound TCP port 8333, open/forwarded in router+firewall, pls dont mention only "Port 8333", thats confusing. What else port bitcoin-core needs, other than tcp 8333 as inbound ? and what ports i should allow in firewall as its outbound port, other than tcp 8333 ?
< tErik_mc>
By the way, do bitcoin-core changes the C:\Users\ folder in windows, into a "Shared" folder ? it must not do that.
< GitHub87>
[bitcoin] laanwj closed pull request #8033: Fix Socks5() connect failures to be less noisy and less unnecessarily scary (master...proxy_fail_too_scary) https://github.com/bitcoin/bitcoin/pull/8033
< luke-jr>
otebuv: Bitcoin Core does indeed have a wallet builtin
< otebuv>
@luke-jr what about wallet/addresses functionality can i create new wallet addresses with bitcoin-core
< luke-jr>
(BlueMatt added Core-imitation logic implementing the actual Bitcoin protocol in BitcoinJ years ago, but AFAIK it's likely buggy and outdated by now)
< luke-jr>
otebuv: Bitcoin Core implements (and defines) the actual Bitcoin protocol, whereas BitcoinJ just has enough to trust a remote Bitcoin Core node
< otebuv>
what are the main differences between bitcoin-core and bitcoinj in terms of functionality
< GitHub126>
bitcoin/master 457b9df Wladimir J. van der Laan: Merge #8031: improvement to readability...
< GitHub126>
bitcoin/master fe80102 Matthew English: changing "(tests are) automatically run" to correspond to the earlier instance of "run automatically (on the build server)"
< GitHub150>
[bitcoin] theuni opened pull request #8067: travis: use slim generic image, and some fixups (master...travis-generic-image) https://github.com/bitcoin/bitcoin/pull/8067
< gmaxwell>
and saw the "Editors note: Shortly before publication, Bitcoin Core developers pointed out that an RBF-notification might be added soon, after all." and was confused by that.
< gmaxwell>
I've been contacting Jeff for months in private raising my concerns about his unproductive tyrades-- seemingly motivated by creating drama to bring attention to his business-- while he continues to contribute no ongoing technical work the the bitcoin ecosystem. Most of my emails have gone unresponded or not meaningfully responded.
< GitHub50>
[bitcoin] MarcoFalke opened pull request #8066: [qa] test_framework: Use different rpc_auth_pair for each node (master...Mf1605-qaAuthPairDiff) https://github.com/bitcoin/bitcoin/pull/8066
< GitHub130>
bitcoin/master 5c3f8dd Pieter Wuille: Merge #7696: Fix de-serialization bug where AddrMan is left corrupted...
< kanzure>
we don't mention in our docs "don't connect to your bitcoin node from a thousand workers that listen for notifications"
< luke-jr>
we're moving the dev meetings to the p2p network and using longpolling with bitcoin-cli to read the chat? :P
< jonasschnelli>
jcorgan: Agree. You could start a discussion on the bitcoin-core-dev ML?
< kanzure>
some feedback from d4de- he recommends that future bitcoin core meetings shoud have someone that more actively guides discussion, e.g. make things more explicit rather than implicit
< wumpus>
I'm kind of divided on the notification thing to be honest - I'd prefer to stick to only one notification mechanism in bitcoin core (apart from the silly -Xnotify), and somehow zmq got a precedent there
< GitHub116>
[bitcoin] laanwj closed pull request #7841: Expose information on whether transaction relayed is enabled in getnetwork (master...patch-2) https://github.com/bitcoin/bitcoin/pull/7841
< GitHub159>
[bitcoin] laanwj opened pull request #8049: Expose information on whether transaction relayed is enabled in `getnetwork` (master...2016_05_rpc_relaytxes) https://github.com/bitcoin/bitcoin/pull/8049
< GitHub194>
[bitcoin] laanwj opened pull request #8048: doc: Remove outdated qt4 install information from README.md (master...2016_05_doc_noqt4) https://github.com/bitcoin/bitcoin/pull/8048
< GitHub15>
[bitcoin] jonasschnelli closed pull request #8046: [Qt][OSX] Fix Cmd-Q / Menu Quit shutdown on OSX (master...2016/05/fix_quit) https://github.com/bitcoin/bitcoin/pull/8046
< GitHub130>
bitcoin/master 169d379 Jonas Schnelli: Merge #8046: [Qt][OSX] Fix Cmd-Q / Menu Quit shutdown on OSX...
< GitHub130>
bitcoin/master 34ebceb Jonas Schnelli: [Qt][OSX] Fix Cmd-Q / Menu Quit shutdown on OSX
< GitHub29>
[bitcoin] laanwj closed pull request #8004: signal handling: fReopenDebugLog and fRequestShutdown should be type sig_atomic_t (master...fix_signal_handler) https://github.com/bitcoin/bitcoin/pull/8004
< GitHub57>
bitcoin/master 2efe38b Wladimir J. van der Laan: Merge #8004: signal handling: fReopenDebugLog and fRequestShutdown should be type sig_atomic_t...
< GitHub57>
bitcoin/master 3262316 Chirag Davé: fReopenDebugLog and fRequestShutdown should be type sig_atomic_t...
< GitHub176>
[bitcoin] jonasschnelli opened 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
< jonasschnelli>
AaronvanW: you'll find him in #secp256k1 or in #bitcoin-wizards
< wumpus>
at the least, GPUs became a lot better with integer operations compared to the time I used it a lot, partially thanks to bitcoin mining :-)
< jonasschnelli>
I'm impressed how bitcoin-core does perform on a 29$ computer (Pine64). Progress=0.5~ in <24h. dbcache=1500. Using a cheap/slow USB stick.
< GitHub94>
[bitcoin] wtogami opened pull request #8033: Fix Socks5() connect failures to be less noisy and unnecessarily scary (master...proxy_fail_too_scary) https://github.com/bitcoin/bitcoin/pull/8033
< GitHub123>
bitcoin/master b02119e Pavel Janík: Remove useless argument to AlertNotify....
< jonasschnelli>
The idea I had with resize the caches was that Bitcoin-Qt could ask for a db cache size during first run (like the datadir), then It could allocate ~>1GB, after IBD it could reduce it back to 100MB.
< GitHub96>
[bitcoin] laanwj opened pull request #8030: test: Revert fatal-ness of missing python-zmq (master...2016_05_revert_zmq_req_tests) https://github.com/bitcoin/bitcoin/pull/8030
< GitHub10>
[bitcoin] laanwj closed pull request #7976: Remove obsolete reference to CValidationState from UpdateCoins. (master...cleancoinsupdate) https://github.com/bitcoin/bitcoin/pull/7976
< GitHub128>
bitcoin/master e29cfc4 Wladimir J. van der Laan: Merge #7976: Remove obsolete reference to CValidationState from UpdateCoins....
< GitHub128>
bitcoin/master c8b9248 21E14: Remove obsolete reference to CValidationState from UpdateCoins.