--- Day changed Tue Aug 21 2018 00:03 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has joined #lnd 00:06 -!- doml3_13333337 [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 240 seconds] 00:11 -!- peevsie [~peevsie@2604:2000:f18f:e300::2] has quit [Remote host closed the connection] 00:12 -!- peevsie [~peevsie@2604:2000:f18f:e300::2] has joined #lnd 00:33 -!- jungly [~quassel@79.8.200.97] has joined #lnd 00:35 -!- itaseski [~itaseski@213.135.176.233] has joined #lnd 01:08 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 01:15 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #lnd 01:33 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 01:37 < Talkless> I got first incomming channel opened with me, whohoo! 01:38 < Talkless> Next milestone, forward satoshis! :) 02:13 < stevenroose> roasbeef: would you be open to having a "daemon" package in neutrino that implements a stand-alone "neutrinod" with a gRPC interface? 02:23 <@roasbeef> stevenroose: yeh somthing we've been meaning to do, but hasn't been a super high prio for us lately 02:23 <@roasbeef> feels like should have stuff like watchonly addr watching to really make it worthwhile 02:23 <@roasbeef> tho that adds a bit larger scope there 02:23 <@roasbeef> i guess one other q is: what would ppl use it for? 02:24 <@roasbeef> for example full node cna do like queries or w/e, I guess we could add some of that, just fetching over p2p network? 02:24 <@roasbeef> some nodes will ban if you send a getdata and they didn't send an inv tho 02:25 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 256 seconds] 02:29 -!- jpe [~jp@fnord.cryptophone.de] has joined #lnd 02:30 -!- jpe [~jp@fnord.cryptophone.de] has quit [Client Quit] 02:30 -!- jpe [~jp@fnord.cryptophone.de] has joined #lnd 02:30 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 02:31 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 02:31 -!- jpe [~jp@fnord.cryptophone.de] has quit [Client Quit] 02:32 -!- jpe [~jp@fnord.cryptophone.de] has joined #lnd 02:32 < stevenroose> roasbeef: use it as an SPV client? 02:39 < stevenroose> I mean it's a lightweight daemon that can do validation through scans and broadcasts 02:43 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 02:48 -!- gethh [uid264798@gateway/web/irccloud.com/x-jmypszpsoufqvcfr] has joined #lnd 02:51 -!- math_ [~mario@p4FCB3FA3.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 03:07 -!- EagleTM [~hab@x4db4749f.dyn.telefonica.de] has joined #lnd 03:08 < booyah> LND can work with own full node right? can it be prunned 03:16 < Talkless> booyah: I am running my own full not. Dunno about pruned. 03:16 < Talkless> full node* 03:17 -!- cryptodechange [~cryptodec@host86-140-30-147.range86-140.btcentralplus.com] has quit [Ping timeout: 248 seconds] 03:18 < Talkless> booyah: https://github.com/lightningnetwork/lnd/issues/527#issuecomment-354173269 they support Neutrino, that is a lightweight solution I guess 03:18 -!- tomaw25 [~tomaw@5.105.44.111] has joined #lnd 03:18 -!- tomaw25 [~tomaw@5.105.44.111] has quit [Remote host closed the connection] 03:22 -!- nlsun19 [~nlsun@114-198-21-21.dyn.iinet.net.au] has joined #lnd 03:22 -!- nlsun19 [~nlsun@114-198-21-21.dyn.iinet.net.au] has quit [Remote host closed the connection] 03:26 < molz> booyah, i wouldn't use a pruned node, you can lose money 03:26 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 03:26 < molz> even with a full node we still need to watch what bitcoind can slip off 03:28 < molz> LND and Eclair users are the first group that seriously use ZMQ in bitcoind, testing it out to the max 03:31 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 250 seconds] 03:33 -!- AndyS2 [~noname@static.74.88.9.5.clients.your-server.de] has quit [Ping timeout: 248 seconds] 03:33 -!- AndyS2 [~noname@static.74.88.9.5.clients.your-server.de] has joined #lnd 03:34 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 03:42 < stevenroose> booyah: they support Bitcoin Core as a full node backend, so I guess they support pruned mode as well 03:49 -!- github-lnd [github-lnd@gateway/service/github.com/x-vqxqboldbrwjfizj] has joined #lnd 03:49 -github-lnd:#lnd- [lnd] sevastos opened pull request #1758: config: add MaxRemoteDelay chainConfig option (master...maxremotedelay) https://git.io/fAUvy 03:49 -!- github-lnd [github-lnd@gateway/service/github.com/x-vqxqboldbrwjfizj] has left #lnd [] 03:52 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 244 seconds] 03:59 < molz> stevenroose, they who? 03:59 < stevenroose> molz: lnd does, doesn't it? 04:00 < molz> nope 04:00 < stevenroose> Was under the impression they already did 04:00 < stevenroose> ah 04:00 < stevenroose> Whoops :D booyah ignore my response 04:00 < molz> i haven't seen the devs say it's safe to run lnd on a pruned node, some people have tried it, but for me i wouldn't do it 04:08 -!- modin1 [~modin@117.80.157.226] has joined #lnd 04:12 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #lnd 04:14 -!- modin1 [~modin@117.80.157.226] has quit [Remote host closed the connection] 04:18 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 276 seconds] 04:18 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 04:28 -!- Geeky_Bear [~Geeky_Bea@46.36.28.132] has joined #lnd 04:29 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Remote host closed the connection] 04:30 -!- Geeky_Bear [~Geeky_Bea@46.36.28.132] has quit [Remote host closed the connection] 04:34 -!- Pioklo_ [~Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 04:34 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd 04:37 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 256 seconds] 04:38 -!- kamyl [~user@unaffiliated/kamyl] has quit [Ping timeout: 240 seconds] 04:38 -!- kamyl [~user@unaffiliated/kamyl] has joined #lnd 04:40 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Ping timeout: 268 seconds] 04:42 -!- deusexbeer [~deusexbee@095-129-172-241-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 04:43 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #lnd 04:44 -!- Pioklo__ [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 04:45 -!- deusexbeer [~deusexbee@095-129-172-241-dynamic-pool-adsl.wbt.ru] has joined #lnd 04:45 -!- Pioklo_ [~Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 272 seconds] 04:50 -!- botka [~nodebot@static.171.39.76.144.clients.your-server.de] has quit [Ping timeout: 244 seconds] 04:50 -!- kamyl [~user@unaffiliated/kamyl] has quit [Ping timeout: 256 seconds] 04:51 -!- tumi [tumi@u.nix.is] has quit [Ping timeout: 256 seconds] 04:52 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Read error: Connection reset by peer] 04:56 -!- botka [~nodebot@static.171.39.76.144.clients.your-server.de] has joined #lnd 04:57 -!- tumi [tumi@u.nix.is] has joined #lnd 04:58 -!- kamyl [~user@unaffiliated/kamyl] has joined #lnd 05:05 -!- Pioklo_ [~Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 05:06 -!- Pioklo__ [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 240 seconds] 05:10 -!- itaseski_ [~itaseski@213.135.176.233] has joined #lnd 05:11 -!- itaseski [~itaseski@213.135.176.233] has quit [Ping timeout: 256 seconds] 05:14 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd 05:17 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Remote host closed the connection] 05:20 -!- Pioklo__ [~Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 05:23 -!- Pioklo_ [~Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 268 seconds] 05:37 -!- Pioklo__ [~Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 240 seconds] 05:38 -!- Pioklo__ [~Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 05:58 -!- Pioklo_ [~Pioklo@118-40.echostar.pl] has joined #lnd 05:58 < Veggen> wow. BLW crafted a TX, through me...10k satoshi. And seems "I took" 26 Satoshi! 05:58 -!- Pioklo__ [~Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 272 seconds] 05:59 < Veggen> I don't have that fee policy. I have 100 msat base_fee and 0.0001 feerate. So it should be 1.1 satoshi. 06:00 < Veggen> and there were 26 satoshi left for the rest of TX, probably one more routing hop. 06:08 -!- github-lnd [github-lnd@gateway/service/github.com/x-zifopsxitppevxfd] has joined #lnd 06:08 -github-lnd:#lnd- [lnd] ZapUser77 opened pull request #1759: Added command: Rebalance (master...Rebalance) https://git.io/fAUOq 06:08 -!- github-lnd [github-lnd@gateway/service/github.com/x-zifopsxitppevxfd] has left #lnd [] 06:13 < lndbot> molz stevenroose: lnd works fine with pruned bitcoind backend, running it since several weeks 06:13 < molz> keep it for a few months to find out for sure 06:14 < molz> and if there's a reorg, check it to find if it can pass the test 06:16 < lndbot> reorg is only a few blocks? wouldn't matter for prune 06:16 < molz> i prefer to follow the advice of a Core dev (reference to c-lightning but it's the same for all impls): Jan 25 11:49:49 it's not recommended to use it with a pruned node, because if lightningd falls too far behind (further than the pruning) it can't get the blocks anymore from bitcoind and will become stuck 06:17 < molz> how do you know reorgs only happen for a few blocks? you don't know that 06:18 < lndbot> taht's correct, but for lnd to fall behind the prune horizon it would have to be offline for the length of the pruning height 06:19 -!- Pioklo_ [~Pioklo@118-40.echostar.pl] has quit [Read error: Connection reset by peer] 06:19 < lndbot> you're already running into problems after 24 hours, when peers can cheat you (without watchtower) 06:19 -!- Pioklo_ [~Pioklo@118-40.echostar.pl] has joined #lnd 06:20 < lndbot> nicolasdorier just created a version of btcpayserver that prunes to 50gb or something like that 06:20 < molz> i can run many fullnodes, no thanks 06:21 < lndbot> means your lnd would have to be offline for several *month* to fall behind the pruning horizon 06:21 < molz> i wouldn't even run a pruned bitcoin for my real money onchain, why should i run a pruned bitcoin for my LND? 06:22 < lndbot> it's mainly for merchants who can now use a 10$ host instead of 70$ one 06:23 < lndbot> (in the btcpayserver case) 06:27 < molz> right, they're taking a risk foolishly while hard disks are very cheap these days 06:28 < molz> im not even paying $70 a month to run full nodes lol 06:39 < stevenroose> molz: basically keep last 3 months and make sure you have your lightning node up 06:39 -!- cryptodechange [~cryptodec@host86-163-78-115.range86-163.btcentralplus.com] has joined #lnd 06:43 < EagleTM> what's the best course of action for lnd if you have a harddisk crash? restore from seed and hope the channels will be force-closed by the other side without fraud? 06:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 06:45 < Veggen> Hard disk space is curently not the issue. Keep the blocks onm a very chap disk. 06:47 -!- itaseski_ [~itaseski@213.135.176.233] has quit [Quit: Leaving] 06:55 < molz> stevenroose, what's been happening a lot is someone tries to send a tx but it doesn't broadcast, so in order to rebroadcast it, they need the raw tx, can a pruned node produce the raw tx for them? 06:58 < stevenroose> molz: one thing: the node should not be responsible for storing that tx.. if any client of a node wants the tx confirmed, it should be able to rebroadcast itself until it is confirmed 06:59 < stevenroose> you should be able to hot-swap a node, so that f.e. if you build in redundancy of nodes, you could swap for another node whenever one crashes or gets too much load 07:01 < waxwing> molz, i joined #lightninghack as per https://wiki.fulmo.org/index.php?title=Lightning_Hackday_Wiki and i'm the only one there :) 07:06 < waxwing> roasbeef, right, i guess was just surprised since golang (sensibly) seems to be intolerant of unused vars, i see this propagated all over the btcd codebase (pver) but can't see anywhere what its purpose is. no matter ofc. 07:09 < molz> stevenroose, eh.. if bitcoind doesn't store that tx in your mempool for you then how does your tx work? in what mempool? 07:10 < molz> i guess you're not aware of what's going on with bitcoin and lnd 07:11 < molz> and ofc you could swap your lnd to run on another bitcoind node but we're talking about you want to save space and money with a pruned bitcoind node here 07:21 < lndbot> what does pruning has to do with the mempool? 07:42 < stevenroose> molz: I'm quite aware of what's going on.. I'm just saying that if lnd wants a tx to be confirmed, it can't just send it to a node and consider it done. If the tx ends up lost, it should (lnd itself) be able to retry sending it to a (different or the same) node 07:43 < stevenroose> I don't think btcd even persistently stores its mempool. So if lnd sends a tx to btcd, and btcd is restarted, the tx could be lost and lnd would have to submit it again 07:44 < molz> stevenroose, a tx can be stuck for months.. what i'm saying is if my tx doesn't broadcast, i can ask a miner to mine it for me but he needs the txid and raw tx hexstring.. so can a pruned node give me that raw tx? which i don't know and if you dont know just say you don't know 07:47 < lndbot> a pruned node is a full node and can do everything a non-pruned node can do - with the exception of giving you data about blocks and tx from the blocks that are pruned off (like from 2017 and before, depending on how much you pruned) 07:47 < lndbot> that has nothing to do with (stuck) tx in the mempool 07:49 -!- yep555 [~yep555@p200300C99F3E1000ACD5E73FCA7E513C.dip0.t-ipconnect.de] has joined #lnd 07:53 < molz> joeblow lol you have no clue and im done with this convo 07:55 < lndbot> then maybe enlighten me instead of showing this arrogance 07:57 < Veggen> I think it'd be safe to prune upto the point of the oldest LN channel. 07:57 < Veggen> but no mode. 07:57 < Veggen> no more. 07:57 < lndbot> I think so too 07:57 < Veggen> in reality, it's going o be pretty limited use case. 07:59 < Veggen> how will you know what the oldest LN channewl is? In reality, you can't prune beyond some time in 2017. 08:00 < Veggen> there could, in theory, be a pocket LN network somewhere that simply does not have a connection to main LN network. So you can't take current grasph and use that for pruning. 08:00 < Veggen> eh, current graph. 08:02 < molz> joeblow arrogance is on your part with your text trying to tell me you know better and im tired of reading it, no arrogance on my part here 08:03 -!- doml3_13333337 [~Drolmer@unaffiliated/drolmer] has joined #lnd 08:05 < molz> Veggen, im firing up a pruned testnet node to find out for myself it it can give me a raw hextring for my txid.. over the years the pruned node is created for people who don't want to run a fullnode (and yes i don't consider a pruned node as a real full node) and i think serious devs don't even use a pruned node for their serious btc stashes 08:06 < lndbot> Veggen, why would you need to know about channels from other lnd nodes? Isn't it enough if you know about the channels of your own lnd node? 08:07 < Veggen> Mmm, I think you should validate that the funding transactyions from the channels you route through exists. 08:07 < Veggen> ...will LND do that? validate the funding tx'es for all gossiped channels? 08:07 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 276 seconds] 08:07 < EagleTM> from what i understand you get told by the next hop 08:09 < Veggen> told what, exactly? 08:09 < Veggen> should read the source code :) 08:09 < lndbot> well, a pruned bitcoind node validates all transactions on ibd? so you're not missing any funding tx 08:09 < EagleTM> whether it fails or not... basins this on aantonp's explanation here https://www.youtube.com/watch?v=c4TjfaLgzj4&feature=youtu.be 08:09 < EagleTM> *basing 08:11 < EagleTM> so with source routing it should be enough to know just about your own channels and do trial and error. but just guessing here 08:12 < molz> hey EagleTM :) are you running an lnd node? 08:12 < EagleTM> yes i do 08:27 < EagleTM> bitrefill node seems to have gone down for maintenance, interesting ;) 08:29 < lndbot> Hmm? 08:31 < qubenix> roasbeef: have you considered signing git commits? now we have to trust github to use beyond a tag, i trust you more. 08:32 < stevenroose> molz: what I'm saying is that you *should not rely on a node to store your raw txs*.. I also don't like your tone.. It looks like you don't have much experience with this stuff 08:33 < lndbot> Up here having issues connecting? 08:34 < EagleTM> maybe i misjudge "active": false 08:36 < molz> stevenroose, how do you resolve stuck transactions then? sorry you don't like my tone but i only asked you a straight question and you kept telling me stuff unrelated 08:38 < molz> stevenroose, and whether you think i have much experience with this stuff or not, I've done and seen real life txs with opening and closing txs on lnd, not sure you have any experience in this at all 08:38 < stevenroose> molz: I don't I'm saying if your tx is stuck, you have to resubmit it to your node. 08:38 < molz> stevenroose, and how do you resubmit it to your node? 08:38 < stevenroose> You take the same tx and submit it again.. 08:39 < stevenroose> Instead of deleting it after the first submit 08:39 < molz> nobody said deleting anything, show me a real example 08:39 < stevenroose> You say once you submit a tx, if you want to get it back, you need to ask your node to fetch it from its mempool 08:39 < stevenroose> You can just keep it yourself.. 08:39 < molz> what 08:39 < molz> i never said i want to get it back, do you understand raw txs in bitcoin? 08:40 < stevenroose> lol 08:40 < molz> how do you resubmit your tx to your node? 08:40 < molz> give me a real example 08:41 < stevenroose> You call the sendrawtransaction api (https://masonicboom.github.io/btcrpcapi/docs/master/sendrawtransaction.html) 08:41 < stevenroose> And put your encoded tx as an argument.. 08:42 < EagleTM> justin: did a manual peer connect, now shown as "active": true. hm not sure whether the peer dropped at some point, should be automatic really 08:43 < lndbot> molz can you please explain what a pruned node has to do with the mempool? The mempool of a pruned node is the same as the mempool from a non-pruned node. So you "resubmit" your stuck tx the same way as you would do with a non-pruned node? 08:43 < molz> stevenroose, can you do this with a pruned node? 08:44 < stevenroose> molz: ofc you can.. you can do this with any node that is connected, even an SPV node 08:44 < stevenroose> joeblow, I'm sorry this discussion got overheated :D I was just trying to give it my 2 cents 08:45 < molz> stevenroose, so in that sendrawtransaction api, do you realize you need a "hextring"? and can you get this from a pruned node is what im wondering? 08:45 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 256 seconds] 08:46 < stevenroose> molz: the hexstring is your transcation 08:47 < stevenroose> You get it by creating your transaction (in lnd) and serializing it to bytes and then encode in hexadecimal 08:47 < molz> stevenroose, tell me how you can get it, Hint: it's very simple straight from bitcoind 08:47 -!- Guest38458 [~tyn@73.93.142.128] has joined #lnd 08:47 < molz> stevenroose, sounds like you're quoting from some text bs 08:47 < stevenroose> lol, I give up 08:47 < molz> all you need is bitcoin-cli help 08:47 < stevenroose> do some reading 08:48 < molz> no you do it 08:48 < molz> i've help many people with their stuck txs 08:48 < molz> it would be a nightmare to tell them to go around the circle with what you said 08:49 < molz> stevenroose, here's what you do: bitcoin-cli getrawtransaction and bitcoin-cli sendrawtransation 08:51 < lndbot> why shouldn't that be possible with a pruned node? 08:51 < stevenroose> molz: I'm talking about the case when your node doesn't have the transactin anymore 08:52 < stevenroose> molz: When you use getrawtransaction, you ask the node to look it up in its mempool. What do you do if it's no longer in its mempool? 08:52 < stevenroose> F.e. when the mempool overflows and the node needs to discard transactions. Or when the node crashes and the mempool is deleted? 08:55 < EagleTM> wrt peers: Looks like I run into this Disconnecting :9735, reason: unable to start peer: peer did not complete handshake within 5 seconds - i guess this happens when you have load on the server 08:55 < lndbot> stevenroose: the discussion about stuck tx has only to do with the mempool, and has nothing to do with pruning. Correct? 09:04 < molz> stevenroose, in that case the stuck tx is gone? i know if you run bitcoind with -blocksonly it doesn't keep any mempool and it can help to release the stuck txs.. then "abandonetransaction" command can be used but idk if this can be done with lnd 09:05 < molz> abandontransaction* 09:07 < EagleTM> ok looks like most of the peer connection stuff was fixed recently in https://github.com/lightningnetwork/lnd/pull/1349/commits i'm running a release and not master, all good for now i guess 09:11 < stevenroose> joeblow, yeah that sounds correct 09:12 < stevenroose> and molz, "in that case the stuck tx is gone", that's not really a solution to the problem :D so what I was trying to explain is that lnd should also keep a copy of the transaction before sending it to the node, so that in that case, it can just rebroadcast it with sendrawtransaction 09:12 < stevenroose> Besides, I'm quite sure lnd does 09:12 -!- BB-Martino [~martino@bitbargain.co.uk] has quit [Ping timeout: 240 seconds] 09:20 < Veggen> hrm.holy shit. I was reading some reddit, and doing some research into who was the richest addresses. 09:21 < Veggen> hmm, wait. it could be simply a p2SH. Not segwit. Is there any way to differ? 09:21 < molz> stevenroose, lnd doesn't give you a raw tx when you do an onchain tx, but c-lightning does 09:21 < Veggen> 3DD91Qx1Tat7zGWhtcowXCFZTrePstERYu in BCH. 144k BCH. 09:21 < molz> stevenroose, this is why i'm wondering if a pruned node can keep your raw txs for more than just a few days 09:22 < molz> currently im trying to help someone with his stuck opening tx and stuck closing tx, and the miner who would mine this for me is absent 09:23 < Veggen> If that's "segwit" they made into anyone can spend again, that's one hell of a bounty if you have a bit of hash rate. 09:24 < lndbot> Pruning doesn’t impact the mempool 09:26 < EagleTM> Veggen: most likely multisig on BCH 09:26 -!- BB-Martino [~martino@bitbargain.co.uk] has joined #lnd 09:27 -!- BB-Martino is now known as Guest77187 09:27 < Veggen> Eagle: I realized. 09:28 < lndbot> If it’s Bitmain they could just keep their funds in OP TRUE since they can reorg out anyone who tries to take it 09:28 < lndbot> alexbosworth, what's your take on pruning? Safe? Not safe? 09:29 < lndbot> (for use with lightning) 09:30 < stevenroose> > If it’s Bitmain they could just keep their funds in OP TRUE since they can reorg out anyone who tries to take it 09:30 < stevenroose> :D :D :D 09:32 < lndbot> I’ve tested pruning a bunch with LND, obviously it is not officially supported and it will fall over on huge reorgs and restore from seed, but otherwise it works if you are very careful about startup sequence and not letting bitcoind run without lnd also running 09:35 -!- Guest77187 [~martino@bitbargain.co.uk] has quit [Quit: ZNC - http://znc.in] 09:37 -!- BB-Martino_ [~martino@bitbargain.co.uk] has joined #lnd 09:41 < Veggen> alexboswrth: do LND validate funding txes of channels it routes through? (not its own) 09:47 < lndbot> Good question, I’m not sure 09:59 -!- rls [~rls@69.197.143.181] has joined #lnd 10:05 -!- gethh [uid264798@gateway/web/irccloud.com/x-jmypszpsoufqvcfr] has quit [Quit: Connection closed for inactivity] 10:09 -!- EagleTM [~hab@x4db4749f.dyn.telefonica.de] has quit [Ping timeout: 272 seconds] 10:12 -!- jungly [~quassel@79.8.200.97] has quit [Remote host closed the connection] 10:37 -!- nkk71 [~nkk71@89-172-251-140.adsl.net.t-com.hr] has joined #lnd 10:38 -!- nkk71 [~nkk71@89-172-251-140.adsl.net.t-com.hr] has quit [Remote host closed the connection] 10:45 -!- nedbat9 [~nedbat@190.74.188.244] has joined #lnd 10:47 -!- itaseski [~itaseski@213.135.176.233] has joined #lnd 10:52 -!- nedbat9 [~nedbat@190.74.188.244] has quit [Ping timeout: 268 seconds] 10:53 -!- rls [~rls@69.197.143.181] has quit [Ping timeout: 276 seconds] 11:20 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 11:42 -!- Netsplit over, joins: Bunnyh 11:43 -!- kkt2MartinPospch [kkt2matrix@gateway/shell/matrix.org/x-gupnznlmjmzxoero] has joined #lnd 11:52 -!- jpe [~jp@fnord.cryptophone.de] has quit [Ping timeout: 276 seconds] 11:59 -!- rls [~rls@69.197.143.181] has joined #lnd 12:02 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds] 12:17 < booyah> alexboswrth, about being carefull when it runs, why not instead have lnd save the last blockheight it checked up-to? 12:17 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #lnd 12:17 < booyah> (and make sure the ZMQ or whatever that is used is used atomically, eg add blockheight/hash to replies?) 12:23 < lndbot> lnd saves the last blockheight the problem is missing announcements from bitcoind 12:24 < lndbot> What happens if lnd is offline a long time and asks bitcoind for an old block that has already been pruned away? 12:32 -!- Humvee28 [~Humvee@150.pool85-59-71.dynamic.orange.es] has joined #lnd 12:33 -!- Humvee28 [~Humvee@150.pool85-59-71.dynamic.orange.es] has quit [Remote host closed the connection] 12:34 -!- Netsplit over, joins: betawaffle, ivegotasthma 12:35 -!- rk3y [~rk3y@vmd27150.contaboserver.net] has joined #lnd 12:36 -!- Netsplit over, joins: s7r 12:39 -!- Netsplit *.net <-> *.split quits: stevenroose, meshcollider, stiell, p3tr, molz, RusAlex 12:40 -!- Netsplit over, joins: p3tr 12:40 -!- RusAlex [~Chel@89-212-19-164.static.t-2.net] has joined #lnd 12:40 < lndbot> we're talking about a pruning horizon of a few months at least (that'd be a long time offline for a lnd node) 12:40 -!- stiell [~stian@139.163.102.62.customer.cdi.no] has joined #lnd 12:41 < lndbot> and after 144 blocks you already have bigger problems when your lnd node is offline (at least without watchtowers) 12:41 -!- RusAlex [~Chel@89-212-19-164.static.t-2.net] has quit [Changing host] 12:41 -!- RusAlex [~Chel@unaffiliated/rusalex] has joined #lnd 12:42 -!- stiell [~stian@139.163.102.62.customer.cdi.no] has quit [Changing host] 12:42 -!- stiell [~stian@fsf/member/stiell] has joined #lnd 12:44 < lndbot> Only if you are receiving 12:46 -!- Netsplit over, joins: stevenroose 12:46 -!- meshcollider [meshcollid@gateway/shell/elitebnc/x-wgvbdtbctoyeevjj] has joined #lnd 12:46 -!- Netsplit over, joins: molz 12:47 -!- lypsis [~lypsis@2a02:c207:3001:7075:dead:beef:babe:cafe] has quit [Ping timeout: 256 seconds] 12:53 -!- lypsis [~lypsis@2a02:c207:3001:7075:dead:beef:babe:cafe] has joined #lnd 12:53 -!- BB-Martino_ [~martino@bitbargain.co.uk] has quit [Ping timeout: 272 seconds] 13:00 -!- BB-Martino [~martino@bitbargain.co.uk] has joined #lnd 13:00 -!- BB-Martino is now known as Guest90292 13:07 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 13:12 -!- jl2012_ [sid133844@gateway/web/irccloud.com/x-mspisgraidtswzjf] has joined #lnd 13:14 -!- tumi_ [tumi@u.nix.is] has joined #lnd 13:18 -!- Guest38458 [~tyn@73.93.142.128] has left #lnd [] 13:19 -!- Netsplit *.net <-> *.split quits: Giszmo, tumi 13:19 -!- jl2012_ is now known as jl2012 13:19 -!- tin_ [~tyn@73.93.142.128] has joined #lnd 13:25 -!- Netsplit over, joins: chjj 13:26 -!- Netsplit over, joins: Giszmo 13:26 <@roasbeef> stevenroose: yeh i just mean like which rpc's would you add? 13:54 -!- rls [~rls@69.197.143.181] has quit [Ping timeout: 255 seconds] 14:10 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 14:11 -!- Guest90292 is now known as BB-Martino 14:31 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Excess Flood] 14:40 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 14:50 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 14:51 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 14:52 -!- Giszmo [~leo@pc-72-54-46-190.cm.vtr.net] has quit [Ping timeout: 252 seconds] 14:53 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Client Quit] 15:01 < Talkless> If I again enable autopilot, and some existing channel is bigger that autopilot.maxchansize, will autopilot close these channels? 15:02 < Talkless> molz: any idea? 15:02 < Veggen> autopilot won't close channels afaik. 15:02 < Talkless> there's also allocation limit, that could be exeeded too. 15:03 < Talkless> Veggen: I'll try to enable it again, see how it goes... 15:12 -!- Giszmo [~leo@45.232.32.202] has joined #lnd 15:14 < Talkless> Veggen: yeah it is currently opening new channel, so far so good. 15:20 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 15:36 -!- Pioklo__ [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 15:39 -!- Pioklo_ [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 244 seconds] 15:43 -!- itaseski [~itaseski@213.135.176.233] has quit [Ping timeout: 240 seconds] 15:55 -!- Pioklo__ [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 264 seconds] 16:03 <@roasbeef> Veggen: yeh dunno how optimized their path finding is really 16:03 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has joined #lnd 16:05 <@roasbeef> waxwing: which is nice, as you can find bugs at times if you don't declare a variable 16:05 <@roasbeef> it cares about unused declarted variables, not so much unused params 16:05 <@roasbeef> stevenroose: it does do re-trying 16:07 -!- doml3_13333337 [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 268 seconds] 16:07 <@roasbeef> Veggen: yep, most of the mobile wallet don't really, so eventually someone coudl flood them with a buncha garbage 16:08 <@roasbeef> BLW is a bit diff tho, as the entire infra depends on a single server that has 100% of all your transactions: time, destination, amount, etc 16:08 <@roasbeef> it somehow took LN and stripped out _all_ the privacy we've worked pretty hard to create 16:08 <@roasbeef> it's as private as a web wallet (BLW is) 16:13 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 16:16 < waxwing> BLW? 16:16 <@roasbeef> "bitcoin lightning wallet" this kinda popular-ish lightnign wallet 16:16 <@roasbeef> a central server does all route planning, and that _same_ server also handles things like backups 16:16 < waxwing> oh that thing. interesting. 16:16 < waxwing> remember "thunder" or whatever? :) 16:17 <@roasbeef> hehh 16:17 < waxwing> or did that never happen. the bc.i thing 16:17 <@roasbeef> that was bettter, even in its infancy 16:17 <@roasbeef> yeh didn't really happen 16:17 <@roasbeef> dunno what mattsj is doing these days 16:17 <@roasbeef> they did contribute a fair bit on the ML back in the day tho 16:17 <@roasbeef> but yeh BLW is a privacy disaster 16:17 < waxwing> i'm kind of mystified as to what the heck those guys even do. 16:18 < waxwing> (bc.i or .com or w/e) 16:18 <@roasbeef> yeh srsly 16:18 <@roasbeef> idk they sell adds on the explorer now, and add like random alts to their consumer wallet 16:18 <@roasbeef> somehow, they still have a ton of users for their web wallet, which is what they've been raising based off of recently 16:18 <@roasbeef> afaik, they're also trying to get into the already over crowded custodial biz as well 16:18 <@roasbeef> are they doing anythign useful? nah not rly 16:19 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has joined #lnd 16:33 -!- marijnfs_ [~smuxi@2a01:c22:7a15:c000:3e64:4e4f:4191:1722] has joined #lnd 16:33 -!- marijnfs_ [~smuxi@2a01:c22:7a15:c000:3e64:4e4f:4191:1722] has quit [Remote host closed the connection] 16:33 -!- marijnfs_ [~smuxi@2a03:8600:1001:1024::1003] has joined #lnd 16:35 < waxwing> roasbeef, just so you know, i'm working on psbt now, i'm sure the first attempt won't be too great, but we'll see; it's a good learning exercise anyway. 16:38 <@roasbeef> fuk yeh 16:38 <@roasbeef> lemmie know if you have any q's as far as like API design or using the supported libs 16:39 < waxwing> for now i'm just writing a psbt.go in btcsuite/btcutil 16:39 <@roasbeef> gotcha, eventually would want to make it a diff package 16:40 <@roasbeef> may be a good exercise to start with the API itself, then work backwards from there 16:40 <@roasbeef> so like 16:40 <@roasbeef> partialTx, err := pbst.ReadPartialTx(io.Reader) 16:40 <@roasbeef> etc 16:40 < waxwing> define all the constants, make a psbt struct, read in the kv pairs into the struct and the unsigned tx, then writing out too. 16:40 <@roasbeef> like ideally what would be the easiest way to use, and also then expose the relevant details 16:41 < waxwing> i went through the bip and the test vectors a while back, so got a *pretty* good idea of what's needed, although going as far as writing code for the roles (like combiner) is kind of another level i'd put off till later. 16:41 <@roasbeef> fsho 16:41 < waxwing> mainly just get the ser/deser routines to pass the test vectors for now. 16:48 <@roasbeef> fsho 16:51 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 16:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 17:00 -!- marijnfs_ [~smuxi@2a03:8600:1001:1024::1003] has quit [Remote host closed the connection] 17:17 -!- github-lnd [github-lnd@gateway/service/github.com/x-euizcxpmisswfzxl] has joined #lnd 17:17 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #1757: htlcswitch/switch: shutdown links concurrently (master...parallel-link-shutdown) https://git.io/fAJPJ 17:17 -!- github-lnd [github-lnd@gateway/service/github.com/x-euizcxpmisswfzxl] has left #lnd [] 17:49 -!- kashike12 [~kashike@177.63.231.251] has joined #lnd 17:50 -!- kashike12 [~kashike@177.63.231.251] has quit [Remote host closed the connection] 18:01 -!- modin24 [~modin@ip68-10-2-206.hr.hr.cox.net] has joined #lnd 18:03 -!- modin24 [~modin@ip68-10-2-206.hr.hr.cox.net] has quit [Remote host closed the connection] 18:04 -!- peevsie [~peevsie@2604:2000:f18f:e300::2] has quit [Ping timeout: 265 seconds] 18:13 -!- github-lnd [github-lnd@gateway/service/github.com/x-zekbfquqmjnqxloa] has joined #lnd 18:13 -github-lnd:#lnd- [lnd] valentinewallace opened pull request #1763: channeldb+rpc: add pagination of listinvoices (master...listinvoices-pagination) https://git.io/fATRm 18:13 -!- github-lnd [github-lnd@gateway/service/github.com/x-zekbfquqmjnqxloa] has left #lnd [] 18:23 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 18:34 -!- deusexbeer [~deusexbee@095-129-172-241-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 18:36 <@roasbeef> lol @ this spam 18:36 -!- Ziya [~Android@104.223.94.74] has joined #lnd 18:40 <@roasbeef> Ziya: what's your use case? 18:43 <@roasbeef> answer is depends 18:43 <@roasbeef> can give a better answer if know the use case 18:44 <@roasbeef> like can you send a DVD over at the same time, nah 18:44 <@roasbeef> a few bytes? possibly 18:46 <@roasbeef> lemmie know when you have additional details ol 18:46 <@roasbeef> lol* 18:46 <@roasbeef> state your entire use case, then we can analyze it to see if it's really even applicable 18:49 -!- github-lnd [github-lnd@gateway/service/github.com/x-kxyflhfpctiiarql] has joined #lnd 18:49 -github-lnd:#lnd- [lnd] cfromknecht opened pull request #1764: htlcswitch/link: only resovle+gc fwdpkgs for live channels (master...isolate-fwdpkg-to-live-links) https://git.io/fATEJ 18:49 -!- github-lnd [github-lnd@gateway/service/github.com/x-kxyflhfpctiiarql] has left #lnd [] 18:56 -!- github-lnd [github-lnd@gateway/service/github.com/x-uognrwvexjzwwoep] has joined #lnd 18:56 -github-lnd:#lnd- [lnd] Roasbeef pushed 9 new commits to master: https://git.io/fATEC 18:56 -github-lnd:#lnd- lnd/master 215a47e Conner Fromknecht: channeldb/forwarding_package: loosen Add/SettleFailRef acking... 18:56 -github-lnd:#lnd- lnd/master 8177866 Conner Fromknecht: channeldb/channel: expose AckAddHtlc and AckSettleFail 18:56 -github-lnd:#lnd- lnd/master af6c4e5 Conner Fromknecht: channeldb/channel: adds readLogKey for chanids... 18:56 -!- github-lnd [github-lnd@gateway/service/github.com/x-uognrwvexjzwwoep] has left #lnd [] 18:57 < lndbot> molz, the time has come. ^^ should get rid of 99% of those annoying logs 18:57 < molz> oh? 19:00 < molz> HEAD is now at f028eaa... Merge pull request #1698 from cfromknecht/switch-fwdpkg-cleanup 19:06 < molz> conner, [ERR] LTND: unable to open channeldb: unable to update edge indexes: EOF 19:11 -!- tin_ [~tyn@73.93.142.128] has quit [Ping timeout: 240 seconds] 19:11 <@roasbeef> you updated a super old node? 19:12 <@roasbeef> that migration is from a few months ago 19:12 <@roasbeef> or you tried to downgrade it before we prevented that? 19:12 < molz> oh i thought i got the latest master 19:13 < molz> weird .. how did i get that commit? 19:13 < lndbot> what does `lnd version` show? 19:14 < molz> conner, [INF] LTND: Version 0.4.2-beta commit=f028eaa152d14e0fe85b556b79cfece2b9596cea 19:22 -!- Giszmo [~leo@45.232.32.202] has quit [Ping timeout: 252 seconds] 19:25 -!- Ziya [~Android@104.223.94.74] has quit [Quit: -a- Connection Timed Out] 19:26 -!- gethh [uid264798@gateway/web/irccloud.com/x-iuruiymtjhkzuxxl] has joined #lnd 19:28 <@roasbeef> your db version went backwards it looks like 19:28 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 240 seconds] 19:28 < lndbot> mainnet or testnet? 19:35 -!- Ziya [~Android@104.223.94.74] has joined #lnd 19:37 -!- Giszmo [~leo@pc-72-54-46-190.cm.vtr.net] has joined #lnd 19:38 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 19:50 -!- Ziya [~Android@104.223.94.74] has quit [Quit: -a- Connection Timed Out] 19:50 -!- Ziya [~Android@104.223.94.74] has joined #lnd 20:05 -!- Ziya [~Android@104.223.94.74] has quit [Quit: -a- Connection Timed Out] 20:05 -!- Ziya [~Android@104.223.94.74] has joined #lnd 20:14 -!- github-lnd [github-lnd@gateway/service/github.com/x-irrliuryolwimlhx] has joined #lnd 20:14 -github-lnd:#lnd- [lnd] Roasbeef pushed 5 new commits to master: https://git.io/fATgY 20:14 -github-lnd:#lnd- lnd/master 1c7f10a Wilmer Paulino: lnrpc: add pagination fields for ListInvoices RPC protos... 20:14 -github-lnd:#lnd- lnd/master 0339964 Wilmer Paulino: cmd/lncli: add pagination flags for listinvoices command... 20:14 -github-lnd:#lnd- lnd/master f315b5b Wilmer Paulino: channeldb: support querying for invoices within a specific time range... 20:14 -!- github-lnd [github-lnd@gateway/service/github.com/x-irrliuryolwimlhx] has left #lnd [] 20:15 -!- github-lnd [github-lnd@gateway/service/github.com/x-lhdsextyhpzgudwe] has joined #lnd 20:15 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #1720: channeldb+rpc: add pagination of listinvoices (master...listinvoices-pagination) https://git.io/fN5YB 20:15 -!- github-lnd [github-lnd@gateway/service/github.com/x-lhdsextyhpzgudwe] has left #lnd [] 20:20 -!- Ziya [~Android@104.223.94.74] has quit [Quit: -a- Connection Timed Out] 21:11 -!- Ziya [~Android@104.223.94.74] has joined #lnd 21:12 -!- rls [~rls@69.197.143.181] has joined #lnd 22:09 -!- lndbot [~lndbot@138.197.213.35] has quit [Remote host closed the connection] 22:09 -!- lndbot1 [~lndbot@138.197.213.35] has joined #lnd 22:11 -!- windsok [~windsok@unaffiliated/windsok] has quit [Remote host closed the connection] 22:14 -!- windsok [~windsok@rarepepe.cash] has joined #lnd 22:14 -!- windsok [~windsok@rarepepe.cash] has quit [Changing host] 22:14 -!- windsok [~windsok@unaffiliated/windsok] has joined #lnd 22:15 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 22:18 < Veggen> roasbeef: Looking forward to try mobile LND :) 22:50 -!- lndbot [~lndbot@138.197.213.35] has joined #lnd 22:51 -!- lndbot1 [~lndbot@138.197.213.35] has quit [Ping timeout: 252 seconds] 22:59 -!- lndbot [~lndbot@138.197.213.35] has quit [Remote host closed the connection] 22:59 -!- lndbot [~lndbot@138.197.213.35] has joined #lnd 23:11 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 23:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 23:20 -!- tin_ [~tyn@76-220-26-109.lightspeed.sntcca.sbcglobal.net] has joined #lnd 23:56 -!- tin_ [~tyn@76-220-26-109.lightspeed.sntcca.sbcglobal.net] has quit [Ping timeout: 260 seconds]