< GitHub34>
[bitcoin] laanwj closed pull request #7021: add bip65 tests to rpc-tests.sh -extended (in 0.11 branch) (0.11...11rpcfixups) https://github.com/bitcoin/bitcoin/pull/7021
< GitHub101>
[bitcoin] gmaxwell closed pull request #6991: Minor: Clarify 'fee' field in fundrawtransaction help text (master...clarify-fundrawtransaction-help) https://github.com/bitcoin/bitcoin/pull/6991
< GitHub194>
bitcoin/master 9bd3f03 Peter Todd: Clarify 'fee' field in fundrawtransaction help text...
< gmaxwell>
for me bitcoin core sync runs at around 8000tx/s (with secp256k1), even though every tx is involving a non-cachable missing record check for bip30 (in addition to all the cached stuff)... thats really quite remarkable IMO.
< gmaxwell>
FWIW, I've unsubscribed from bitcoin-dev mailing list.
< gmaxwell>
yes, not a risk for us but we'll probably get asked to update when people notice bitcoin-qt links it.
< GitHub184>
[bitcoin] morcos opened pull request #7020: Implement helper class for CTxMemPoolEntry constructor (master...EntryHelper) https://github.com/bitcoin/bitcoin/pull/7020
< gmaxwell>
Well it's also a bit #bitcoin-core-dev too, in that I think it would be useful if work were done in the GUI to make mining fun, ... but probably more than that is just speculation :)
< gmaxwell>
also it suggests a framework for setting minimum feerates which are independant of bitcoin's price-- though dependant on communications efficiency, which is perhaps no better. :)
< GitHub50>
[bitcoin] morcos closed pull request #6292: Rename and comment priority calculation in TxMemPoolEntry (master...PriorityComment) https://github.com/bitcoin/bitcoin/pull/6292
< GitHub101>
[bitcoin] gmaxwell opened pull request #7016: Avoid a compile error on hosts with libevent too old for EVENT_LOG_WARN. (master...without_EVENT_LOG_WARN) https://github.com/bitcoin/bitcoin/pull/7016
< gmaxwell>
morcos: the relay network has its own protocol, and a local proxy you run that speaks bitcoin p2p.
< tulip>
morcos: there's also stratum proxies like bfgminer and stratum-mining-proxy which present work to downstream miners, based on either an upstream work server or a Bitcoin node. the latter was meant for use with early hardware miners which supported getwork but not stratum.
< gmaxwell>
(Forrestv seems to have flamed out due to a mixture of bitcoin drama, and then donations to support p2pool being relatively low (compared to life changing amounts of income centeralized pool operators were getting), and then he got ripped off ... twice, I think, by mining hardware makers.)
< gmaxwell>
Also through this time the developer burned out on Bitcoin, and only does life support maintaince on p2pool now.
< gmaxwell>
P2pool is nice idea with cute features, but has always struggled with the high startup cost of having to run a bitcoin node with it; and then high latency asics showed up (in particular, some of the early BFL products had 10%+ hashrate loss from 10 second retasking)
< gmaxwell>
morcos: well it's armored by bitcoin nodes in and out; not that there haven't been problems.
< gmaxwell>
Yes. It is. I tried to do it for bitcoin core eons ago, but the utility library was GPLed... they since changed the licensing.
< wumpus>
sure that's why I dont give "integrate it into bitcoin core" as an alternative, but say communicate through a pipe or socket
< gmaxwell>
But the biggest reason for the seperate process is to tear down development barriers. E.g. so someone can build a module without the scarryness in bitcoin core. :)
< GitHub21>
[bitcoin] jonasschnelli opened pull request #7006: [Qt] add startup option to reset Qt settings (master...2015/11/qt_resetsettings) https://github.com/bitcoin/bitcoin/pull/7006
< GitHub147>
[bitcoin] jgarzik opened pull request #7005: Add MAINTAINERS file, a user guide to code subsystems (master...2015_maintainer) https://github.com/bitcoin/bitcoin/pull/7005
< jonasschnelli>
[12:41:14] <Luke-Jr>jonasschnelli: why a new key? :/ <-- the new key is not really new, It's just the one that I use for bitcoin-dev posts, etc. The "old" key is used for non-bitcoin software-projects (and sadly, i have used it for gitian signatures)
< CodeShark>
if I whitelist a node, other than network/transport issues or misbehaving, is there ever any conceivable situation where the node could get disconnected by bitcoin core
< jgarzik>
morcos, the latter - I always travis in jgarzik/bitcoin on the merged tree before pushing
< gmaxwell>
I mean, I'm probably at fault for making people think that its the only way to get a fraud proof for spending non-existing coins, since in the very first writeup I suggest that https://en.bitcoin.it/wiki/User:Gmaxwell/features#Proofs
< gmaxwell>
it's been discussed in #bitcoin-wizards.
< Luke-Jr>
wangchun: let's chat in #bitcoin since there is conversation here already
< GitHub56>
[bitcoin] sdaftuar closed pull request #6992: [WIP] [Mempool] Add space for priority transactions (master...add-priority-to-mempool) https://github.com/bitcoin/bitcoin/pull/6992
< GitHub51>
bitcoin/master 09c1ae1 Wladimir J. van der Laan: torcontrol improvements and fixes...
< GitHub51>
bitcoin/master 2f796e5 Peter Todd: Better error message if Tor version too old
< GitHub51>
bitcoin/master 8f4e67f Wladimir J. van der Laan: net: Automatically create hidden service, listen on Tor...
< GitHub33>
[bitcoin] laanwj closed pull request #6639: net: Automatically create hidden service, listen on Tor (master...2015_08_tor_hs_v2) https://github.com/bitcoin/bitcoin/pull/6639
< GitHub29>
[bitcoin] jonasschnelli opened pull request #7000: [Qt] add shortcurts for debug-/console-window (master...2015/11/qt_shortcuts) https://github.com/bitcoin/bitcoin/pull/7000
< GitHub86>
[bitcoin] jonasschnelli opened pull request #6999: add (max)uploadtarget infos to getnetinfos RPC help (master...2015/11/maxuploadtarget_rpc_help) https://github.com/bitcoin/bitcoin/pull/6999
< GitHub55>
[bitcoin] laanwj opened pull request #6998: doc: Remove mention of pulltester from README.md (master...2015_11_readme_pull_pulltester) https://github.com/bitcoin/bitcoin/pull/6998
< GitHub93>
[bitcoin] sturles opened pull request #6997: Don't use hard-coded AllowFree, as this is usually far too low. (master...no-default-free-priority) https://github.com/bitcoin/bitcoin/pull/6997
< gmaxwell>
prior to bitcoin they were hard(er) because of flooding attacks, but we have a one-two punch here: we have highly valuable tiny messages AND mechenisms to stop flooding attacks.
< wumpus>
a tor bitcoin bundle would be pretty nice
< GitHub131>
[bitcoin] sdaftuar opened pull request #6992: [WIP] [Mempool] Add space for priority transactions (master...add-priority-to-mempool) https://github.com/bitcoin/bitcoin/pull/6992
< jgarzik>
btcdrak, release manager != project lead... bitcoin core is intentionally decentralized ever since Satoshi turned things over to Gavin.
< GitHub3>
[bitcoin] petertodd opened pull request #6991: Minor: Clarify 'fee' field in fundrawtransaction help text (master...clarify-fundrawtransaction-help) https://github.com/bitcoin/bitcoin/pull/6991
< GitHub167>
[bitcoin] laanwj closed pull request #6969: doc: there is no libboost-base-dev, add missing sudo in release notes (master...2015_11_docfix) https://github.com/bitcoin/bitcoin/pull/6969
< GitHub2>
bitcoin/master cbf9609 Wladimir J. van der Laan: Merge pull request #6969...
< GitHub2>
bitcoin/master 7085728 Wladimir J. van der Laan: doc: there is no libboost-base-dev, add missing sudo...
< GitHub21>
[bitcoin] fanquake opened pull request #6985: [gitian] Use latest vm-builder ( 0.12.4+bzr494 ) on Debian (master...patch-3) https://github.com/bitcoin/bitcoin/pull/6985
< wumpus>
for https://github.com/bitcoin/bitcoin/issues//2368 "Consider reducing 'getblocks' limit below 500" I have no idea whether it's still relevant, but the limit is still hardcoded to 500
< sipa>
warren: set a large dbcache, and start closing bitcoin-qt right before the crash
< GitHub126>
[bitcoin] jonasschnelli opened pull request #6984: don't enforce maxuploadtarget's disconnect for whitelisted peers (master...2015/11/maxupload_whitebind) https://github.com/bitcoin/bitcoin/pull/6984
< wumpus>
Luke-Jr: not just the return value, in multiple ways it doesn't behave the same on all platforms. we had issues due to that was well, one of the reasons why bitcoin core switched to a typesafe library for formatting that doesn't rely on libc
< warren>
Running Bitcoin Core v0.11.2rc1 with blank data dir on Windows 10 ... it connected to 9 peers including a local peer. Stuck at 0 blocks for the past 10 minutes. what should I try?
< phantomcircuit>
jtimon, there wouldn't happen to be a library somewhere of all the pure functions in bitcoin core would there?
2015-11-10
< sipa>
i think it makes sense for bitcoin-qt to do something smartish to guess how much memory to use for caches
< wumpus>
jgarzik: in case of bitcoin core that's noto the case, only still-unset settings get overridden
< GitHub60>
[bitcoin] laanwj closed pull request #6981: doc: Add note about SI units to developer notes (master...2015_11_si_units) https://github.com/bitcoin/bitcoin/pull/6981
< jgarzik>
There's a reason why I pushed Gavin hard for multiple committers when Satoshi disappeared - Gavin was release manager, not Bitcoin Leader
< Luke-Jr>
as long as sipa hates 1024 KB, and I prefer 1024 KB, there's no way to satisfy both without an option. If you all decide to make it 1000-based only, I can just add an option to Bitcoin LJR if I ever care enough (unlikely)
< GitHub159>
[bitcoin] laanwj opened pull request #6981: doc: Add note about SI units to developer notes (master...2015_11_si_units) https://github.com/bitcoin/bitcoin/pull/6981
< jgarzik>
wangchun, Scaling Bitcoin Pt 2 is the next step in figuring out uncontroversial hard fork
< sipa>
Bitcoin Core will implement any uncontroversial hard fork.
< wumpus>
but for bitcoin core which is a high-level application there shoulod be no reason to not just use SI units
< sipa>
bitcoin traditionally uses 1000-based units (feerate is per 1000 bytes, block limit is 1000000 bytes), but I can't say I've payed much attention to it myself
< GitHub4>
bitcoin/master b56953e Wladimir J. van der Laan: qt: Periodic translations update
< GitHub120>
[bitcoin] laanwj closed pull request #6693: Set Windows TCP buffers to 64KB to match OSX and Unix (master...issue_6554) https://github.com/bitcoin/bitcoin/pull/6693
< GitHub35>
bitcoin/master 755b4ba Wladimir J. van der Laan: Merge pull request #5574...
< GitHub67>
bitcoin/master c53d48a Jorge Timón: BIP70: Chainparams: DRY: Make qt/guiutil.cpp fit BIP70 chain name strings...
< gmaxwell>
wumpus: I heard from andytoshi that you've been keeping him honest on rust-bitcoin. :)
< wumpus>
yes that solves one problem but causes many others. We tried forcing the locale to C in bitcoin for a while but this messed with file name encodings on windows.
< GitHub138>
bitcoin/0.11 40941d9 David A. Harding: [Docs] First-draft release notes for 0.11.2RC1
< GitHub138>
bitcoin/0.11 929b2c7 David A. Harding: [docs] Minor revisions to 0.11.2RC1 release notes...
< GitHub138>
bitcoin/0.11 9149589 David A. Harding: [docs] 0.11.2 release notes: add sipa graphs & leveldb note...
< wumpus>
not saying that is not the way forward to 'find' the same datadir in bitcoin-cli and bitcoind, as well as other software, but it doesn't quite make it easier
< GitHub126>
[bitcoin] laanwj opened pull request #6970: Fix crash in validateaddress with -disablewallet (master...2015_11_rpc_validateaddress_crash) https://github.com/bitcoin/bitcoin/pull/6970
< Luke-Jr>
~/.config/Bitcoin/Bitcoin-Qt.conf
< wumpus>
bitcoin, by design, only has one datadir. If you move it, everything moves with it
< Luke-Jr>
does bitcoin-qt use strDataDir for the config location too? :/
< wumpus>
indeed it's the same for finding bitcoin.conf
< gmaxwell>
wumpus: I'd still suggest adding (hopefully) 1/2 LOC: code to use RegQuery to find the same location in bitcoind/bitcoin-cli.
< gmaxwell>
Luke-Jr: I think we could probably just add code that reads the registry in the same way RandAddSeedPerfmon and looks to the same place QT looks, and call that from bitcoind/bitcoin-cli on windows, and document the location so other programs can look. No?
< gmaxwell>
wumpus: sometimes we have to... there are dozens of windows ifdefs in the code. Unless you think linking bitcoind/bitcoin-cli to QT is a better plan. :)
< wumpus>
gmaxwell: qsettings is the qt equivalent of adding command line arguments, you can pass a datadir to bitcoin-cli and it will work
< Luke-Jr>
wumpus: my main concern is BFGMiner, not bitcoin-cli
< gmaxwell>
wumpus: it is a bit broken that changing your datadir breaks bitcoind / bitcoin-cli from finding it.
< wumpus>
most people that want to use RPC with bitcoin-qt will use the debug console
< wumpus>
maybe 1% of users actually use bitcoin-qt with bitcoin-cli, 0.1% uses it with a changed datadir through qt
< wumpus>
bitcoin.conf is usually in the same directory as the cookie so it won't avoid *any* problems
< wumpus>
otherwise I'd just have made it write a rpcuser and rpcpassword to bitcoin.conf
< dgenr8>
writing to bitcoin.conf should be controlled by a setting in bitcoin.conf
< gmaxwell>
then you have the "how do you find bitcoin.conf" problem.
< wumpus>
don't write to bitcoin.conf
< Luke-Jr>
it's tempting to change this to write to bitcoin.conf instead of QSettings then
< gmaxwell>
using something QT specific for handling finding the datadir on windows was probably what should have been avoided, since bitcoind and bitcoin-cli also need to find the data directory.
< Luke-Jr>
if it's overridden via bitcoin.conf or cmdline, it uses that; otherwise the platform default