< dufferzafar>
okay, is it bitcoin-help? i saw this channel mentioned on slack, so came here
< wumpus>
it's fine as long as you don't go arguing how bitcoin's P2P protocol works...
< wumpus>
I think you need to read up on how your tooling is used with other TCP protocols, it's not really different for bitcoin
< dufferzafar>
so, the ports 12192 & 12476 are the ones the two bitcoin processes (btc1 & btc2) are listening on
< dufferzafar>
i'm doing some network measurement experiments on bitcoin
< dufferzafar>
i have bitcoin daemons running on multiple machines
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #15197: Refactor and slightly stricter p2p message processing (master...2019/01/netmsg_1) https://github.com/bitcoin/bitcoin/pull/15197
< luke-jr>
Alixe: this is not "talk to devs", it is "talk about development", and your question is not about development. some of us are in #bitcoin too
< sipa>
#bitcoin
< Alixe>
So I think mining hash power can't do anything because full nodes enforce consensus rules. But some people think governments or corporates can buy a lot of nodes to affect Bitcoin with having majority of full nodes. Is it possible?
< bitcoin-git>
[bitcoin] gkrizek opened pull request #15196: Update all subprocess.check_output functions to be Python 3.4 compatible (master...cron-ci-fix) https://github.com/bitcoin/bitcoin/pull/15196
< gwillen>
just replacing it with some kind of simple fixed notice with a pointer to the COPYING file, without varying years or names other than "the Bitcoin developers" or what have you
< bitcoin-git>
[bitcoin] practicalswift opened pull request #15191: validation: Add missing cs_LastBlockFile locks in PruneAndFlush() and UnloadBlockIndex(). Add missing locking annotation for nLastBlockFile and fCheckForPruning. (master...cs_LastBlockFile) https://github.com/bitcoin/bitcoin/pull/15191
< sipa>
gwillen: IANAL but i believe those copyright statements per file (and much less the year indications) are almost certainly worthless, especially when attributing to "The Bitcoin Core developers", which is not a legal entity
< bitcoin-git>
[bitcoin] practicalswift opened pull request #15187: fees: Complete the removal of fee-estimation file read code for old versions (master...fee-estimation) https://github.com/bitcoin/bitcoin/pull/15187
< wumpus>
https://travis-ci.org/bitcoin/bitcoin/jobs/480544456 the only visible warning is the one about a missspelling in fuzzing.md, however that's an old warning and also spelling errors don't cause the test to fail
< bitcoin-git>
bitcoin/master b9dafe7 practicalswift: Fix remaining compiler warnings (MSVC). Move disabling of specific warnings from /nowarn to project file.
< bitcoin-git>
bitcoin/master 19c60ca Wladimir J. van der Laan: Merge #14151: windows: Fix remaining compiler warnings (MSVC)...
< bitcoin-git>
[bitcoin] laanwj closed pull request #14409: utils and libraries: Make 'blocksdir' always net specific (master...20181005-blockspath-always-netspecific) https://github.com/bitcoin/bitcoin/pull/14409
< bitcoin-git>
[bitcoin] laanwj closed pull request #14958: qa: Remove race between connecting and shutdown on separate connections (master...2018-12-improve-shutdown-test) https://github.com/bitcoin/bitcoin/pull/14958
< bitcoin-git>
bitcoin/master 4412a59 João Barbosa: qa: Remove race between connecting and shutdown on separate connections
< bitcoin-git>
bitcoin/master 3ae3748 Wladimir J. van der Laan: Merge #14958: qa: Remove race between connecting and shutdown on separate connections...
< gribble>
https://github.com/bitcoin/bitcoin/issues/14958 | qa: Remove race between conneting and shutdown on separate connections by promag · Pull Request #14958 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] promag opened pull request #15177: doc: Explain empty result of /rest/headers (master...2019-01-restheadersdoc) https://github.com/bitcoin/bitcoin/pull/15177
< bitcoin-git>
bitcoin/master 3537c83 Hennadii Stepanov: Do not deselect peer when switching away from tab...
< bitcoin-git>
bitcoin/master acec9e4 Wladimir J. van der Laan: Merge #15136: qt: "Peers" tab overhaul...
< bitcoin-git>
[bitcoin] laanwj closed pull request #15165: contrib: Allow use of github API authentication in github-merge (master...2019_01_ghmerge) https://github.com/bitcoin/bitcoin/pull/15165
< gribble>
https://github.com/bitcoin/bitcoin/issues/14978 | Factor out PSBT utilities from RPCs for use in GUI code; related refactoring. by gwillen · Pull Request #14978 · bitcoin/bitcoin · GitHub
< bitcoin-git>
bitcoin/master f411c8b João Barbosa: gui: Remove unused return type in some BitcoinGUI methods
< bitcoin-git>
bitcoin/master 8a79261 João Barbosa: gui: Keep network style in BitcoinGUI
< bitcoin-git>
bitcoin/master fe7048b João Barbosa: gui: Show current wallet name in window title
< bitcoin-git>
[bitcoin] jonasschnelli closed pull request #15149: gui: Show current wallet name in window title (master...2019-01-updatewindowtitle) https://github.com/bitcoin/bitcoin/pull/15149
< gribble>
https://github.com/bitcoin/bitcoin/issues/14958 | qa: Remove race between conneting and shutdown on separate connections by promag · Pull Request #14958 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] koalaman opened pull request #15170: refactor/lint: Add ignored shellcheck suggestions to an array (master...master) https://github.com/bitcoin/bitcoin/pull/15170
< bitcoin-git>
[bitcoin] sdaftuar opened pull request #15169: WIP: Parallelize CheckInputs() in AcceptToMemoryPool() (master...2018-12-parallel-mempool-scriptchecks) https://github.com/bitcoin/bitcoin/pull/15169
< kanzure>
/join #bitcoin-wizards
2019-01-14
< gribble>
https://github.com/bitcoin/bitcoin/issues/14978 | Factor out PSBT utilities from RPCs for use in GUI code; related refactoring. by gwillen · Pull Request #14978 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] promag closed pull request #15107: rest: Return 404 in /rest/headers if block hash does not exists (master...2019-rest-header-404) https://github.com/bitcoin/bitcoin/pull/15107
< gribble>
https://github.com/bitcoin/bitcoin/issues/54 | do not create "Your Address" account when creating a new wallet by tcatm · Pull Request #54 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/54 | do not create "Your Address" account when creating a new wallet by tcatm · Pull Request #54 · bitcoin/bitcoin · GitHub
< luke-jr>
CODER82: your question doesn't really make sense, and in any case belongs in #bitcoin
< TokenHash>
"money is a social system, therefore it's ok to integrate social management tools in Bitcoin such as 'invalidateblock' and others" is a fallacy.
< gmaxwell>
if the signature is correct, you're good to go, unfortunately people maliciously submit bitcoin core as viruses to av companies and they don't give a crap about giving accurate results...
< gribble>
https://github.com/bitcoin/bitcoin/issues/15150 | gui: Show wallet selector on console window if there are wallets loaded by promag · Pull Request #15150 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/10540 | [WIP] Salvage wallet should not set the aggressive flag on Db::verify() by jnewbery · Pull Request #10540 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/14978 | Factor out PSBT utilities from RPCs for use in GUI code; related refactoring. by gwillen · Pull Request #14978 · bitcoin/bitcoin · GitHub
< achow101>
so hwi is currently under my account. but if we are going to use it for hardware wallet support in core, then perhaps it would be better to have it under a proper github org. the obvious one that comes to mind is bitcoin-core
< wumpus>
#topic moving hwi under bitcoin-core org (achow101)
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< wumpus>
gkrizek: there's not that much configuration; server is chat.freenode.net port is 6697, room is "#bitcoin-commits,#bitcoin-core-dev", nick is "bitcoin-git", branches is "master,0.11,0.12,0.13,0.14,0.15,0.16,0.17"
< luke-jr>
echeveria: Bitcoin intentionally doesn't support such timeouts
< gmaxwell>
At the time BIP70 was written, the only 'used' metric bitcoin core really had was "spent by the mempool"
2019-01-09
< gmaxwell>
roasbeef: their bip70 violates the spec and can't be used with bitcoin core regardless.
< jarthur>
Stripe had thrown its support in, prior to taking a break from Bitcoin point of sale.
< gkrizek>
wumpus: fanquake: I'd be happy to help migrate any tooling from GitHub Services to an App or API/Webhook. I'd imagine that would require Bitcoin Core org permissions though...
< jarthur>
relligions: this is the development/operations channel for a popular Bitcoin reference client, the altcoin chat is off-topic and getting in the way. That's why you'd be banned.