< ossifrage> To my local 0.15.0, I added a command line option to specify the max upload timeframe to try and more evenly spread out the data spent serving old blocks. The 24 hour default results in overly spikey network traffic.
< jonasschnelli> sipa: re #11167, is it a problem that you can send to BIP173 addresses when IsWitness is diabled? "addwitnessaddress" rejects while sendtoaddress doesn't... I guess since it's active on mainnet this doesn't matter anymore?
< gribble> https://github.com/bitcoin/bitcoin/issues/11167 | Full BIP173 (Bech32) support by sipa · Pull Request #11167 · bitcoin/bitcoin · GitHub
< sipa> jonasschnelli: right
< sipa> it was there to prevent creating a segwit address (which could be stolen from) before it activated
< sipa> but it's complicated by the fact that many tests in regtest operate in a state where it is not active yet
< esotericnonsense> whee! successfully compiled and running on my phone.
< achow101> esotericnonsense: ... why?
< esotericnonsense> achow101: because i can!
< achow101> bitcoind or bitcoin-qt?
< esotericnonsense> bitcoind
< esotericnonsense> i don't think it's ever going to sync
< achow101> esotericnonsense: I think it has a higher probability of syncing than my bitcoin 0.1.0 node does
< esotericnonsense> even the 2009 blocks are slow
< achow101> how slow?
< esotericnonsense> the log is truncated, hang on
< esotericnonsense> 1m15s from 2010-01-01 to 2010-04-01 (height 32490 -> 48298)
< goatpig> you in for a week at this rate
< achow101> esotericnonsense: started at 21:27:28 utc, currently at 1661
< esotericnonsense> unfortunately the actually-possibly-useful thing that it could be used for won't work; it would be fun to use it as a trusted node in schildbach's wallet
< achow101> granted it has crashed multiple times and the vm it is in has also crashed a few times
< esotericnonsense> but i am going to guess that they'd clash on the ports and neither side can be configured
< esotericnonsense> (also if it's pruned it won't connect either)
< esotericnonsense> achow101: lol.
< achow101> I don't think it's ever going to get anywhere near being in sync
< esotericnonsense> are there any issues with copying datadirs across architectures? endianness? other stuff?
< achow101> shouldn't be
< esotericnonsense> (I could produce a pruned datadir on my main box and chuck that over)
< sipa> achow101: i think it should be totally possible to sync
< sipa> i got abcore to sync with 0.13 on my oneplus one (woth 3 GB ram)
< sipa> on my nexus 5x now i haven't tried, as it only has 2 GB ram, but with 0.15 i think it should be possible
< achow101> sipa: I was talking about my 0.1.0 node
< sipa> oh, i missed that
< luke-jr> jonasschnelli: https://github.com/bitcoin/bips/pull/592 fix readme?
< bitcoin-git> [bitcoin] sipa opened pull request #11389: Support having SegWit always active in regtest (master...201709_itsalwayssegwitinregtestia) https://github.com/bitcoin/bitcoin/pull/11389
< arubi> heh
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/aeed345c9bad...10a20bf7700e
< bitcoin-git> bitcoin/master 723aa1b Wladimir J. van der Laan: qt: Backup former GUI settings on `-resetguisettings`...
< bitcoin-git> bitcoin/master 10a20bf Wladimir J. van der Laan: Merge #11338: qt: Backup former GUI settings on `-resetguisettings`...
< bitcoin-git> [bitcoin] laanwj closed pull request #11338: qt: Backup former GUI settings on `-resetguisettings` (master...2017_10_backup_resetguisettings) https://github.com/bitcoin/bitcoin/pull/11338
< jonasschnelli> luke-jr: Oh. Yes. Will do
< ThomasV> sipa: what was your point about bip124 and CLTV, CSV?
< ThomasV> it seems to me that nLocktime and nSequence are "out of scope" anyway
< ThomasV> by that I mean the derived address does not depend on them
< sipa> ThomasV: CLTV and CSV are script opcodes
< sipa> CLTV sets a requirement on the nLockTime field of the spending transaction
< ThomasV> sipa: so?
< sipa> so they're not out of scope
< sipa> they're things that influence the address
< ThomasV> maybe we don't agree on the scope then.
< ThomasV> how?
< sipa> i think you misunderstand me
< sipa> i wasn't talking about nLockTime and nSequence
< ThomasV> no, you were talking about the parameter in the script
< sipa> i'm talking about having scriptPubKeys with the CLTV or CSV instruction in them
< ThomasV> right
< ThomasV> but how would that interfer with bip124?
< sipa> i have no idea, i have never looked at bip124
< ThomasV> or, to put it differently, what do you expect bip124 to achieve there?
< sipa> i brought CLTV up as an example of something where there is more to backup than just a key
< ThomasV> oh but we agree that there is more to backup :)
< ThomasV> I thought you were saying that bip124 would be broken by these opcodes
< sipa> sorry if i gave that impression
< sipa> but i don't know bip124
< ThomasV> sipa: BIP124 is not really specified, but it is trivial to read
< ThomasV> it just says "lets define a template for scripts"
< ThomasV> where pubkeys are variables
< sipa> right
< ThomasV> the scriptpubkey type (non-segwit, segwint-in-p2sh or native-segwit) is something orthogonal, though.
< esotericnonsense> achow101: on both aarch64 and armv7l it works properly by just copying datadir over from amd64 (i don't have the patience to wait). https://esotericnonsense.com/img/bitcoind-motog.jpg
< esotericnonsense> still have no use for it. :P
< bitcoin-git> [bitcoin] jnewbery opened pull request #11390: [docs] document scripted-diff (master...document_scripted_diff) https://github.com/bitcoin/bitcoin/pull/11390