< wumpus>
CodeShark: I remember you were planning to use bitcoin core's rpc system in another project - you may like https://github.com/bitcoin/bitcoin/pull/7766, it removes further bitcoin-specific logic from rpc/server.cpp
< GitHub186>
[bitcoin] MarcoFalke opened pull request #7767: [qa] add test: Deserialize getblock result (master...Mf1603-qaMininodeDeser) https://github.com/bitcoin/bitcoin/pull/7767
< GitHub158>
[bitcoin] laanwj opened pull request #7766: rpc: Register calls where they are defined (master...2016_03_separate_rpc_registration) https://github.com/bitcoin/bitcoin/pull/7766
< wumpus>
this can be somewhat more beefy, but not requires deep understanding of bitcoin core itself
< MarcoFalke>
So when someone want to "try out" patching something in bitcoin, they can jsut grab an easy issue
< GitHub188>
[bitcoin] jonasschnelli opened pull request #7762: [ZMQ] append a message sequence number to every ZMQ notification (master...2016/03/zmq_seq) https://github.com/bitcoin/bitcoin/pull/7762
< GitHub90>
[bitcoin] jonasschnelli opened pull request #7761: [Qt] remove trailing output-index from transaction-id (master...2016/03/ui_txid) https://github.com/bitcoin/bitcoin/pull/7761
< GitHub91>
[bitcoin] MarcoFalke opened pull request #7757: [qa] wallet: Wait for reindex to catch up (master...Mf1603-qaWalletReindex) https://github.com/bitcoin/bitcoin/pull/7757
< GitHub123>
[bitcoin] laanwj opened pull request #7756: Add cursor to iterate over utxo set, use this in `gettxoutsetinfo` (master...2016_03_utxo_cursor) https://github.com/bitcoin/bitcoin/pull/7756
< GitHub100>
bitcoin/master 84370d5 Wladimir J. van der Laan: Merge #7751: test_framework: python3.4 authproxy compat...
< Chris_Stewart_5>
How does bitcoin core handle the behavior of an undefined hash type for an OP_CHECKSIG op code? Is it just ignored if it isn't a predefined hash type?
< GitHub25>
[bitcoin] laanwj opened pull request #7744: test_framework: detect failure of bitcoind startup (master...2016_03_detect_startup_failure) https://github.com/bitcoin/bitcoin/pull/7744
< wumpus>
hm re: https://github.com/bitcoin/bitcoin/issues/7463, it seems that if bitcoind never spins up RPC (for example, if init failures) the successive bitcoin-cli -rpcwait getblockcount will wait forever
< wumpus>
that's true, that is a reason why one would run multiple versions of bitcoin core, some people indeed do that
< wumpus>
also philosophically, upgrading bitcoin core should be a conscioius decision. You may or may not agree with any consensus changes.
< wumpus>
and for example it doesn't help bug reporting *at all* if some distribution, in its stable release, keeps shipping bitcoin 10.2 forever. We'd get tons of reports against old versions, for bugs that have probably been solved ages ago.
< wumpus>
I'm quite happy that bitcoin isn't packaged by distributions - we had some bad experiences in the past with ubuntu's bitcoin package being stuck at 0.3.x, for example.
< demaged>
besideds, what's the reason bitcoin isn't migrating to testing, stuck in ustable for years now :/
2016-03-24
< GitHub149>
[bitcoin] luke-jr opened pull request #7743: [0.11] Important backports for 0.11.3 (updated to v0.12.0) (0.11...backports-for-0.11.3) https://github.com/bitcoin/bitcoin/pull/7743
< GitHub139>
[bitcoin] luke-jr closed pull request #7047: [WIP] Backports for 0.11.3 (updated to 93ca5a3) (0.11...backports-for-0.11.3) https://github.com/bitcoin/bitcoin/pull/7047
< GitHub178>
[bitcoin] jonasschnelli opened pull request #7742: [Wallet][RPC] add missing abandon status documentation (master...2016/03/ab_doc) https://github.com/bitcoin/bitcoin/pull/7742
< wumpus>
even getting the bitcoin dependencies deterministic was a hell of a lot of work, just imagine for a full OS
< wumpus>
jonasschnelli: scope creep is a very bitcoin-y thing
< wumpus>
<sipa> which means that an attacker can't even see the message sizes, except by traffic analysis <- I think that would be quite essential for bitcoin, as so much can already be identified from the packet sizes
< GitHub17>
[bitcoin] laanwj closed pull request #7506: Use CCoinControl selection in CWallet::FundTransaction (master...enhancement/use-coin-control-selection) https://github.com/bitcoin/bitcoin/pull/7506
< GitHub55>
bitcoin/master b88e0b0 Wladimir J. van der Laan: Merge #7506: Use CCoinControl selection in CWallet::FundTransaction...
< GitHub55>
bitcoin/master d6cc6a1 João Barbosa: Use CCoinControl selection in CWallet::FundTransaction
< GitHub36>
[bitcoin] laanwj closed pull request #7609: All files related to my RPM spec file project in one commit (master...master) https://github.com/bitcoin/bitcoin/pull/7609
< GitHub121>
bitcoin/master 3ba07bd Wladimir J. van der Laan: Merge #7609: All files related to my RPM spec file project in one commit...
< GitHub121>
bitcoin/master 0e4b50a Alice Wonder: Description of RPM directory
< GitHub121>
bitcoin/master 146746b Alice Wonder: All files related to my RPM spec file project in one commit
< wumpus>
I think it's safe to say there won't be so many bitcoin nodes in datacenters to rival the number of https implementations, let alone be a power usage concern
< wumpus>
then again - for bitcoin nodes we need to worry about consumer hw, not so much big datacenters
< gmaxwell>
the only software ever created that does that is bitcoin core.
< sipax>
jonasschnelli: bitcoin does
2016-03-23
< gmaxwell>
hm. so I have a node that was offline for a week throwing "Bitcoin is downloading blocks" -- it's not caught up, and yet it shows no blocks inflight on any peers
< BCB>
Any idea why bitcoin 0.12 would be disconnection from an ipv6 addy with "socket recv error Connection reset by peer (104)" after receiving pong message
< jonasschnelli>
I need to go afk. Happy to discuss that more in detail later. Thanks for the feedback, also happy to get feedback on the bitcoin-dev mail.
< gmaxwell>
as far as the auth goes, I think for bitcoin symmetric mutual auth is not really a perfect fit; -- often the connection-accepting side wants to know that their resources are not being wasted by sybils, but don't really care who it is otherwise... and clients want to know they're talking to the host they expect, but really don't want it to know who they are. The exception is basically when you
< gmaxwell>
jonasschnelli: what sipa and I are referring to is that we don't want bitcoin nodes sending data that distinguishes them (esp passively) from other nodes.
< sipa>
jonasschnelli: if i would redesign bitcoin p2p it would always be authenticated and always encrypted
< GitHub140>
[bitcoin] laanwj closed pull request #7740: [0.12 BP] [Wallet][RPC] add abandoned status to listtransactions (0.12...2016/03/aba_rpc_012) https://github.com/bitcoin/bitcoin/pull/7740
< GitHub170>
bitcoin/0.12 7ffc2bd Jonas Schnelli: [Wallet][RPC] add abandoned status to listtransactions...
< wumpus>
if there are to be any bounties in the bitcoin core project ever it'd be for reviewing code, that's by far the most difficult thing to motivate people to do
< GitHub160>
bitcoin/0.12 19866c1 Alex Morcos: Fix calculation of balances and available coins....
< wumpus>
in any case if anyone actually wants to support bitcoin core on XP, be my guest, you're welcome, but don't simply expect it from others
< GitHub103>
[bitcoin] laanwj opened pull request #7737: devtools: make github-merge.py use py3 (master...2016_03_python_3_github_merge) https://github.com/bitcoin/bitcoin/pull/7737
< GitHub185>
[bitcoin] jonasschnelli opened pull request #7732: [Qt] Debug window: replace "Build date" with "Datadir" (master...2016/03/qt_datadir) https://github.com/bitcoin/bitcoin/pull/7732
2016-03-21
< jtimon>
morcos: wumpus: MarcoFalke this is what I meant the other day, I'm sorry it took me days to have something that could potentially make some sense: https://github.com/bitcoin/bitcoin/pull/7731
< GitHub31>
[bitcoin] jtimon opened pull request #7731: Discussion: By "more precision", I don't mean using rational numbers in CFeeRate (master...0.12.99-feerate) https://github.com/bitcoin/bitcoin/pull/7731
< GitHub50>
[bitcoin] jtimon opened pull request #7728: Fees: Tests: Check CFeeRate internal precision in mempool_tests.cpp (master...0.12.99-feerate-precision-test) https://github.com/bitcoin/bitcoin/pull/7728
< GitHub114>
[bitcoin] jtimon opened pull request #7727: Travis test (not to merge): Introduce silent bug in CFeeRate (master...0.12.99-feerate-test-bug) https://github.com/bitcoin/bitcoin/pull/7727
< moli>
yes, i guess i like to do it my way so i can remember where i put it, and i notice you have bitcoin.conf.5 in your bitcoin-segwit, i wish we could have bitcoin.conf in windows download package
< moli>
and bitcoin.conf doesn't come with the download package, i have to create it and then put it in Bitcoin folder
< moli>
so in the folder Bitcoin it has wallet.dat, bitcoin.conf, etc
< moli>
sipa, i don't use the default, so my datadir is something like this: C:\bitcoin-0.12.0\bin\bitcoin-qt.exe -datadir=C:\Bitcoin
< moli>
oops, i meant bitcoin.conf
< moli>
sipa, i'm not sure if you're looking for bitcoin-conf, but on windows by default it's in: C:\Users\UserName\AppData\Roaming\Bitcoin\bitcoin-conf
< morcos>
mine is in ~/.config/Bitcoin/Bitcoin-Qt.conf
2016-03-20
< sipa>
wumpus, jonasschnelli: is there any way to check what datadir a Bitcoin-Qt was configured to use?
< GitHub85>
[bitcoin] morcos opened pull request #7716: [0.12] Backport BIP9 and softfork for BIP's 68,112,113 (0.11...backportBIP9SoftFork) https://github.com/bitcoin/bitcoin/pull/7716
< wumpus>
morcos: oh no, you found a bitcoin cheat code :D
< GitHub85>
[bitcoin] morcos closed pull request #7706: [WIP] Fix calculation of balances and available coins. (master...fixconflicts2) https://github.com/bitcoin/bitcoin/pull/7706
< GitHub7>
[bitcoin] morcos opened pull request #7715: Fix calculation of balances and available coins. (master...fixconflicts_take2) https://github.com/bitcoin/bitcoin/pull/7715
< jtimon>
too much unnecessary disruption to get to this result, so I had to reduce it to something more readable. After many apparently false positives (I knew the rpc tests couldn't possibly let pass some of the things I did), https://github.com/jtimon/bitcoin/tree/0.12.99-feerate-test-bug it's basically what I have, but I still won't push my not-to-be-merged point about CFeeRate having "bad aji" which I'm still not sure I'm right about