< 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
< paveljanik>
I probably won't be able to join the beginning of the meeting again. Suggested topic: Qt 5.6 support. Bitcoin Core doesn't compile with it, because Qt 5.6 dropped almost all pkgconfig files, so configure fails.
< GitHub169>
[bitcoin] morcos opened pull request #7706: [WIP] Fix calculation of balances and available coins. (master...fixconflicts2) https://github.com/bitcoin/bitcoin/pull/7706
< GitHub167>
[bitcoin] laanwj opened pull request #7703: tor: Change auth order to only use HASHEDPASSWORD if -torpassword (master...2016_03_auth_order) https://github.com/bitcoin/bitcoin/pull/7703
< GitHub33>
bitcoin/master 982670c Alex Morcos: Add LockPoints...
< GitHub110>
[bitcoin] MarcoFalke closed pull request #7661: [wallet] Round up to the next satoshi on odd fee rates (master...Mf1603-walletCeil) https://github.com/bitcoin/bitcoin/pull/7661
< GitHub37>
[bitcoin] MarcoFalke closed pull request #7660: [amount] Extend GetFee() by optional flag ceil (master...Mf1603-amountCeil) https://github.com/bitcoin/bitcoin/pull/7660
< wumpus>
bitcoin.org has extensive infrastructure for documentation, don't think bitcoincore.org has
< MarcoFalke>
but bitcoin/bitcoin commits are read by somewhat more people than the website commits
< morcos>
anywya, we're not talking about using doubles for an amount, i think everyone would 100% agree, that no bitcoin amount should ever be represented as a double (bitcoins.satoshis)
< MarcoFalke>
Using doubles for bitcoin should be fine right now, as a double can hold all possible values with exact precision IIRC.
< GitHub103>
[bitcoin] laanwj closed pull request #7697: Tests: make prioritise_transaction.py more robust (master...fix-prioritise-transaction) https://github.com/bitcoin/bitcoin/pull/7697
< GitHub116>
bitcoin/master 622fe6c Wladimir J. van der Laan: Merge #7697: Tests: make prioritise_transaction.py more robust...
< GitHub116>
bitcoin/master ec14339 Suhas Daftuar: Tests: make prioritise_transaction.py more robust
< Chris_Stewart_5>
thanks guys, If I am understanding this correctly, we would have to deploy another soft fork to make this signature valid again for bitcoin core nodes? Are the flags in the test case used ONLY for these test cases or is there similar flags used in bitcoin core's interpreter?
< Chris_Stewart_5>
Hi guys, I know this isn't the correct channel, but I figured some one in this channel might be able to answer my question - i've already tried #bitcoin-dev
< GitHub25>
[bitcoin] sdaftuar opened pull request #7697: Tests: make prioritise_transaction.py more robust (master...fix-prioritise-transaction) https://github.com/bitcoin/bitcoin/pull/7697
< GitHub1>
[bitcoin] EthanHeilman opened pull request #7696: Fix de-serialization bug where AddrMan is left corrupted (master...bug) https://github.com/bitcoin/bitcoin/pull/7696
< GitHub87>
[bitcoin] sipa opened pull request #7689: Replace OpenSSL AES with our own constant-time version (edit of #5949) (master...const_aes) https://github.com/bitcoin/bitcoin/pull/7689
< GitHub73>
[bitcoin] sipa opened pull request #7688: List solvability in listunspent output and improve help (master...helpspendsolv) https://github.com/bitcoin/bitcoin/pull/7688
< GitHub155>
bitcoin/master c87f51e Wladimir J. van der Laan: Merge #7663: Make the generate RPC call function for non-regtest...
< GitHub3>
[bitcoin] laanwj closed pull request #7663: Make the generate RPC call function for non-regtest (master...generatenonreg) https://github.com/bitcoin/bitcoin/pull/7663
< GitHub155>
bitcoin/master 8a253b3 Pieter Wuille: Make the generate RPC call function for non-regtest
< GitHub154>
[bitcoin] laanwj opened pull request #7676: torcontrol: rename global base, avoid overlap with field (master...2016_03_torcontrol_rename_base) https://github.com/bitcoin/bitcoin/pull/7676
< GitHub16>
[bitcoin] achow101 opened pull request #7668: Fix history deletion bug after font size change (master...rpcconsole-hist-fix) https://github.com/bitcoin/bitcoin/pull/7668
< GitHub23>
[bitcoin] laanwj closed pull request #7640: Removes forward slash (/) from user agent in peers tab UI. (master...master) https://github.com/bitcoin/bitcoin/pull/7640
< GitHub55>
[bitcoin] laanwj closed pull request #7553: Remove vfReachable and modify IsReachable to only use vfLimited. (master...2016-02-17-reachable) https://github.com/bitcoin/bitcoin/pull/7553
< GitHub32>
bitcoin/master 9f14e5a Wladimir J. van der Laan: Merge #7553: Remove vfReachable and modify IsReachable to only use vfLimited....
< achow101>
well it looks like the rpc tests do have regtest mining stuff there, but I'm not sure that it will work well with not being in the Bitcoin Core project.
< achow101>
warren: I suppose I could do that, but that just make things annoying since this is just for rpc tests for Armory. Do you know if the Bitcoin Core rpc tests have mining implmented in them? If so I can just borrow that
< achow101>
Is there any way in Bitcoin Core to mine to a specific address when in regtest mode?
< GitHub191>
[bitcoin] MarcoFalke opened pull request #7666: [0.12.1] Fix doc and output for rpcauth (0.12...Mf1603-012fixdocrpcauth) https://github.com/bitcoin/bitcoin/pull/7666
< GitHub50>
[bitcoin] jtimon opened pull request #7665: Contrib: Introduce script to tag compiled binaries for convenience (py) (master...0.12.99-contrib-tag) https://github.com/bitcoin/bitcoin/pull/7665
< GitHub45>
[bitcoin] sipa opened pull request #7663: Make the generate RPC call function for non-regtest (master...generatenonreg) https://github.com/bitcoin/bitcoin/pull/7663