< bitcoin-git> [bitcoin] kallewoof closed pull request #11489: [wallet] sendtoaddress output type argument (master...201709_segwitwallet2_sendtoaddress) https://github.com/bitcoin/bitcoin/pull/11489
< jrieck> hi
< Randolf> Hello jrieck.
< jrieck> how are we doing tonight?
< Randolf> Hungry, but remedying that by eating dinner.
< Captain_G> To the devs: Thank you guys for all your efforts, if only to advance cryptocurrencies in general. If the rest of us commonfolk could see the distant future, you guys might actually get the respect you deserve.
< xmsx_> Hey guys, any of you had issues with hanging "Checking all blk files are present" ?
< jonasschnelli> xmsx_: is that your last debug.log entry?
< xmsx_> https://bitcointalk.org/index.php?topic=2612957.0 -- same as here, daemon starts fine, but it loads blk files tooo long
< xmsx_> it crunches something as it uses 100% CPU
< xmsx_> RPC returns "Loading block index...", is there any reason why it takes so long to finish?
< shane> took me 9 hours to write this im excited
< xmsx_> after I do sendrawtransaction, do I need to reboot with -rescan?
< luke-jr> xmsx_: no, these are #bitcoin topics
< luke-jr> this channel is for development, not users
< luke-jr> shane: and ##altcoin-dev is for you
< shane> sorry thank you for the link can i get that alt core dev link again
< shane> i dced
< luke-jr> [07:32:18] <luke-jr> shane: and ##altcoin-dev is for you
< shane> thank you very much
< provoostenator> When launching with -debug=rpc is there any way to get a more details than just "ThreadRPCServer method=validateaddres". In particular, can I make it spit out the IP address where the request came from?
< gmaxwell> provoostenator: that sounds useful, I don't know of any existing way to do that. esp if the rpcauth is used, logging the user would be nice.
< jonasschnelli> Is there a rason why GetMinimumFee() is wallet only?
< provoostenator> gmaxwell: I have no idea how to do that, so just made a ticket #12223
< gribble> https://github.com/bitcoin/bitcoin/issues/12223 | Log origin IP of RPC request · Issue #12223 · bitcoin/bitcoin · GitHub
< * provoostenator> wonders if fanquake uses a bot to tag issues or is just really fast
< provoostenator> I'll try to review all outstanding 0.16.0 milestone issues today. 8 bottles of beer on the wall, ...
< mrannanay> Hi, so I've been looking at the libnatpmp implementation in relation to #11902
< gribble> https://github.com/bitcoin/bitcoin/issues/11902 | NAT-PMP port forwarding support · Issue #11902 · bitcoin/bitcoin · GitHub
< mrannanay> I wanted to know if we would move forward with https://github.com/miniupnp/libnatpmp if the implementation works.
< mrannanay> I hope that this does not add a dependency (this was one of the objectives that I understood from the issue description)
< wumpus> mrannanay: wouldn't using that library add a dependency, by definition?
< mrannanay> We could implement the functions but that would essentially mean porting the whole library
< sipa> mrannanay: one of the reasons why nat-pmp seems so appealing is that it is so simple
< sipa> maybe it isn't worth the effort of adding a depemdecy but instead implement the few commands we care about ourselves
< mrannanay> sipa: +1
< eshan> Hii!! i am a noob here , i just installed bitcoind on my system and want to build a web based application (buy, sell, trade, multiple wallets).
< eshan> any help would be appreciated
< eshan> :)
< instagibbs> eshan, #bitcoin
< eshan> thanks instagibbs
< aj> mrannanay, sipa: about 60% of the code for libnatpmp is arch specific stuff to work out the gateway address :( it seems kinda painful
< sipa> aj: ouch :(
< aj> sipa: it's not a lot of code still, 600 loc for windows, cygwin, linux, bsd, macos, and haiku iirc. but it's pretty gross.
< mrannanay> aj: I think its all about parsing the "/proc/net/route" file.
< aj> mrannanay: sure, that's the linux code path
< mrannanay> aj: How do you suggest we do this?
< aj> mrannanay: no idea :(
< bitcoin-git> [bitcoin] sdaftuar opened pull request #12225: Mempool cleanups (master...2018-01-mempool-cleanups) https://github.com/bitcoin/bitcoin/pull/12225
< provoostenator> Maybe that 60% can be extracted into a seperate package that both we and libnatpmp can use?
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/9a97f39afaa8...f4c942e36154
< bitcoin-git> bitcoin/master ec527c6 Russell Yanofsky: Don't allow relative -walletdir paths...
< bitcoin-git> bitcoin/master f4c942e Wladimir J. van der Laan: Merge #12220: Error if relative -walletdir is specified...
< bitcoin-git> [bitcoin] laanwj closed pull request #12220: Error if relative -walletdir is specified (master...pr/wdabs) https://github.com/bitcoin/bitcoin/pull/12220
< bitcoin-git> [bitcoin] ryanofsky opened pull request #12227: test_runner: Readable output if create_cache.py fails (master...pr/runcache) https://github.com/bitcoin/bitcoin/pull/12227
< bitcoin-git> [bitcoin] mmgen opened pull request #12228: Allow wallet file to be a symlink, as was the case before v0.15.0 (master...wallet_symlink) https://github.com/bitcoin/bitcoin/pull/12228
< bitcoin-git> [bitcoin] mmgen closed pull request #12228: Allow wallet file to be a symlink, as was the case before v0.15.0 (master...wallet_symlink) https://github.com/bitcoin/bitcoin/pull/12228
< cfields> sorry for missing yesterday's meeting, was travelling and completely forgot
< cfields> BlueMatt: unlikely ping
< gmaxwell> 2018-01-19 20:10:21 Potential stale tip detected, will try using extra outbound peer (last tip update: 7 seconds ago)
< gmaxwell> ^ while setnetworkactive false...
< sdaftuar> gmaxwell: was taht just a confusing log message, or did we make a connection we shouldn't?
< sdaftuar> wait what
< sdaftuar> 7 seconds ago?
< gmaxwell> sdaftuar: node was syncing.
< gmaxwell> so it has a best header that is probably hours old, and chaintip which was progressing.
< sdaftuar> gmaxwell: that is confusing to me... maybe there's a bug in how g_last_tip_update (time of last tip update) is being set
< gmaxwell> it might matter that I'm syncing over submitblock rpc
< sdaftuar> the tip stale check is based on how long since the tip updated. the minimum value there should be like 1800 seconds or something; 7 should be impossible
< sdaftuar> is this running master?
< gmaxwell> pft no, some spinoff based on 0.15, though I didn't see anything in the diff that could have caused that.
< sdaftuar> so no changes to the TipMayBeStale() function in net_processing.cpp then. hmm
< gmaxwell> right.
< sdaftuar> i am puzzled
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #12231: rpc: Avoid KeyError in getpeerinfo bytes per msg (master...Mf1801-rpcPeerInfoKeyError) https://github.com/bitcoin/bitcoin/pull/12231