< bitcoin-git>
[bitcoin] richardkiss opened pull request #12600: Add a test for large tx output scripts with segwit input. (master...feature/segwit_big_txout_script) https://github.com/bitcoin/bitcoin/pull/12600
< larafale>
sipa_: thx a lot pieter
< larafale>
luke-jr: also thx, appreciate the feedbacks :)
< Popkultur>
Hi, just a question: What about bit rot on the blockchain? This might not yet be an issue, but there might be a good idea to implement some sort of error checking algorithm which consolidates historical blocks by p2p?
< Popkultur>
okay, thinking further I guess this already happens by downloading a fresh copy of the blockchain. And there are checksums, too.
< bitcoin-git>
bitcoin/master ee04119 Chris Moore: Show a transaction's virtual size in its details dialog.
< bitcoin-git>
bitcoin/master ce56fdd MarcoFalke: Merge #12580: Show a transaction's virtual size in its details dialog...
< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #12580: Show a transaction's virtual size in its details dialog (master...show_vsize) https://github.com/bitcoin/bitcoin/pull/12580
< Randolf>
MarcoFalke: If you've got a moment, please also see PR #12501 -- after last week's meeting it seems that this should be okay to go, but if you think it needs more peer-review that's fine too.
< bitcoin-git>
bitcoin/master 4d14d06 DaveFromBinary: docs: clarified systemd installation instructions in init.md for Ubuntu users....
< bitcoin-git>
bitcoin/master 71f56da Wladimir J. van der Laan: Merge #12452: docs: clarified systemd installation instructions in init.md for Ubuntu users....
< bitcoin-git>
[bitcoin] laanwj closed pull request #12452: docs: clarified systemd installation instructions in init.md for Ubuntu users. (master...doc-init-updates) https://github.com/bitcoin/bitcoin/pull/12452
< bitcoin-git>
[bitcoin] laanwj closed pull request #10922: New file-partition.md doc describing how to partition files to ensure fast initial blockchain synchronization.. (master...master) https://github.com/bitcoin/bitcoin/pull/10922
< stevenroose>
gmaxwell: quick question: do you remember around what time the (txt) document on confidential transaction was published? (the confidential_values.txt)
< sipa>
stevenroose: may 2015 iirc
< stevenroose>
Phew, that's been some time
< stevenroose>
It seems like we're getting closer though :)
< bitcoin-git>
bitcoin/master 1830784 532479301: Consensus: Fix bug when compiler do not support __builtin_clz*...
< bitcoin-git>
bitcoin/master cbc1fcf Wladimir J. van der Laan: Merge #12573: Fix compilation when compiler do not support __builtin_clz*...
< bitcoin-git>
[bitcoin] laanwj closed pull request #12573: Fix compilation when compiler do not support __builtin_clz* (master...vs2017) https://github.com/bitcoin/bitcoin/pull/12573
< bitcoin-git>
bitcoin/master 992f568 fanquake: depends: Only use D_DARWIN_C_SOURCE when building miniupnpc on darwin
< bitcoin-git>
bitcoin/master 6645eaf Wladimir J. van der Laan: Merge #12466: depends: Only use D_DARWIN_C_SOURCE when building miniupnpc on darwin...
< bitcoin-git>
[bitcoin] laanwj closed pull request #12466: depends: Only use D_DARWIN_C_SOURCE when building miniupnpc on darwin (master...fix-miniupnpc-darwin) https://github.com/bitcoin/bitcoin/pull/12466
< bitcoin-git>
[bitcoin] eklitzke opened pull request #12604: Add DynamicMemoryUsage() to CDBWrapper to estimate LevelDB memory use (master...leveldb_memory) https://github.com/bitcoin/bitcoin/pull/12604
< bitcoin-git>
bitcoin/master 55f89da Ben Woosley: Don't test against the mempool min fee information in mempool_limit.py...
< bitcoin-git>
bitcoin/master 955fd23 Wladimir J. van der Laan: Merge #12512: Don't test against the mempool min fee information in mempool_limit.py...
< bitcoin-git>
[bitcoin] laanwj closed pull request #12512: Don't test against the mempool min fee information in mempool_limit.py (master...fix-min-fee-test) https://github.com/bitcoin/bitcoin/pull/12512
< bitcoin-git>
[bitcoin] Sjors closed pull request #12482: [tests] bind functional test nodes to 127.0.0.1 (master...2018/02/test-framework-bind) https://github.com/bitcoin/bitcoin/pull/12482
< bitcoin-git>
[bitcoin] Sjors reopened pull request #12482: [tests] bind functional test nodes to 127.0.0.1 (master...2018/02/test-framework-bind) https://github.com/bitcoin/bitcoin/pull/12482
< theymos>
There's some sort of bug related to accounts (which I know you intend to deprecate at some point, but still exist). Bitcointalk.org uses the used-to-be-standard accounts pattern of 'getaccountaddress <account>' & 'getbalance <account>'. Upon upgrading from 0.14.2 to 0.16.0, addresses are being given out by getaccountaddress, but at some point they no longer become associated with the account.
< theymos>
I haven't tracked down exactly where the account designation gets lost. I'm just going to take this opportunity to get rid of accounts usage. Though I suppose that other people will run into this problem, since it was the standard pattern some years ago.
< achow101>
theymos: can you open an issue on github about that?
< theymos>
ok
< ProfMac>
Hmm. I kind of liked accounts. Where is the archive discussion about this?
< mlz>
ProfMac, look in the logs of this channel
< luke-jr>
theymos: getaccountaddress wasn't the standard pattern ever AFAIK; that's going to result in address reuse..
< luke-jr>
should be getnewaddress <account>
< theymos>
getaccountaddress generates a new address for the account when the old one receives a payment
< luke-jr>
yes, which it might not have yet
< luke-jr>
liable to give the same address to two people using the website at the same time, and then get paid by both to the same
< midnightmagic>
accounts have always been broken, in some way or other. :(
< gmaxwell>
luke-jr: that wouldn't happen if each person is a different account.
< gmaxwell>
giving one person the same address multiple times until you've seen a payment on the old one isn't _that_ bad.
< theymos>
The ideal is probably invoice-based accounting, but that's a huge change from balances-based accounting. So currently bitcointalk.org is just reusing addresses 100%, since getaccountaddress is broken and I don't have time to implement the address-changing thing right now...
< ProfMac>
By happenstance, I have 0.8.1 -qt open. When I go to "receive coins" --> "new address" and drop in an existing label, it returns a new address. This occured when only 1 address existed and had received funds, and also when there were multiple addresses, several of which had never received funds.