1 2016-03-20 00:19:49	0|Luke-Jr|wumpus: FWIW, most of the base58 optimisation was already in practice in libbase58 (although implemented differently)
 2 2016-03-20 07:22:51	0|la|http://oortr.com/ZjllYz
 3 2016-03-20 11:02:12	0|GitHub34|[13bitcoin] 15MarcoFalke closed pull request #7721: [qa] Use print() in rpc tests (06master...06Mf1603-qaPy3print) 02https://github.com/bitcoin/bitcoin/pull/7721
 4 2016-03-20 18:01:15	0|GitHub187|[13bitcoin] 15laanwj opened pull request #7723: build: python 3 compatibility (06master...062016_03_build_python_3) 02https://github.com/bitcoin/bitcoin/pull/7723
 5 2016-03-20 22:13:41	0|BCB|why isn't 8333 an iana registered port?
 6 2016-03-20 22:25:41	0|Ylbam|simple question: will BIP9 be used for SW deployment?
 7 2016-03-20 22:32:56	0|sipa|Ylbam: yes, that's next on the todo list: uodate the segwit code to be bip9 based
 8 2016-03-20 22:33:12	0|sipa|*update
 9 2016-03-20 22:33:41	0|Ylbam|ok thanx sipa
10 2016-03-20 22:37:09	0|Ylbam|sipa: it looks like BIP9 requires a 95% consensus for activation, are you feeling concerned about Classic mining currently being above the 5% veto threshold?
11 2016-03-20 22:38:00	0|Ylbam|SF activations I mean
12 2016-03-20 22:40:42	0|sipa|SW is a softfork, it's up to miners to choose to adopt it, not up to me
13 2016-03-20 22:42:40	0|Ylbam|sipa: ok, so nothing special planned here, hoping we won't get stalled
14 2016-03-20 23:37:35	0|sipa|wumpus, jonasschnelli: is there any way to check what datadir a Bitcoin-Qt was configured to use?
15 2016-03-20 23:59:15	0|morcos|sipa: you know there is a QT settings file somewhere right?